Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

ДокиДепо — открытые инструменты склада

REMOTE · DOKIDEPO.RU

Read-only инструменты малого склада: назначение, ограничения и безопасный план первого дня.

Available components

0 this week 88 Trust /100

Last scanned (18 hours ago)

Scores higher than 95% of remote servers

Reachable. Last reached 21 Nov 2026.

Category E-commerce

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 739 tokens (~147/item across 5 items; 5 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 Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 14 Nov 26 0
    • DNSSEC: unverified → fail ▼ security
    • Authorization: unverified → partial ▲ security
    • Injection markers: unverified → pass ▲ security
    • Stability: unverified → pass ▲ security
    • TLS certificate: unverified → pass ▲ security
    • HSTS header: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • Endpoint reachability: unreachable → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
  • 12 Nov 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • DNSSEC: fail → unverified ▼ security
    • Stability: pass → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • HSTS header: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 9 Nov 26 +1
    • Stability: 0.97 → pass security
  • 8 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 7 Nov 26 +1
    • Stability: 0.97 → pass security
  • 6 Nov 26 −1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

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 21 Nov 2026 · Probed https://dokidepo.ru/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=dokidepo.ru CN=YE1,O=Let's Encrypt,C=US 6 Oct 2026 4 Jan 2027 ECDSA 256 ECDSA-SHA384 5011535db4e7a1eda6c3034b9839c56fcb7
SANs: dokidepo.ru
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of dokidepo.ru. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ru. DS published 26734 8 Verified
dokidepo.ru. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff
x-frame-options DENY
referrer-policy same-origin
permissions-policy camera=(self), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://dokidepo.ru/api/mcp Verified 200
http (plaintext) http://dokidepo.ru/api/mcp HTTPS enforced 308 https://dokidepo.ru/api/mcp
MCP tools · 5 exposed · ~681 tokens

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 →

Tool Tokens
get_embed_widget ~171

Используйте, когда редакции или сайту нужен готовый безопасный виджет: текущий остаток, расчёт наценки и маржи, количество к заказу, диагностика узкого места склада или генератор артикулов. Передайте один фиксированный id; сервер вернёт проверенный sandboxed iframe, страницу установки и ограничения. Не принимает HTML, URL или свободный текст. Неизвестный id или лишнее поле дают JSON-RPC -32602 Invalid params.

NameTypeReqDescription
idstringyesstock-balance — приход, расход и остаток; markup-margin — наценка и маржа; purchase-list — количество к заказу; warehouse-bottleneck — диагностика узкого места; sku-generator — артикулы из названий и…
NameTypeReqDescription
safetystringyes–
widgetobjectyes–

No examples provided.

get_first_warehouse_day ~109

Используйте, когда владелец малого склада хочет безопасно проверить ДокиДепо на одном учебном товаре до импорта каталога и приглашения команды. Без аргументов возвращает фиксированную последовательность: места → приёмка → размещение → отбор → упаковка → сверка. Не создаёт организацию, не меняет остатки и не принимает рабочие данные. Любое входное поле даёт JSON-RPC -32602 Invalid params.

Input schema present but exposes no named parameters.

NameTypeReqDescription
safetystringyes–
startUrlstringyes–
stepsarrayyes–

No examples provided.

get_public_tool ~119

Используйте после list_public_tools, когда уже известен точный id нужного инструмента. Возвращает его назначение, входы, результат, ограничения и измеряемую ссылку. id обязателен и должен быть одним из перечисленных значений; неизвестный id или лишнее поле дают JSON-RPC -32602 Invalid params. Не принимает свободный текст, URL, файлы или рабочие данные.

NameTypeReqDescription
idstringyesТочный неизменяемый идентификатор открытого инструмента ДокиДепо.
NameTypeReqDescription
safetystringyes–
toolobjectyes–

No examples provided.

get_publisher_kit ~110

Используйте, когда редакции, сообществу или ИИ-агенту нужно подготовить публикацию о ДокиДепо без сочинения фактов и ссылок. Без аргументов возвращает фиксированные текст, ссылки, обложку, контакт и границы приватности. Не публикует материал и не принимает свободный текст, URL, файлы или данные аудитории. Любое входное поле даёт JSON-RPC -32602 Invalid params.

Input schema present but exposes no named parameters.

NameTypeReqDescription
kitobjectyes–
safetystringyes–

No examples provided.

list_public_tools ~172

Используйте первым, когда нужно подобрать открытый складской инструмент по задаче. Необязательный category фильтрует каталог; без него возвращается all. Результат содержит только проверенные карточки и измеряемые ссылки ДокиДепо. Не выполняет складские операции и не принимает файлы, товары, пароли или коды. Лишнее поле или неизвестная категория дают JSON-RPC -32602 Invalid params.

NameTypeReqDescription
categorystring–Фиксированный фильтр: all — весь каталог; inventory — остатки, закупка и приёмка; labeling — этикетки, штрихкоды и адреса; pricing — цены и маржа; setup — запуск склада; publishing — встраиваемые вид…
NameTypeReqDescription
safetystringyes–
toolsarrayyes–

No examples provided.

Install

How do I install the ДокиДепо — открытые инструменты склада MCP server?

ДокиДепо — открытые инструменты склада is a hosted endpoint at https://dokidepo.ru/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · dokidepo.ru

# add to Claude Code
claude mcp add --transport http ru-dokidepo-public-tools 'https://dokidepo.ru/api/mcp'
Common questions

What is the ДокиДепо — открытые инструменты склада MCP server?

ДокиДепо — открытые инструменты склада is an MCP server listed in the public MCP registry as ru.dokidepo/public-tools. Read-only инструменты малого склада: назначение, ограничения и безопасный план первого дня. This page covers its hosted endpoint (https://dokidepo.ru/api/mcp).

Is the ДокиДепо — открытые инструменты склада MCP server safe to use?

ДокиДепо — открытые инструменты склада scores 88 out of 100 on VerifyMCP. 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 server expose?

ДокиДепо — открытые инструменты склада exposes 5 tools: list_public_tools, get_public_tool, get_first_warehouse_day, get_embed_widget, get_publisher_kit. Their descriptions and schemas cost roughly 681 tokens of context every time the server is loaded.

Does the ДокиДепо — открытые инструменты склада MCP server require authentication?

No. We connected to ДокиДепо — открытые инструменты склада without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the ДокиДепо — открытые инструменты склада MCP server still maintained?

ДокиДепо — открытые инструменты склада is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the ДокиДепо — открытые инструменты склада MCP server?

VerifyMCP ran 13 checks on ДокиДепо — открытые инструменты склада, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.