bulk_cards
Массовая выгрузка до 100 карточек за один вызов.
Вернёт объект с полями cards (успешные) и errors (точечные ошибки по отдельным ИНН) — один плохой ИНН не ломает весь bulk.
LABSCO SUMMARY
It answers from a snapshot it carries, and ping is how you find out which one.
Every lookup resolves against a local copy of the register rather than a call outward, which is why ping returns the snapshot size beside the server version — that pair is the freshness statement, and it is worth reading before a card is quoted anywhere it matters. Everything else in the API is shaped around whichever identifier you happen to hold: an INN, an OGRN or OGRNIP, or nothing but a name, with get_full_card accepting either number and resolving the clash by preferring inn. bulk_cards is the one built for lists, and it returns partial success with the failures itemised rather than rejecting the batch.
What it is
A lookup server over a local snapshot of the EGRUL register: cards resolved by INN, OGRN or OGRNIP, fuzzy name search through FTS5, targeted founder and director reads, and a bulk mode.
What you get
- Identifier lookups that know their own formats: search_by_inn takes a 10-digit INN for a company or a 12-digit one for a sole trader or individual, and search_by_ogrn takes a 13-digit OGRN or a 15-digit OGRNIP.
- The whole record in a single call: get_full_card returns every section — registration details, OKVED activity codes, founders and director — accepting inn or ogrn, and using inn when both arrive.
- Name search for when you have no number: search_by_name runs a fuzzy match through FTS5 with a result limit and an only_active filter.
- Founders and director on their own: get_founders returns a company's founders and get_director returns its current head, each taking the 10-digit INN only.
- Bulk that does not fail as a unit: bulk_cards takes up to 100 INNs per call and splits the response into cards for the ones that resolved and errors for the ones that did not.
- ping reports that the server is up, its version, and the size of the local snapshot it is answering from.
Requirements
No credentials, but no data until you import it: download the FNS EGRUL and EGRIP open-data dumps (about 15 GB) and run atomno-mcp-egrul-import once. Lookups then resolve against that local snapshot, which ping reports on.
Setup effort
Follow the published steps — pipx install atomno-mcp-egrul
USE CASES
01
Checking a counterparty before you sign anything
Resolve the company from the number on the invoice, open every section of its card, and confirm who is entitled to sign.
02
Resolving a company when all you have is a name
Search the name as it was written to you, then open the card of the match that fits.
03
Screening a supplier list in one pass
Send the identifiers as a batch and read the cards that came back beside the itemised failures.
04
Finding out who actually owns the company you deal with
Read the founders on record, then the person currently running it.
05
Knowing how current the data is before quoting it
Ask the server for its version and the snapshot it is serving from, and date the answer accordingly.
8 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
get_director
Текущий руководитель юр.лица по ИНН (только 10-значный ИНН).
get_founders
Учредители юр.лица по ИНН (только 10-значный ИНН).
get_full_card
Полная карточка (все секции: реквизиты, ОКВЭД, учредители, директор).
Хотя бы один из inn / ogrn обязателен. Если переданы оба — используется inn.
ping
Диагностика: сервер жив, сообщает версию и размер локального слепка.
search_by_inn
Карточка юр.лица или ИП по ИНН (10 цифр — ООО/АО, 12 — ИП/физлицо).
search_by_name
Fuzzy-поиск юр.лиц по названию через FTS5.
search_by_ogrn
Карточка по ОГРН (13 цифр) или ОГРНИП (15 цифр).
BEFORE YOU INSTALL
What to know first
Tools you get
8 tools when we connected. Seven are data tools plus a ping health check. Without imported dumps or ATOMNO_API_KEY, they query an empty local SQLite database.
Requires
- Python 3.11+
- uv or pipx
- The FNS EGRUL/EGRIP open-data dumps, imported locally (about 15 GB)
Where it runs
All 3 documented clients run the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 8 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
pipx install atomno-mcp-egrulDownload the EGRUL and EGRIP open-data archives from the FNS site after accepting its licence — https://www.nalog.gov.ru/opendata/7707329152-egrul/ and https://www.nalog.gov.ru/opendata/7707329152-egrip/ (about 15 GB for a full snapshot; the server does not download them itself)
In a working folder, put the archives under dumps/egrul/YYYY-MM-DD/ and dumps/egrip/YYYY-MM-DD/
From that folder, run the one-time full import: atomno-mcp-egrul-import --registry egrul --full and then atomno-mcp-egrul-import --registry egrip --full
The import writes mcp_egrul_data.sqlite into that folder — set MCP_EGRUL_DB to its absolute path in the client entry below, otherwise every lookup queries an empty database
MCP Clients
Claude Desktop, Cursor
JSON
{
"mcpServers": {
"egrul": {
"command": "uvx",
"args": [
"atomno-mcp-egrul"
],
"env": {
"MCP_EGRUL_DB": "<YOUR_MCP_EGRUL_DB>"
}
}
}
}Any MCP client — without uv
For clients without uv: the pipx install atomno-mcp-egrul step above puts the atomno-mcp-egrul command on your PATH (pip install atomno-mcp-egrul in a venv works too).
ANY MCP CLIENT — WITHOUT UV · JSON
{
"mcpServers": {
"egrul": {
"command": "atomno-mcp-egrul",
"env": {
"MCP_EGRUL_DB": "<YOUR_MCP_EGRUL_DB>"
}
}
}
}
