MCP Fssp

What atomno-mcp/mcp-fssp MCP server does

The atomno-mcp/mcp-fssp MCP server exposes Russian Federal Bailiff Service enforcement-proceeding lookups through MCP. It is intended for checking open proceedings associated with three subject types:

• Individuals identified by full name and date of birth.
• Legal entities identified by a 10-digit INN or 13-digit OGRN.
• Individual entrepreneurs identified by a 12-digit INN or 15-digit OGRNIP.

Returned information can include proceeding amounts, statuses, bailiff data, and the stated basis for collection. The project describes the results as an aggregator view over public FSSP data, not as official documents. It is not affiliated with the FSSP or with the listed commercial providers.

The project is relevant to Russian counterparty due diligence, onboarding, legal review, and screening workflows. Personal data handling remains the operator’s responsibility, including compliance with applicable Russian personal-data requirements.

How it works

The atomno-mcp/mcp-fssp MCP server runs locally as a Python command-line MCP server. It selects a backend using MCP_FSSP_PROVIDER. Supported provider names in the configuration are damia, checko, newdb, api_cloud, self_parser, and atomno_pro; the documented commercial API options require credentials from the relevant provider.

The documented tool interface includes ping, check_individual_debts, check_legal_entity_debts, and get_proceeding_details. The individual lookup accepts a name, birth date, and optional region. The legal-entity lookup accepts an INN or OGRN, and the proceeding-details operation accepts a proceeding ID. The roadmap indicates staged delivery: the current v0.1 scope centers on the Damia provider and individual checks, while later versions add more providers and lookup operations.

The README explains that the historical official FSSP API has been unavailable since March 10, 2022, while the public website uses CAPTCHA. This server therefore relies on provider APIs rather than claiming to restore that official API. The planned Pro mode is separate from the open client and is not required when using a supported provider key directly.

Setup and configuration

Install the package with pipx install atomno-mcp-fssp, uvx atomno-mcp-fssp, or pip. For MCP clients, the documented configuration uses uvx with atomno-mcp-fssp as its argument. Cursor and Claude Desktop examples pass provider settings and the provider key through the MCP server’s env block.

A minimal configuration selects a provider and supplies its credential, for example MCP_FSSP_PROVIDER=damia with MCP_FSSP_DAMIA_KEY set. Alternatives include MCP_FSSP_CHECKO_KEY, MCP_FSSP_NEWDB_KEY, and MCP_FSSP_API_CLOUD_KEY. The server also exposes settings for request timeout, request-rate limiting, user agent, audit-log location, and log level. Defaults documented in the README include a 15-second HTTP timeout, 30 requests per minute, an SQLite audit log at ./audit.sqlite, and INFO logging.

The audit log does not store names and birth dates in plain text according to the README; it stores a SHA-256 value derived from the normalized name and birth date. Operators should still assess whether their use of the data is lawful and appropriate.

Limitations and notes

Results are described as informational and may not be current, complete, or accurate. They should not replace documents issued by the FSSP. For legally significant decisions, the project recommends obtaining primary documents from the debtor or through official channels.

Provider availability, pricing, quotas, and response quality are outside the MCP server itself. The README lists free trial or free daily allowances for some providers and paid request options for others, so an operator must review the selected provider’s terms.

The README lists summarize_debts and monitor_debts_changes as Pro-version or future capabilities. They should not be treated as part of the confirmed open-client baseline. CAPTCHA-based self-parsing and the hosted Pro backend are also described as roadmap or planned components rather than established dependencies of the local package.

The atomno-mcp/mcp-fssp MCP server is licensed under MIT. The separate planned Pro backend is described as proprietary, so that statement does not change the license of the open client.