chestny-znak-mcp-ru
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CRPT_TOKEN | Yes | Токен ГИС МТ (Честного знака), выдаётся в обмен на данные, подписанные КЭП. Живёт около 10 часов. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| crpt_check_authA | 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]}. |
| crpt_list_sectionsA | List API sections and how many catalog endpoints each contains. |
| crpt_get_sectionA | 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}. |
| crpt_search_methodsA | 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). |
| crpt_mapA | 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. |
| crpt_describe_methodB | Return the full catalog record for one endpoint: method, host, path, scope, safety level, pagination style, rate limit, params and doc URL. |
| crpt_call_methodA | 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. |
| crpt_write_methodA | 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. |
| crpt_delete_methodA | 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. |
| crpt_get_rawA | 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. |
| crpt_write_rawA | 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. |
| crpt_delete_rawA | 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. |
| crpt_fetch_allA | 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"}. |
| crpt_list_cabinetsA | 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. |
| crpt_add_cabinetA | 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. |
| crpt_set_keyA | 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. |
| crpt_use_cabinetA | Switch the active cabinet. Subsequent API calls use its credentials. Args: name: the cabinet to activate (see crpt_list_cabinets). |
| crpt_remove_cabinetA | Delete a stored cabinet. If it was active, another becomes active. Args: name: the cabinet to remove. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 18 tools
Each tool has a clearly distinct role: catalog discovery (describe, list sections, get section, search, map), execution (read, write, delete via catalog or raw path, fetch all), and credential/cabinet management (check, list, add, set key, use, remove). Though several tools browse the catalog, their inputs and outputs are differentiated well enough that an agent should not confuse them.
All tool names share the consistent crpt_ prefix and a snake_case verb_noun pattern (list_sections, get_section, search_methods, call_method, add_cabinet, remove_cabinet). The only slightly off-pattern name is crpt_map, but it still fits the discoverability theme and does not break overall consistency.
At 18 tools the server is on the heavier side, but each tool serves a distinct purpose across catalog introspection, generic API execution, raw-path fallback, pagination, and credential management. This is slightly above the ideal 3-15 range but remains justified for the server's broad scope.
The tool surface covers the full workflow: discovering endpoints, invoking reads/writes/deletes safely, bypassing catalog gaps via raw calls, fetching large result sets, and managing multiple credential cabinets. There are no obvious dead ends for the stated purpose of working with the Честный знак API.