Skip to main content
Glama
ilyautov

chestny-znak-mcp-ru

by ilyautov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to chestny-znak-mcp-ru

No user-submitted related servers found.

    Related Servers

    • @woyax/mcp-chestnyi-znak

      woyaxnini
      A
      license
      A
      quality
      D
      maintenance
      MCP 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.
      10
      51 npm
      3
      -

    • sbis-mcp-ru

      ilyautov
      A
      license
      A
      quality
      A
      maintenance
      SBIS (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.
      18
      51 PyPI
      5
      MIT

    • wildberries-mcp-ru

      ilyautov
      A
      license
      A
      quality
      A
      maintenance
      Wildberries 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.
      25
      31 PyPI
      2
      MIT

    • yandex-market-mcp-ru

      ilyautov
      A
      license
      A
      quality
      A
      maintenance
      Yandex 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.
      26
      26 PyPI
      2
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.2/5.0

    Scored across 18 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count4/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources