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.

Честный знак MCP (RU) — коды маркировки, ГИС МТ, СУЗ

PYPI · CHESTNY-ZNAK-MCP-RU

API Честного знака в ИИ-ассистенте: коды маркировки, эмиссия в СУЗ, отчёты

−20 this week 72 Trust /100

Last scanned (21 hours ago)

Scores higher than 68% of PyPI servers

Category E-commerce

Trust breakdown (7 categories)

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 setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 0 of 30 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to ilyautov/chestny-znak-mcp-ru). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 50 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2303 tokens (~127/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 Management67
  • Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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; "crpt_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
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.

  • 4 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 3 Nov 26 −5
    • Stability: pass → 0.63 functional
  • 1 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 31 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
  • 28 Oct 26 +1
    • Stability: 0.97 → pass security
  • 27 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 21 Oct 26 +1
    • Stability: 0.97 → pass security
  • 20 Oct 26 −1
    • Stability: pass → 0.97 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 4 Nov 2026 · Analysed pypi/chestny-znak-mcp-ru@0.3.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo ilyautov/chestny-znak-mcp-ru
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/ilyautov/chestny-znak-mcp-ru/.github/workflows/publish-pypi.yml@refs/tags/v0.3.0
Rekor log index 2831867742
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:ebad58292dc92f0b79566b5d4e8f5ea4d6db29029e119762eafaf0ba6477a437

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 30 packages
Packages resolved 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 18 exposed · ~2,303 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
crpt_add_cabinet ~219

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.

NameTypeReqDescription
credentialsobjectyes–
i_understand_key_goes_to_chatboolean––
namestring––
NameTypeReqDescription
resultstringyes–

No examples provided.

crpt_call_method ~180

Execute one READ endpoint from the catalog by operation_id. Target API: ГИС МТ и СУЗ «Честный знак» (markirovka.crpt.ru, suzgrid.crpt.ru). Reads only: nothing here changes data, so it runs without confirmation. To change data use crpt_write_method, to delete use crpt_delete_method. Args: operation_id: id from the catalog (see crpt_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.

NameTypeReqDescription
body–––
operation_idstringyes–
path_values–––
query–––
NameTypeReqDescription
resultstringyes–

No examples provided.

crpt_check_auth ~55

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.

NameTypeReqDescription
resultstringyes–

No examples provided.

crpt_delete_method ~211

Execute one DESTRUCTIVE endpoint: deletes or irreversibly changes data. Target API: ГИС МТ и СУЗ «Честный знак» (markirovka.crpt.ru, suzgrid.crpt.ru). 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 crpt_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.

NameTypeReqDescription
body–––
confirm_writeboolean––
i_understand_this_modifies_databoolean––
operation_idstringyes–
path_values–––
query–––
NameTypeReqDescription
resultstringyes–

No examples provided.

crpt_delete_raw ~210

Delete data at ANY path, including paths not in the catalog. Target API: ГИС МТ и СУЗ «Честный знак» (markirovka.crpt.ru, suzgrid.crpt.ru). 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.

NameTypeReqDescription
body–––
confirm_writeboolean––
host–––
i_understand_this_modifies_databoolean––
methodstring––
pathstringyes–
query–––
NameTypeReqDescription
resultstringyes–

No examples provided.

crpt_describe_method ~50

Return the full catalog record for one endpoint: method, host, path, scope, safety level, pagination style, rate limit, params and doc URL.

NameTypeReqDescription
operation_idstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

crpt_fetch_all ~196

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"}.

NameTypeReqDescription
body–––
items_path–––
limitinteger––
max_itemsinteger––
operation_idstringyes–
path_values–––
query–––
NameTypeReqDescription
resultstringyes–

No examples provided.

crpt_get_raw ~199

Read ANY endpoint by path, including ones missing from the catalog. Target API: ГИС МТ и СУЗ «Честный знак» (markirovka.crpt.ru, suzgrid.crpt.ru). Safe verbs only (GET, HEAD, OPTIONS). To change data use crpt_write_raw, to delete use crpt_delete_raw. Args: path: full path beginning with '/', e.g. "/api/v3/ping". 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.

NameTypeReqDescription
body–––
host–––
methodstring––
pathstringyes–
query–––
NameTypeReqDescription
resultstringyes–

No examples provided.

crpt_get_section ~60

List all endpoints in one section. Args: section: section name (see crpt_list_sections), e.g. "statistics". Returns JSON list of {operation_id, method, path, safety, summary}.

NameTypeReqDescription
sectionstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

crpt_list_cabinets ~54

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.

NameTypeReqDescription
resultstringyes–

No examples provided.

crpt_list_sections ~21

List API sections and how many catalog endpoints each contains.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

crpt_map ~82

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.

NameTypeReqDescription
entitystring––
NameTypeReqDescription
resultstringyes–

No examples provided.

crpt_remove_cabinet ~43

Delete a stored cabinet. If it was active, another becomes active. Args: name: the cabinet to remove.

NameTypeReqDescription
namestringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

crpt_search_methods ~79

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).

NameTypeReqDescription
limitinteger––
querystringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

crpt_set_key ~222

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.

NameTypeReqDescription
cabinetstring––
credentialsobjectyes–
i_understand_key_goes_to_chatboolean––
NameTypeReqDescription
resultstringyes–

No examples provided.

crpt_use_cabinet ~50

Switch the active cabinet. Subsequent API calls use its credentials. Args: name: the cabinet to activate (see crpt_list_cabinets).

NameTypeReqDescription
namestringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

crpt_write_method ~190

Execute one WRITE endpoint from the catalog: create or update data. Target API: ГИС МТ и СУЗ «Честный знак» (markirovka.crpt.ru, suzgrid.crpt.ru). Requires confirm_write=true; nothing is sent without it. Irreversible operations live in crpt_delete_method, reads in crpt_call_method. Args: operation_id: id from the catalog (see crpt_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.

NameTypeReqDescription
body–––
confirm_writeboolean––
operation_idstringyes–
path_values–––
query–––
NameTypeReqDescription
resultstringyes–

No examples provided.

crpt_write_raw ~182

Create or update data at ANY path, including paths not in the catalog. Target API: ГИС МТ и СУЗ «Честный знак» (markirovka.crpt.ru, suzgrid.crpt.ru). 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.

NameTypeReqDescription
body–––
confirm_writeboolean––
host–––
methodstringyes–
pathstringyes–
query–––
NameTypeReqDescription
resultstringyes–

No examples provided.

Install

How do I install the Честный знак MCP (RU) — коды маркировки, ГИС МТ, СУЗ server?

Честный знак MCP (RU) — коды маркировки, ГИС МТ, СУЗ runs locally as a PyPI package, launched with uvx chestny-znak-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 · chestny-znak-mcp-ru

# add to Claude Code
claude mcp add ilyautov-chestny-znak-mcp-ru -- uvx chestny-znak-mcp-ru
Common questions

What is the Честный знак MCP (RU) — коды маркировки, ГИС МТ, СУЗ server?

Честный знак MCP (RU) — коды маркировки, ГИС МТ, СУЗ is listed in the public MCP registry as io.github.ilyautov/chestny-znak-mcp-ru. API Честного знака в ИИ-ассистенте: коды маркировки, эмиссия в СУЗ, отчёты. This page covers its PyPI package (chestny-znak-mcp-ru).

Is the Честный знак MCP (RU) — коды маркировки, ГИС МТ, СУЗ server safe to use?

Честный знак MCP (RU) — коды маркировки, ГИС МТ, СУЗ scores 72 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. Its build provenance is signed and verified. 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: crpt_check_auth, crpt_list_sections, crpt_get_section, crpt_search_methods, crpt_map, and 13 more. Their descriptions and schemas cost roughly 2,303 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 4 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 (RU) — коды маркировки, ГИС МТ, СУЗ server under?

Честный знак MCP (RU) — коды маркировки, ГИС МТ, СУЗ declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.