Skip to main content
Glama
eamwhite1

AgentTrust

by eamwhite1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to AgentTrust

No user-submitted related servers found.

    Related Servers

    • --

      eamwhite1
      A
      license
      Not graded
      quality
      A
      maintenance
      --
      MIT

    • xpay

      xona-labs
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server for agentic commerce, enabling AI agents to discover services, make x402 payments with USDC across multiple chains, and manage crypto wallets and token swaps.
      415 npm
      1
      MIT

    • AgentPay

      joepangallo
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for AgentPay — the payment gateway for autonomous AI agents. Fund a wallet once, give your agent the key, and it discovers, provisions, and pays for tool APIs on its own. One key, every tool.
      112 npm
      1
      MIT

    • mcp-dev-brasil

      codespar
      A
      license
      Not graded
      quality
      C
      maintenance
      37 MCP servers for agentic commerce and Brazilian services. Covers Stripe ACP, x402 (Coinbase), AP2 (Google), Google UCP, plus 14 traditional Brazilian payment rails, fiscal, banking, communication, logistics, ERP, identity, and crypto APIs. ~480 tools. Supports stdio and Streamable HTTP.
      271
      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

    A3.9/5.0

    Scored across 40 tools

    Disambiguation3/5

    Most tools target distinct resources and actions, but several clusters overlap: get_rlusd_quote and get_dex_quote both return XRP-RLUSD DEX quotes, audit_task and evaluate_escrow_work both perform AI audits, and list_marketplace_jobs vs list_open_jobs sound near-identical. Descriptions are detailed enough to disambiguate in most cases, but an agent could easily misroute these calls.

    Naming Consistency5/5

    All 40 tools use snake_case verb-first names (get_, create_, list_, check_, verify_, submit_, etc.), which makes the large surface predictable and searchable. Even convenience tools like hire_and_pay and explain_agenttrust_trust_model follow recognizable phrasing consistent with the rest of the set.

    Tool Count2/5

    40 tools is a large surface for one MCP server and falls into the 25+ 'too many' band. Many are justified by the broad escrow-plus-marketplace-plus-trust domain, but there is visible redundancy such as get_rlusd_quote vs get_dex_quote and create_escrow_vault vs hire_and_pay that could be consolidated.

    Completeness4/5

    The core escrow lifecycle, marketplace job flow, and wallet trust/verification workflows are well covered, including claims, bids, AI evaluation, and payment release. Obvious gaps are minor but real: there is no way to list all escrows, cancel or dispute an escrow, or update/close marketplace listings and skill listings.

    Maintenance

    ActivityActive
    ResponsivenessSlow

    Resources