Skip to main content
Glama

Related Servers

Alternatives to diadoc-mcp-ru

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      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.
      14
      MIT
    • A
      license
      A
      quality
      B
      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.
      14
      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
      50
      1
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to manage eSignature workflows, including creating signing tasks, tracking document status, and managing templates via natural language.
      142
      -
    • -
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI agents to authenticate users, manage calendar events, create meetings, and maintain persistent API sessions for seamless integration with Russian business platforms. Provides comprehensive business productivity capabilities including session management, password operations, and cross-user calendar coordination.
      -

    TDQS

    A4.1/5.0

    Scored across 14 tools

    Disambiguation4/5

    Most tools target clearly distinct actions (e.g., discovery vs. execution vs. cabinet management), but there is some overlap: diadoc_set_key and diadoc_add_cabinet both modify stored credentials, and the discovery tools (map, list_sections, search_methods) offer adjacent overviews. Descriptions largely disambiguate, though an agent could occasionally confuse key rotation with adding/updating a cabinet.

    Naming Consistency5/5

    All tools use the same diadoc_ prefix and consistent snake_case convention, mostly following a verb_noun pattern (check_auth, list_sections, call_method). The single tool 'map' is a minor deviation but still clearly part of the same naming scheme.

    Tool Count5/5

    With 14 tools, the set is well within the ideal 3-15 range and each tool earns its place across three clear areas: catalog discovery, method execution, and credential/cabinet management. No tool feels redundant or artificially padded.

    Completeness5/5

    The surface covers the full operational lifecycle: discovery (list sections, search, map, describe), execution (call method, raw call, auto-pagination), and credential management (check, add, set, use, remove, list). Minor gaps like explicit credential validation are handled indirectly through key-rotation validation.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues