mcp-zakupki
PYPI · ATOMNO-MCP-ZAKUPKI
MCP server for Russian government procurement data (44-FZ / 223-FZ / 615-PP).
Available components
Last scanned (1 hour ago)
Scores higher than 64% of PyPI servers
Category Finance and Payments
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 Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 26 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 61 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1027 tokens (~171/item across 6 items; 6 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 75% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
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.
- 5 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 1 Nov 26 0
- Stability: 0.97 → pass security
- 31 Oct 26 0
- Stability: pass → 0.97 functional
- 25 Oct 26 0
- Stability: 0.97 → pass security
- 24 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- Stability: pass → 0.97 functional
- 22 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 18 Oct 26 +1
- Stability: 0.97 → pass security
- 16 Oct 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 5 Nov 2026 · Analysed pypi/atomno-mcp-zakupki@0.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
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 26 packages
| Packages resolved | 26 |
|---|---|
| Stale | 1 |
| 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 →
get_customer_history ~148
Карточка заказчика по ИНН или ОГРН с официального сайта ЕИС. Отдаёт реквизиты и статус в реестре недобросовестных поставщиков. Сводку объёмов сайт без токена машинного обмена не считает.
| Name | Type | Req | Description |
|---|---|---|---|
| inn | – | – | ИНН заказчика (10 цифр для юр.лица, 12 для ИП). |
| ogrn | – | – | ОГРН/ОГРНИП заказчика. |
| period_from | – | – | начало периода (YYYY-MM-DD, default 2024-01-01). |
| period_to | – | – | конец периода (YYYY-MM-DD, default — сегодня). |
Structured output declared, but exposes no named fields.
No examples provided.
get_supplier_stats ~85
Сводка по поставщику. На официальном сайте без токена машинного обмена недоступна — вернёт отказ с причиной, не пустые нули.
| Name | Type | Req | Description |
|---|---|---|---|
| inn | – | – | ИНН поставщика. |
| ogrn | – | – | ОГРН/ОГРНИП поставщика. |
| period_from | – | – | – |
| period_to | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_tender ~99
Получить полную карточку тендера по реестровому номеру ЕИС.
| Name | Type | Req | Description |
|---|---|---|---|
| include_documents | boolean | – | включить URLs всех приложенных документов. |
| include_protocols | boolean | – | включить протоколы (более тяжёлый вызов). |
| reg_number | string | yes | реестровый номер тендера (19–21 цифр). Пример: "0173100007426000018". |
Structured output declared, but exposes no named fields.
No examples provided.
lookup_okpd2 ~144
Найти код ОКПД2 / КТРУ по тексту запроса (полнотекстовый поиск). Использует vendored-справочник из 60+ топ-кодов (Phase 0–1) или полный справочник после CI-загрузки. Нет сетевых обращений.
| Name | Type | Req | Description |
|---|---|---|---|
| code_type | string | – | "okpd2" (default), "ktru" или "both". |
| limit | integer | – | количество результатов (1–50, default 10). |
| query | string | yes | текст запроса (минимум 3 символа). Пример: "разработка веб-портала". |
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.
search_tenders ~437
Найти тендеры (44-ФЗ / 223-ФЗ / 615-ПП) по фильтрам в ЕИС zakupki.gov.ru. Возвращает структурированный массив до 100 объектов на вызов с пагинацией через `next_page_token`. Все фильтры комбинируются через AND.
| Name | Type | Req | Description |
|---|---|---|---|
| applications_deadline_from | – | – | – |
| applications_deadline_to | – | – | – |
| customer_inn | – | – | ИНН заказчика (10 цифр — юр.лицо, 12 — ИП). |
| customer_ogrn | – | – | ОГРН заказчика (13 — юр.лицо, 15 — ИП). |
| ktru_codes | – | – | коды КТРУ для более точной фильтрации. |
| law_type | – | – | список из ["44-fz", "223-fz", "615-pp"]; default — оба ФЗ. |
| limit | integer | – | количество объектов в ответе (1–100, default 20). |
| next_page_token | – | – | токен следующей страницы из предыдущего ответа. |
| okpd2_codes | – | – | коды ОКПД2 (можно префиксы: "62.0" включит всё под 62.0). |
| platform | – | – | ЭТП ("sberbank_ast", "rts_tender", "roseltorg", "tek_torg", "gpb", "rad", "fabrikant", "agz_rt"). |
| price_max_rub | – | – | – |
| price_min_rub | – | – | – |
| publish_date_from | – | – | – |
| publish_date_to | – | – | – |
| query | – | – | свободный поиск по наименованию объекта закупки. |
| regions | – | – | коды субъектов РФ ("66" = Свердловская обл., "74" = Челябинская). |
| smp_only | boolean | – | только закупки среди субъектов малого предпринимательства. |
| status | – | – | статус тендера ("published", "applications_open", "applications_closed", "in_progress", "completed", "cancelled", "all_active"). |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the mcp-zakupki server?
mcp-zakupki runs locally as a PyPI package, launched with uvx atomno-mcp-zakupki. 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-zakupki
claude mcp add atomno-mcp-mcp-zakupki -- uvx atomno-mcp-zakupki
What is the mcp-zakupki server?
mcp-zakupki is listed in the public MCP registry as io.github.atomno-mcp/mcp-zakupki. MCP server for Russian government procurement data (44-FZ / 223-FZ / 615-PP). This page covers its PyPI package (atomno-mcp-zakupki).
Is the mcp-zakupki server safe to use?
mcp-zakupki scores 67 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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-zakupki server expose?
mcp-zakupki exposes 6 tools: ping, search_tenders, get_tender, get_customer_history, get_supplier_stats, lookup_okpd2. Their descriptions and schemas cost roughly 938 tokens of context every time the server is loaded.
Is the mcp-zakupki server still maintained?
mcp-zakupki is still listed as active in the MCP registry. We last reached this channel on 5 November 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-zakupki server under?
mcp-zakupki declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.