chestny-znak-mcp-ru
Related Servers
Alternatives to chestny-znak-mcp-ru
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables Russian product marking verification via Chestny ZNAK/CRPT APIs, including authenticity checks, product details, batch checks, and authorized GTIN/CIS lookups.562 npm5MIT
- FlicenseAqualityDmaintenanceMCP server for Russia's Chestnyi Znak product labelling system, allowing AI assistants to query marking codes, documents, warehouse balances, and participant data via natural language.1050 npm3-
- AlicenseAqualityAmaintenanceSBIS (Saby) API for AI assistants: documents and their workflow stages, electronic signature, certificates, employees and organizations. 45 methods, each with a read/write/destructive safety class.1846 PyPI6MIT
- AlicenseAqualityAmaintenanceKontur Diadoc API for AI assistants: legally significant document exchange, signing, counteragents, machine-readable powers of attorney and docflow status. 114 methods, each with a read/write/destructive safety class.1828 PyPI3MIT
- AlicenseAqualityAmaintenanceWildberries seller API in your AI assistant: sales and stocks, product cards, prices and promotions, financial reports and reviews. 307 methods across all 17 Wildberries hosts live in a YAML catalog the server executes, the agent searches it in plain language, and every method carries an access class so writes and irreversible calls ask for confirmation.2530 PyPI4MIT
- AlicenseAqualityAmaintenanceYandex Market Partner API in your AI assistant: orders and returns, products and cards, prices and tariffs, reports, reviews and chats. 165 methods live in a YAML catalog the server executes, the agent searches it in plain language, and every method carries an access class so writes and irreversible calls ask for confirmation.2636 PyPI3MIT
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.