Skip to main content
Glama
JonasFuchss

x402 Discovery & Trust MCP

by JonasFuchss
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to x402 Discovery & Trust MCP

  • x402-mcp by x402node

    x402-mcpofficial

    x402node
    A
    license
    C
    quality
    F
    maintenance
    MCP server bringing 100+ x402-paid APIs to AI agents (Claude, Cursor, MCP-aware clients). Auto-discovers tools from CDP Bazaar; handles USDC micropayments on Base.
    100
    23 npm
    1
    MIT

Related Servers

  • dyoe-agent-tools-mcp

    bjyoe2016
    A
    license
    A
    quality
    C
    maintenance
    Trust layer for AI agents: 22 pay-per-call x402 tools for scam and fraud checks, payment pre-flight, wallet screening, policy approvals, contact extraction and company research. Free preview with no wallet; paid calls settle in USDC on Base.
    22
    104 npm
    MIT

  • x402-tools

    vera-agent-dev
    A
    license
    A
    quality
    B
    maintenance
    Enables AI agents to pay per call for live package-safety and GitHub merge-readiness trust signals via the x402 protocol.
    3
    MIT

  • ada-wallet

    loveaihq
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI agents to pay x402 endpoints on Cardano through a policy-gated wallet with spend caps, payee allowlists, human approval, and an audit log.
    99 npm
    Apache 2.0

  • x402 MCP Payment

    motok2031
    F
    license
    Not graded
    quality
    C
    maintenance
    Enables AI agents to access paid content by integrating cryptocurrency payments through the x402 protocol, allowing LLMs to verify payments and retrieve paid resources automatically.
    1
    -
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 15 tools

Disambiguation5/5

Each tool targets a distinct action on a distinct resource: watch lifecycle (create/edit/cancel/renew/events), search versus semantic_search, and the trust family (score, bulk, preview, leaderboard). Descriptions explicitly disambiguate overlapping cases, e.g. x402_search tells users to use x402_semantic_search for meaning-based queries, and preview is clarified as a sample pack of score output.

Naming Consistency5/5

All tools follow a uniform x402_-prefixed snake_case convention with a clear domain verb/noun pattern (watch_create, trust_score, semantic_search, find_alternatives). The noun-only names (endpoint_history, ecosystem_stats) still fit the same predictable scheme.

Tool Count5/5

Fifteen tools for a discovery-and-trust domain is well-scoped and each earns its place across the search, trust-scoring, and watch-management surfaces. No redundancy that would bloat the set.

Completeness4/5

The surface covers discovery, trust scoring (single/bulk/preview/leaderboard), history, ecosystem stats, and full watch lifecycle including events. The main gap is a 'list watches' operation — watch_events requires a watch_id, so an agent that loses the id has no way to enumerate its watches.

Maintenance

ActivityActive
ResponsivenessWithin a week

Resources