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.
      160 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.
      274
      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.6/5.0

    Scored across 44 tools

    Disambiguation2/5

    The set has clear duplicates and overlapping paths: get_rlusd_quote and get_dex_quote appear functionally identical, and escrow setup offers multiple routes (create_escrow_vault + prepare_escrow vs hire_and_pay vs submit_escrow_transaction vs confirm_escrow_transaction) that can confuse workflow selection. audit_task and evaluate_escrow_work also overlap as AI verification entry points. Many descriptions help, but several boundaries are not clean.

    Naming Consistency4/5

    Nearly all names use snake_case with a predictable verb_noun pattern (get_fees, create_escrow_vault, list_open_jobs, verify_wallet_domain). Minor deviations exist: batch_wallet_trust_scores lacks a leading verb, direct_hire/hire_and_pay mix forms, and identical functions use different names (get_rlusd_quote vs get_dex_quote). Overall the convention is readable and consistent.

    Tool Count2/5

    At 44 tools, the server is well beyond the 3–15 sweet spot and past the 16–25 heavy range. While the domain spans escrow, marketplace, identity, NFTs, and reputation, several tools are convenience duplicates or thin wrappers (hire_and_pay, submit_escrow_transaction, duplicate quote tools), making the surface feel bloated rather than tightly scoped.

    Completeness3/5

    Core workflows are broadly covered: escrow creation/confirmation/evaluation, job posting/bidding/awarding/messaging, trust/KYC/sanctions checks, NFT issuer lookup, and wallet setup. However, lifecycle gaps remain: no escrow cancel/refund/dispute tool, no job edit/cancel or skill delist operation, and no explicit W3C VC verification or NFT issuer registration tool despite those conditions being referenced. These are notable omissions that agents must work around or leave the platform to handle.

    Maintenance

    ActivityActive
    ResponsivenessSlow

    Resources