mcp-fssp: Russian bailiff debt lookup
mcp-fssp
An MCP server that checks Russian bailiff proceedings for individuals, companies and sole proprietors through data providers, no FSSP key needed
- 0 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Returns debt and enforcement-proceeding data about specific people and companies
- Provider keys are paid and grant access to third parties' personal data; use must comply with Russia's 152-FZ
Install
- Works in
- Services
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/mcp-fsspDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Returns debt and enforcement-proceeding data about specific people and companies
- Provider keys are paid and grant access to third parties' personal data; use must comply with Russia's 152-FZ
This is third-party code. Review the repository files before installing.
What it does
The official FSSP API has been closed since March 2022, and the only official access point is a CAPTCHA-protected website, so the server works through commercial intermediaries: Damia (the default provider), Checko, NewDB or api-cloud, with the user supplying a key for one of them. It exposes four tools: ping checks server readiness and the active provider, check_individual_debts searches proceedings for a person by full name and birth date, check_legal_entity_debts searches by a legal entity or sole proprietor's INN or OGRN, and get_proceeding_details returns one proceeding's card by number. Personal data is not written to the audit log in plain text: only a sha256 hash of the name and birth date is stored. Per the stated roadmap, the current version 0.1 is Phase 0: only the Damia provider actually works, the other three providers and a CAPTCHA-solving self_parser are planned for later versions.
Who it is for. For lawyers, banks and scoring teams who need bailiff-debt due diligence on a counterparty right from an agent chat.
Good fit when
- You need to check an individual or a legal entity for open enforcement proceedings before a deal
- You want one unified call instead of parsing raw responses from several different data providers
- It matters that the checked person's name and birth date aren't stored in plain text in logs
Not a fit when
- You have no key for any of the commercial providers (Damia, Checko, NewDB, api-cloud): the server does not work without one
- You need a provider other than Damia: only it works in version 0.1, the rest are planned for future versions
- You need an official FSSP document for a legally binding decision rather than a reference check
Example request
Check whether Ivan Ivanov, born in 1985, has any open enforcement proceedingsMCP
- Transport
- stdio
- Authentication
- API key
Environment variables
MCP_FSSP_PROVIDER- Data provider choice: damia, checko, newdb, api_cloud, self_parser or atomno_pro, defaults to damia.
MCP_FSSP_DAMIA_KEYrequired, secret- Key for the Damia provider, the only one that actually works in the current version.
ATOMNO_API_KEYsecret- Key for Pro-mode features like summarize_debts and change monitoring; the backend has not shipped yet per the roadmap.
Limitations
Not affiliated with Russia's FSSP or any of the data providers, as the README states explicitly. The data is for reference and does not replace official FSSP documents. In version 0.1 only the Damia provider actually works (from 7,000 rubles a year per 1,000 requests, 100 free for testing); the other three providers and a CAPTCHA-solving self_parser are still in development. Pro features (summarize_debts, change monitoring) need a separate paid ATOMNO_API_KEY and a backend that, per the roadmap, has not shipped yet. Compliance with Russia's personal data law (152-FZ) when processing this data is the user's responsibility.
How to disable. Remove the fssp block from mcpServers in your client config and run pipx uninstall atomno-mcp-fssp (or pip uninstall).
FAQ
Do I need a key from FSSP itself?
No, the official FSSP API has been closed since 2022; the server works through a commercial provider like Damia, which is where you need your own key.
Are the checked person's name and birth date stored?
Not in plain text; the audit log stores only a sha256 hash of them, not the data itself.
Discussion
No questions or reviews yet.
NewDB MCP server for KYC and company checks
NewDB MCP Server
The official MCP server for the paid NewDB API: passports, bailiff debts, company registry, tax account holds and bankruptcy checks across Russia and the CIS
An MCP server that checks Russian counterparties by INN or OGRN: company registry, bankruptcy, tax debt, bailiffs and arbitration
KontragentPro MCP: Russian company lookup
KontragentPro MCP server
KontragentPro's official MCP that checks Russian companies by INN with no key required: EGRUL, FNS filings, bankruptcy, inspections and sanctions lists
Unofficial Checko.ru MCP server for counterparty checks: EGRUL, EGRIP, financials, court cases, state contracts and bankruptcies
EGRUL and EGRIP MCP server: company and sole proprietor details, director and founders from Federal Tax Service open data, self-hosted
tender-mcp: Russian procurement analysis
tender-mcp
A FastMCP server that parses Russian EIS procurement XML under laws 44-FZ and 223-FZ and computes contract price, prequalification and dumping risk
README in short
The README explains the project's niche: the official FSSP API is closed, and the only access point is a CAPTCHA-protected site, so the server wraps several commercial providers. It lists four available tools, environment variables, connection steps for Cursor and Claude Desktop via uvx, a personal-data-safety section citing laws 229-FZ and 152-FZ, an honest disclaimer of non-affiliation with FSSP and the providers, and a detailed roadmap from the current version 0.1 to Pro features. MIT license; the planned Pro backend will be proprietary.