mcp-fns-check
PYPI · ATOMNO-MCP-FNS-CHECK · SCANNED SEP 20
Russian tax authority (FNS) counterparty checks: status, debts, blocks. Due diligence MCP.
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
- 2 of 25 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 15 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1432 tokens (~159/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 67% 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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 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-fns-check server?
mcp-fns-check runs locally as a PyPI package, launched with uvx atomno-mcp-fns-check. 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-fns-check
claude mcp add atomno-mcp-mcp-fns-check -- uvx atomno-mcp-fns-check
{
"mcpServers": {
"atomno-mcp-mcp-fns-check": {
"command": "uvx",
"args": [
"atomno-mcp-fns-check"
]
}
}
} {
"servers": {
"atomno-mcp-mcp-fns-check": {
"command": "uvx",
"args": [
"atomno-mcp-fns-check"
]
}
}
} codex mcp add atomno-mcp-mcp-fns-check -- uvx atomno-mcp-fns-check
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"atomno-mcp-mcp-fns-check": {
"type": "local",
"command": [
"uvx",
"atomno-mcp-fns-check"
],
"enabled": true
}
}
} openclaw mcp add atomno-mcp-mcp-fns-check --command uvx --arg atomno-mcp-fns-check
mcp_servers:
atomno-mcp-mcp-fns-check:
command: "uvx"
args: ["atomno-mcp-fns-check"] {
"McpServers": {
"atomno-mcp-mcp-fns-check": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"atomno-mcp-fns-check"
]
}
}
} assistant mcp add atomno-mcp-mcp-fns-check -t stdio -c uvx -a atomno-mcp-fns-check
{
"mcpServers": {
"atomno-mcp-mcp-fns-check": {
"command": "uvx",
"args": [
"atomno-mcp-fns-check"
]
}
}
} 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.
- 20 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.
- 19 Sept 26 −3
- Stability: pass → 0.83 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.
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-fns-check@0.1.12
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 25 packages
| Packages resolved | 25 |
|---|---|
| Stale | 2 |
| 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 →
check_contractor ~239
Главный тул: полная проверка контрагента по одному идентификатору. Принимает ИНН (10 цифр — юр.лицо, 12 — ИП/физлицо) или ОГРН (13 цифр — юр.лицо, 15 — ИП). Тип определяется строго по длине и контрольной цифре.
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | ИНН (10/12 цифр) или ОГРН/ОГРНИП (13/15 цифр). Пример: '7707083893' (Сбербанк) или '1027700132195'. |
| include_extended_risks | boolean | – | Запускать ли 3 расширенные проверки (налоговые долги из открытых данных ФНС, ФССП, КАД). По умолчанию True. |
| lawsuits_threshold_rub | number | – | Порог фильтрации арбитражных дел в рублях. По умолчанию 1 000 000 ₽ — отсекает мелкие споры. |
Structured output declared, but exposes no named fields.
No examples provided.
check_for_red_flags ~385
Агрегированный риск-чек по контрагенту (7 проверок, SPEC §3.5). Базовые 4 проверки (всегда): * `mass_address` — массовый юр.адрес ФНС; * `mass_director` — массовый руководитель (≥10 действующих компаний); * `disqualified_director` — руководитель в реестре дисквалифицированных; * `bankruptcy_records` — активные дела в ЕФРСБ. Расширенные 3 проверки (`include_extended=True`): * `tax_debts` — задолженность по налогам из открытых данных ФНС (набор «debtam»); * `enforcement_proceedings` — открытые исп.производства (Банк данных ФССП); * `active_lawsuits` — активные арбитражные дела где контрагент ответчик (КАД), фильтр по сумме иска через `lawsuits_threshold_rub`. Любая внешняя проверка может вернуть ошибку (CAPTCHA, 5xx, timeout) — она попадёт в `errors[]` и не сорвёт остальные проверки. Пустой `flags[]` сам по себе не означает «чисто»: смотрите `coverage` — сколько проверок реально ответило.
| Name | Type | Req | Description |
|---|---|---|---|
| include_extended | boolean | – | запускать ли расширенные 3 проверки. По умолчанию True. |
| inn | string | yes | ИНН контрагента (10 или 12 цифр). |
| lawsuits_threshold_rub | number | – | порог фильтра арбитражных дел в рублях. По умолчанию 1 000 000 ₽ (отсечь мелкие споры). |
Structured output declared, but exposes no named fields.
No examples provided.
check_individual_bankruptcy ~153
Проверка банкротства физического лица в ЕФРСБ по ФИО и дате рождения. Ищет активные процедуры банкротства гражданина в публичном реестре bankrot.fedresurs.ru. Для уточнения однофамильцев можно передать СНИЛС.
| Name | Type | Req | Description |
|---|---|---|---|
| birth_date | string | yes | Дата рождения 'YYYY-MM-DD' или 'dd.mm.yyyy'. |
| fio | string | yes | ФИО полностью, кириллица. Пример: 'Иванов Иван Иванович'. |
| snils | – | – | Опционально — СНИЛС (11 цифр) для disambiguation однофамильцев. |
Structured output declared, but exposes no named fields.
No examples provided.
check_inn ~88
Полная карточка контрагента по ИНН (10 цифр — юр.лицо, 12 — ИП).
| Name | Type | Req | Description |
|---|---|---|---|
| include_extended | boolean | – | зарезервировано для S2.x (Прозрачный бизнес). |
| inn | string | yes | ИНН контрагента. Пример: '7707083893' (Сбербанк). |
Structured output declared, but exposes no named fields.
No examples provided.
check_ogrn ~54
Карточка контрагента по ОГРН (13 цифр) или ОГРНИП (15 цифр).
| Name | Type | Req | Description |
|---|---|---|---|
| include_extended | boolean | – | – |
| ogrn | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_directors_history ~158
История смены руководителей и учредителей по ИНН. На стадии S3 возвращает только текущего руководителя из egrul.nalog.ru плюс предупреждение о неполноте данных. Полная история (с датами назначения/увольнения) появится на стадии S5 после загрузки Open Data slice ЕГРЮЛ.
| Name | Type | Req | Description |
|---|---|---|---|
| depth_years | integer | – | на S3 не используется (история пока без дат). |
| include_founders | boolean | – | на S3 не используется (ЕГРЮЛ-search не отдаёт учредителей). |
| inn | string | yes | ИНН контрагента (10 или 12 цифр). |
Structured output declared, but exposes no named fields.
No examples provided.
get_legal_status ~62
Текущий жизненный статус: active / liquidating / bankruptcy / liquidated / reorganizing / excluded_inactive. Минимум один из `inn` или `ogrn` обязателен.
| Name | Type | Req | Description |
|---|---|---|---|
| inn | – | – | – |
| ogrn | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_okveds ~60
Перечень кодов ОКВЭД основной + дополнительные с расшифровкой по справочнику ОКВЭД-2.
| Name | Type | Req | Description |
|---|---|---|---|
| include_history | boolean | – | – |
| inn | – | – | – |
| ogrn | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
ping ~25
Диагностический тул: проверяет, что сервер запущен и доступен.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
What is the mcp-fns-check server?
mcp-fns-check is listed in the public MCP registry as io.github.atomno-mcp/mcp-fns-check. Russian tax authority (FNS) counterparty checks: status, debts, blocks. Due diligence MCP. This page covers its PyPI package (atomno-mcp-fns-check).
Is the mcp-fns-check server safe to use?
mcp-fns-check scores 80 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-fns-check server expose?
mcp-fns-check exposes 9 tools: ping, check_contractor, check_inn, check_ogrn, get_legal_status, and 4 more. Their descriptions and schemas cost roughly 1,224 tokens of context every time the server is loaded.
Is the mcp-fns-check server still maintained?
mcp-fns-check 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-fns-check server under?
mcp-fns-check declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.