Диадок MCP (RU) — ЭДО, документы, контрагенты
PYPI · DIADOC-MCP-RU · SCANNED SEP 20
API Диадока в ИИ-ассистенте: документы ЭДО, контрагенты, подписание, МЧД
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 0 of 31 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency32
- 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
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 2233 tokens (~124/item across 18 items; 18 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 Management23
- Stability check failed: the tool surface changed between 0.2.0 and 0.3.0: 1 tool removals, 0 breaking changes, 5 additions. See how to fix → Fail
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety95
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 4 of 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "diadoc_call_method" implies "execute" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
- An AI judge read all 18 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 (RU) — ЭДО, документы, контрагенты server?
Диадок MCP (RU) — ЭДО, документы, контрагенты runs locally as a PyPI package, launched with uvx diadoc-mcp-ru. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · diadoc-mcp-ru
claude mcp add ilyautov-diadoc-mcp-ru -- uvx diadoc-mcp-ru
{
"mcpServers": {
"ilyautov-diadoc-mcp-ru": {
"command": "uvx",
"args": [
"diadoc-mcp-ru"
]
}
}
} {
"servers": {
"ilyautov-diadoc-mcp-ru": {
"command": "uvx",
"args": [
"diadoc-mcp-ru"
]
}
}
} codex mcp add ilyautov-diadoc-mcp-ru -- uvx diadoc-mcp-ru
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ilyautov-diadoc-mcp-ru": {
"type": "local",
"command": [
"uvx",
"diadoc-mcp-ru"
],
"enabled": true
}
}
} openclaw mcp add ilyautov-diadoc-mcp-ru --command uvx --arg diadoc-mcp-ru
mcp_servers:
ilyautov-diadoc-mcp-ru:
command: "uvx"
args: ["diadoc-mcp-ru"] {
"McpServers": {
"ilyautov-diadoc-mcp-ru": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"diadoc-mcp-ru"
]
}
}
} assistant mcp add ilyautov-diadoc-mcp-ru -t stdio -c uvx -a diadoc-mcp-ru
{
"mcpServers": {
"ilyautov-diadoc-mcp-ru": {
"command": "uvx",
"args": [
"diadoc-mcp-ru"
]
}
}
} 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
- Package version: 0.2.2 → 0.3.0 functional
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 16.
- 15 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 14 Sept 26 −18
- Malware scan: pass → unverified ▼ security
- Stability: 0.07 → fail ▼ security
- Schema quality: 110 → 124 ▼ functional
- Schema quality: excellent → good functional
- Destructive annotations: 4 of 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "diadoc_call_method" implies "execute" and declares readOnlyHint instead, contradicting what its own name says it does. functional
- Package version: 0.2.2 → 0.3.0 functional
- 13 Sept 26 +31
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.07 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Tool coverage: 0 functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: 100 functional
- First check of Tool coverage: 100 functional
- 12 Sept 26 0
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Tool coverage: 0 functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: 100 functional
- First check of Tool coverage: 100 functional
- Package version: 0.2.0 → 0.2.2 functional
- 11 Sept 26 36
First indexed and scored.
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/diadoc-mcp-ru@0.3.0
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 | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 31 packages
| Packages resolved | 31 |
|---|---|
| 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 →
diadoc_add_cabinet ~220
Add or update a cabinet (a named set of API credentials), from chat. ⚠️ This puts the key into the chat transcript — requires i_understand_key_goes_to_chat=true. The terminal-free safe alternative is the installer (install.py / double-click), where the key never enters chat. Args: credentials: dict with the required fields for this service ({fields}). For Ozon: {{"client_id": "...", "api_key": "..."}}; for WB: {{"token": "..."}}. name: optional label. If omitted, the cabinet is named after the real shop name fetched from the marketplace (falls back to "main"). i_understand_key_goes_to_chat: must be true to proceed. Saved to ~/.marketplace-mcp/cabinets.json (local, chmod 600), never echoed.
| Name | Type | Req | Description |
|---|---|---|---|
| credentials | object | yes | – |
| i_understand_key_goes_to_chat | boolean | – | – |
| name | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
diadoc_call_method ~168
Execute one READ endpoint from the catalog by operation_id. Target API: https://developer.kontur.ru/doc/diadoc-api. Reads only: nothing here changes data, so it runs without confirmation. To change data use diadoc_write_method, to delete use diadoc_delete_method. Args: operation_id: id from the catalog (see diadoc_search_methods). path_values: values for {placeholders} in the path. query: query-string parameters. body: JSON request body (a few read endpoints take one). Returns JSON: {"ok": true, "status", "data"} or the error envelope.
| Name | Type | Req | Description |
|---|---|---|---|
| body | – | – | – |
| operation_id | string | yes | – |
| path_values | – | – | – |
| query | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
diadoc_check_auth ~56
Check whether the required credentials are present in the environment. Does NOT reveal secret values — only reports which variables are set. Returns JSON: {"ready": bool, "missing": [str], "required": [str]}.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
diadoc_delete_method ~197
Execute one DESTRUCTIVE endpoint: deletes or irreversibly changes data. Target API: https://developer.kontur.ru/doc/diadoc-api. Both confirm_write=true and i_understand_this_modifies_data=true are required; nothing is sent without both. Args: operation_id: id from the catalog (see diadoc_search_methods). path_values: values for {placeholders} in the path. query: query-string parameters. body: JSON request body. confirm_write: must be true. i_understand_this_modifies_data: must be true. Returns JSON: {"ok": true, "status", "data"} or the error envelope.
| Name | Type | Req | Description |
|---|---|---|---|
| body | – | – | – |
| confirm_write | boolean | – | – |
| i_understand_this_modifies_data | boolean | – | – |
| operation_id | string | yes | – |
| path_values | – | – | – |
| query | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
diadoc_delete_raw ~195
Delete data at ANY path, including paths not in the catalog. Target API: https://developer.kontur.ru/doc/diadoc-api. DELETE only. Both confirm_write=true and i_understand_this_modifies_data=true are required. Args: path: full path beginning with '/'. method: DELETE. host: host override; defaults to the service's default host. query: query-string parameters. body: JSON request body. confirm_write: must be true. i_understand_this_modifies_data: must be true. Returns JSON: {"ok": true, "status", "data"} or the error envelope.
| Name | Type | Req | Description |
|---|---|---|---|
| body | – | – | – |
| confirm_write | boolean | – | – |
| host | – | – | – |
| i_understand_this_modifies_data | boolean | – | – |
| method | string | – | – |
| path | string | yes | – |
| query | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
diadoc_describe_method ~51
Return the full catalog record for one endpoint: method, host, path, scope, safety level, pagination style, rate limit, params and doc URL.
| Name | Type | Req | Description |
|---|---|---|---|
| operation_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
diadoc_fetch_all ~197
Auto-paginate a read endpoint and return every row in one response. Handles offset, last_id, cursor (Ozon v4/v5), page and WB lastChangeDate styles. The array path is taken from the catalog automatically. Args: operation_id: a read endpoint from the catalog. query / body / path_values: base parameters (cursor fields are managed). items_path: override the array path (default: the endpoint's own). limit: page size to request. max_items: hard cap to protect context (default 10000). Returns JSON: {"ok", "items", "total_fetched", "pages_fetched", "truncated"}.
| Name | Type | Req | Description |
|---|---|---|---|
| body | – | – | – |
| items_path | – | – | – |
| limit | integer | – | – |
| max_items | integer | – | – |
| operation_id | string | yes | – |
| path_values | – | – | – |
| query | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
diadoc_get_raw ~183
Read ANY endpoint by path, including ones missing from the catalog. Target API: https://developer.kontur.ru/doc/diadoc-api. Safe verbs only (GET, HEAD, OPTIONS). To change data use diadoc_write_raw, to delete use diadoc_delete_raw. Args: path: full path beginning with '/', e.g. "/GetBox". method: safe verb, GET by default. host: host override; defaults to the service's default host. query: query-string parameters. body: JSON request body (rare on reads; some APIs want one). Returns JSON: {"ok": true, "status", "data"} or the error envelope.
| Name | Type | Req | Description |
|---|---|---|---|
| body | – | – | – |
| host | – | – | – |
| method | string | – | – |
| path | string | yes | – |
| query | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
diadoc_get_section ~62
List all endpoints in one section. Args: section: section name (see diadoc_list_sections), e.g. "statistics". Returns JSON list of {operation_id, method, path, safety, summary}.
| Name | Type | Req | Description |
|---|---|---|---|
| section | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
diadoc_list_cabinets ~55
List configured cabinets for this marketplace and which one is active. Returns JSON: {"active": str|null, "cabinets": [names], "fields_needed": [...]}. Secret values are never returned.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
diadoc_list_sections ~22
List API sections and how many catalog endpoints each contains.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
diadoc_map ~83
The big picture: business entities this API covers and the go-to methods for each. Call with no args to see the whole map ("you are here"); pass entity="reviews" (or stocks/prices/orders/…) to list every method of one entity. Use this before guessing — it orients you fast.
| Name | Type | Req | Description |
|---|---|---|---|
| entity | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
diadoc_remove_cabinet ~44
Delete a stored cabinet. If it was active, another becomes active. Args: name: the cabinet to remove.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
diadoc_search_methods ~80
Search the endpoint catalog by keyword (works in Russian and English). Args: query: free text, e.g. "остатки", "stocks", "update price". limit: max results (1-50). Returns JSON list of matching endpoints (best first).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
diadoc_set_key ~223
Change / rotate the API key from chat (e.g. the old one expired or leaked). ⚠️ The key goes into the chat transcript — requires i_understand_key_goes_to_chat=true. The safe, terminal-free alternative is the installer, where the key never enters chat. Use a scoped key and rotate it in the seller cabinet if it was exposed. Args: credentials: dict with the required fields ({fields}). cabinet: which cabinet to update. Default: the active one (so "my key expired" just works). If there is none, the cabinet is named from the marketplace's shop name, else "main". i_understand_key_goes_to_chat: must be true to proceed. On success the key is validated against the marketplace and the shop name is reported. Saved locally (chmod 600), never echoed back.
| Name | Type | Req | Description |
|---|---|---|---|
| cabinet | string | – | – |
| credentials | object | yes | – |
| i_understand_key_goes_to_chat | boolean | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
diadoc_use_cabinet ~52
Switch the active cabinet. Subsequent API calls use its credentials. Args: name: the cabinet to activate (see diadoc_list_cabinets).
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
diadoc_write_method ~178
Execute one WRITE endpoint from the catalog: create or update data. Target API: https://developer.kontur.ru/doc/diadoc-api. Requires confirm_write=true; nothing is sent without it. Irreversible operations live in diadoc_delete_method, reads in diadoc_call_method. Args: operation_id: id from the catalog (see diadoc_search_methods). path_values: values for {placeholders} in the path. query: query-string parameters. body: JSON request body. confirm_write: must be true. Returns JSON: {"ok": true, "status", "data"} or the error envelope.
| Name | Type | Req | Description |
|---|---|---|---|
| body | – | – | – |
| confirm_write | boolean | – | – |
| operation_id | string | yes | – |
| path_values | – | – | – |
| query | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
diadoc_write_raw ~167
Create or update data at ANY path, including paths not in the catalog. Target API: https://developer.kontur.ru/doc/diadoc-api. POST, PUT and PATCH only; requires confirm_write=true. Args: method: POST, PUT or PATCH. path: full path beginning with '/'. host: host override; defaults to the service's default host. query: query-string parameters. body: JSON request body. confirm_write: must be true. Returns JSON: {"ok": true, "status", "data"} or the error envelope.
| Name | Type | Req | Description |
|---|---|---|---|
| body | – | – | – |
| confirm_write | boolean | – | – |
| host | – | – | – |
| method | string | yes | – |
| path | string | yes | – |
| query | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
What is the Диадок MCP (RU) — ЭДО, документы, контрагенты server?
Диадок MCP (RU) — ЭДО, документы, контрагенты is listed in the public MCP registry as io.github.ilyautov/diadoc-mcp-ru. API Диадока в ИИ-ассистенте: документы ЭДО, контрагенты, подписание, МЧД. This page covers its PyPI package (diadoc-mcp-ru).
Is the Диадок MCP (RU) — ЭДО, документы, контрагенты server safe to use?
Диадок MCP (RU) — ЭДО, документы, контрагенты scores 67 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 (RU) — ЭДО, документы, контрагенты server expose?
Диадок MCP (RU) — ЭДО, документы, контрагенты exposes 18 tools: diadoc_check_auth, diadoc_list_sections, diadoc_get_section, diadoc_search_methods, diadoc_map, and 13 more. Their descriptions and schemas cost roughly 2,233 tokens of context every time the server is loaded.
Is the Диадок MCP (RU) — ЭДО, документы, контрагенты server still maintained?
Диадок MCP (RU) — ЭДО, документы, контрагенты 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.