Skip to main content
Glama

Related Servers

Alternatives to diadoc-mcp-ru

No user-submitted related servers found.

    Related Servers

    • 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
    • A
      license
      A
      quality
      A
      maintenance
      VK API for AI assistants: wall posts, communities, messages, market items, ads and stats. 373 methods in one catalog, each with a read/write/destructive safety class; the agent searches methods in plain language instead of receiving 373 tools.
      18
      57 PyPI
      1
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to manage document signing workflows via natural language, including creating envelopes, uploading documents, analyzing contracts, and verifying blockchain anchors.
      8
      40 npm
      1
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to manage eSignature workflows, including creating signing tasks, tracking document status, and managing templates via natural language.
      142
      -
    • A
      license
      A
      quality
      A
      maintenance
      Avito business API in your AI assistant: listings and statistics, buyer messenger, orders and Avito Delivery, bulk upload, promotion and reviews. 64 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.
      30
      43 PyPI
      2
      MIT

    TDQS

    A4/5.0

    Scored across 18 tools

    Disambiguation3/5

    There is meaningful overlap among the catalog discovery tools (list_sections, get_section, search_methods, map, describe_method) and between the catalog execution methods and raw-path execution methods (call_method vs get_raw, write_method vs write_raw). Descriptions do clarify the differences, but an agent could easily hesitate or misselect when deciding which discovery or execution tool to use.

    Naming Consistency4/5

    The tools all share the diadoc_ prefix and mostly follow a verb_noun pattern (list_sections, add_cabinet, delete_method). A few deviations exist, such as diadoc_map (no verb) and diadoc_fetch_all, but overall the naming is predictable and readable.

    Tool Count4/5

    18 tools is on the heavier side but each tool serves a distinct layer: catalog discovery, safe execution, destructive execution, raw fallback, pagination, and cabinet/auth management. The count is slightly over the ideal range but justified by the server's broad scope.

    Completeness5/5

    The tool surface covers the full lifecycle: credential checking, cabinet management, key rotation, catalog exploration, read/write/delete operations, raw endpoint access for uncataloged paths, and pagination. The raw execution tools guarantee that no API endpoint is unreachable, making the surface effectively complete for the stated purpose.

    Maintenance

    ActivityNo data
    ResponsivenessNo issues