Skip to main content
Glama

Related Servers

Alternatives to a202-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for permissioned, structured agent-to-agent communications, enabling agents to coordinate and negotiate through scoped, typed messages with authentication and audit logging.
      1,004 PyPI
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that gives AI agents the ability to discover, match with, and build relationships with other autonomous agents. Supports agent registration, matchmaking, messaging, shared goals, relationship lifecycle management, and real-time event subscriptions.
      25 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for Pact, an escrow protocol for agent-to-agent commerce, enabling agents to create pacts, fund escrow, deliver work, and settle with an LLM evaluator as dispute backstop.
      13 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides a sovereign, MIT-licensed MCP server for professional-service workflows, running entirely on your infrastructure with Ed25519 cryptographic signing for every action.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for XerraMeca, an independent agent-to-agent orchestration service. It enables managing conversations, turns, leases, and replies between autonomous agents via MCP tools.
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      A sovereign, MIT-licensed MCP server for professional-service workflow tools that runs on your infrastructure with Ed25519 signing, enabling autonomous agents to discover and invoke tools securely.
      MIT

    TDQS

    A4.6/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool addresses a distinct phase of the transaction lifecycle: issuing/verifying mandates, approving specific acts, forming agreements, recording obligation states, retrieving transaction records, and verifying evidence. The descriptions clearly separate these concerns, with no apparent overlap or ambiguity in purpose.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (issue_mandate, verify_mandate, create_agreement, record_obligation, get_transaction_record, verify_evidence, issue_approval). The verbs and nouns are descriptive and match the tool's function, making the API predictable.

    Tool Count5/5

    With 7 tools, the server is well-scoped for its purpose of managing commercial mandates, agreements, and obligations. Each tool has a clear and necessary role in the workflow, and the count is neither too sparse nor overwhelming.

    Completeness4/5

    The core lifecycle is covered: mandate issuance, verification, approval, agreement creation, obligation recording, and evidence verification. However, there is no tool for updating or revoking a mandate, and no explicit final settlement step after acceptance_pending, which are minor gaps that could be worked around but may cause dead ends in some scenarios.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues