mcp-egrul
PYPI · ATOMNO-MCP-EGRUL · SCANNED SEP 20
EGRUL/EGRIP company registry lookup for Russian legal entities and entrepreneurs.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security99
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 3 of 32 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 67 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 507 tokens (~63/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage80
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 30% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the mcp-egrul server?
mcp-egrul runs locally as a PyPI package, launched with uvx atomno-mcp-egrul. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · atomno-mcp-egrul
claude mcp add atomno-mcp-mcp-egrul -- uvx atomno-mcp-egrul
{
"mcpServers": {
"atomno-mcp-mcp-egrul": {
"command": "uvx",
"args": [
"atomno-mcp-egrul"
]
}
}
} {
"servers": {
"atomno-mcp-mcp-egrul": {
"command": "uvx",
"args": [
"atomno-mcp-egrul"
]
}
}
} codex mcp add atomno-mcp-mcp-egrul -- uvx atomno-mcp-egrul
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"atomno-mcp-mcp-egrul": {
"type": "local",
"command": [
"uvx",
"atomno-mcp-egrul"
],
"enabled": true
}
}
} openclaw mcp add atomno-mcp-mcp-egrul --command uvx --arg atomno-mcp-egrul
mcp_servers:
atomno-mcp-mcp-egrul:
command: "uvx"
args: ["atomno-mcp-egrul"] {
"McpServers": {
"atomno-mcp-mcp-egrul": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"atomno-mcp-egrul"
]
}
}
} assistant mcp add atomno-mcp-mcp-egrul -t stdio -c uvx -a atomno-mcp-egrul
{
"mcpServers": {
"atomno-mcp-mcp-egrul": {
"command": "uvx",
"args": [
"atomno-mcp-egrul"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 −3
- Stability: pass → 0.80 functional
- 18 Sept 26 +1
- Stability: 0.97 → pass security
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 −3
- Stability: pass → 0.80 functional
- 11 Sept 26 +1
- Stability: 0.97 → pass security
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed pypi/atomno-mcp-egrul@0.1.10
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 32 packages
| Packages resolved | 32 |
|---|---|
| Stale | 3 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
bulk_cards ~77
Массовая выгрузка до 100 карточек за один вызов. Вернёт объект с полями `cards` (успешные) и `errors` (точечные ошибки по отдельным ИНН) — один плохой ИНН не ломает весь bulk.
| Name | Type | Req | Description |
|---|---|---|---|
| inns | array | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_director ~41
Текущий руководитель юр.лица по ИНН (только 10-значный ИНН).
| Name | Type | Req | Description |
|---|---|---|---|
| inn | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_founders ~39
Учредители юр.лица по ИНН (только 10-значный ИНН).
| Name | Type | Req | Description |
|---|---|---|---|
| inn | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_full_card ~72
Полная карточка (все секции: реквизиты, ОКВЭД, учредители, директор). Хотя бы один из `inn` / `ogrn` обязателен. Если переданы оба — используется `inn`.
| Name | Type | Req | Description |
|---|---|---|---|
| inn | – | – | – |
| ogrn | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
ping ~26
Диагностика: сервер жив, сообщает версию и размер локального слепка.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
search_by_inn ~51
Карточка юр.лица или ИП по ИНН (10 цифр — ООО/АО, 12 — ИП/физлицо).
| Name | Type | Req | Description |
|---|---|---|---|
| inn | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
search_by_name ~77
Fuzzy-поиск юр.лиц по названию через FTS5.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | максимум результатов (1..50). |
| only_active | boolean | – | фильтровать только записи со статусом 'active'. |
| query | string | yes | строка запроса (минимум 2 символа). |
Structured output declared, but exposes no named fields.
No examples provided.
search_by_ogrn ~43
Карточка по ОГРН (13 цифр) или ОГРНИП (15 цифр).
| Name | Type | Req | Description |
|---|---|---|---|
| ogrn | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
What is the mcp-egrul server?
mcp-egrul is listed in the public MCP registry as io.github.atomno-mcp/mcp-egrul. EGRUL/EGRIP company registry lookup for Russian legal entities and entrepreneurs. This page covers its PyPI package (atomno-mcp-egrul).
Is the mcp-egrul server safe to use?
mcp-egrul scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the mcp-egrul server expose?
mcp-egrul exposes 8 tools: ping, search_by_inn, search_by_ogrn, search_by_name, get_full_card, and 3 more. Their descriptions and schemas cost roughly 426 tokens of context every time the server is loaded.
Is the mcp-egrul server still maintained?
mcp-egrul is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the mcp-egrul server under?
mcp-egrul declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.