Checko MCP Server

Unofficial Checko.ru MCP server for counterparty checks: EGRUL, EGRIP, financials, court cases, state contracts and bankruptcies

MCP serverMedium riskRussian stack

nymaxxx/checko-mcp

Install

{
  "mcpServers": {
    "checko": {
      "command": "uvx",
      "args": ["checko-mcp"],
      "env": { "CHECKO_API_KEY": "ваш_ключ" }
    }
  }
}

Requires uv. Works in any MCP client; a Cursor example is in .cursor/mcp.example.json.

This is third-party code. Review the repository files before installing.

What it does

The server connects the Checko.ru API to the agent through 12 tools: company and sole trader search, EGRUL and EGRIP records, individual data by INN, financial statements, arbitration cases, state contracts under 44-FZ and 223-FZ, inspections, bank by BIC, change history, and Fedresurs and bankruptcy registry notices. Six ready prompts define call order for common tasks: counterparty check, payment details check, bankruptcy risk, tender participant review and financial analysis. Resources include an agent guide, a legal note on Federal Law 152-FZ and a methodology for auditing individuals.

Who it is for. For lawyers, finance staff, procurement and sales teams who vet Russian companies before a deal.

Good fit when

  • You need to vet a new counterparty before signing
  • You need to assess a tender participant by contracts, lawsuits and financials
  • You need to verify payment details against registry data

Not a fit when

  • You need a legally valid document rather than a model summary
  • You have no lawful basis to collect data on individuals

Example request

Check the counterparty with INN 7700000000: status, court cases for the last three years, financials and bankruptcy signs

Limitations

Requires your own Checko.ru API key; API access is paid under Checko's plans. The project is not affiliated with Checko. Conclusions come from the language model and can be wrong, so verify key facts with the tax service, court and bankruptcy registries. Handling data on individuals falls under Federal Law 152-FZ.

How to disable. Delete the checko block from your MCP client config.

MCP

Transport
stdio
Authentication
API key
Environment variables
Environment variables
CHECKO_API_KEY
required, secret
Checko.ru API key
CHECKO_BASE_URL
API base URL, https://api.checko.ru/v2 by default
CHECKO_TIMEOUT
Request timeout in seconds, 30 by default

Security check

  • Requires a paid Checko.ru API key
  • Can request personal data of individuals

README in short

The Russian README lists the server's tools, prompts and reference resources. The main launch path is uvx, with Docker Compose, docker run and pip alternatives and a config for each. It covers environment variables and legal limits under Russian personal data and information laws, and warns that the model can make mistakes. MIT licensed.

FAQ

What do I need to install?

Just uv, which includes uvx. Docker or a local Python install also work.

Can I trust the conclusions?

Data comes from registries via Checko, but the model retells it. Verify important facts with primary sources before deciding.

Editors’ pick

166 skills for scientific work: bioinformatics, cheminformatics, clinical data, geospatial analysis and 100+ databases

SkillMedium risk44.9K
Editors’ pick

Google's open-source MCP server for databases: ready tools for Postgres, MySQL, BigQuery, Spanner and more, plus custom tools in tools.yaml

MCP serverHigh risk16.4K
Editors’ pick

A token-lean MCP server for PostgreSQL, MySQL, MariaDB, SQL Server and SQLite with a read-only mode

MCP serverHigh risk3.5K
Editors’ pick

Official MongoDB MCP server: queries and aggregations, index management, Atlas clusters and local deployments

MCP serverHigh risk1.1K