Skip to main content
Glama
agents-trust

Agents Trust MCP

by agents-trust
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Agents Trust MCP

No user-submitted related servers found.

    Related Servers

    • nsgoods workbench MCP

      Nikoble1926
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables read-only queries of the x402 catalogue: checking endpoint payability and prices, finding endpoints by host or keyword, monitoring host drift, and verifying nsgoods signatures offline.
      2
      MIT
    • @vapi-network/mcp by vAPI-Network

      @vapi-network/mcpofficial

      vAPI-Network
      A
      license
      Not graded
      quality
      C
      maintenance
      Lets MCP clients discover x402 APIs, pay for calls from a local non-custodial wallet, and inspect balances and payment receipts.
      9
      Apache 2.0
    • AgentBodega MCP by agentbodegastore

      AgentBodega MCPofficial

      agentbodegastore
      A
      license
      A
      quality
      F
      maintenance
      Enables agents to search and inspect live service offerings, generate x402 payment snippets, and understand blockchain-only balance policies.
      4
      32 npm
      4
      MIT

    • till

      bzdmin
      A
      license
      Not graded
      quality
      B
      maintenance
      Lets agents discover, verify, and inspect x402/B402 payment endpoints on BNB Chain, with read-only tools to list skills, check live counter behavior, and review the settlement tape.
      3 npm
      MIT

    • x402 Atlas

      89rat
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to search and verify machine-payable HTTP 402/x402 APIs using live probe data, providing ranked results by liveness, uptime, price, and trustworthiness.
      -
    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

    A3.6/5.0

    Scored across 4 tools

    Disambiguation4/5

    The four tools mostly target distinct actions: recommend discovers APIs, inspect reads stored evidence for one exact endpoint, receipt looks up settlement, and health reports version. Recommend and inspect could be mildly confused because both deal with API endpoint information, but the descriptions clearly separate discovery/pricing from evidence retrieval without provider calls.

    Naming Consistency3/5

    Recommend and inspect are imperative verbs, while receipt and health are nouns. The names are concise and readable, but the set does not follow a consistent verb_noun or single-convention pattern.

    Tool Count5/5

    Four tools is well-scoped for a focused trust/payment service: discovery, evidence inspection, receipt lookup, and health checking each have a clear role. There is no obvious tool bloat or thinness.

    Completeness4/5

    The surface covers the core lifecycle of finding APIs, inspecting stored evidence, checking payment settlement, and verifying service health. Minor gaps may exist around broader payment/authorization management or listing receipts, but core workflows appear workable.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources