Skip to main content
Glama
JonasFuchss

x402 Endpoint Trust

by JonasFuchss
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to x402 Endpoint Trust

  • x402-mcp by x402node

    x402-mcpofficial

    x402node
    A
    license
    C
    quality
    D
    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
    47 npm
    1
    MIT

Related Servers

  • 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.
    1,341 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
    -

  • Caravan MCP

    OJ-IRO
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI clients to discover, trust-check, and pay for Algorand x402 services in USDC, with policy-guarded spending, relay fallback, and an audit ledger.
    2 npm
    MIT

  • x402 Ads MCP

    forgemeshlabs
    A
    license
    A
    quality
    A
    maintenance
    x402 Ads lets AI agents buy and verify ad placements with per-request USDC payments. Agents can discover inventory, submit campaign context, receive structured placement options, and pay through x402 without API keys or accounts. Built for autonomous promotion, attribution, and pay-per-action agent commerce.
    7
    76 npm
    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

A4.5/5.0

Scored across 13 tools

Disambiguation5/5

Each tool has a clearly distinct responsibility: single scoring, bulk scoring, history, discovery via search/alternatives/leaderboard, ecosystem stats, and watch lifecycle (create, events, edit, cancel, renew). The only potential overlap between trust_score and trust_bulk is explicitly differentiated by one vs. many endpoints.

Naming Consistency5/5

All tools follow a consistent x402_ prefix with descriptive snake_case names using a noun or verb-noun pattern (trust_score, watch_create, semantic_search). No mixing of conventions or vague generic verbs; the naming is predictable and self-explanatory.

Tool Count5/5

13 tools is well within the ideal 3-15 range for a specialized trust/monitoring service. Each tool serves a distinct function without redundancy, covering scoring, discovery, history, ecosystem context, and watch management.

Completeness5/5

The surface covers the full workflow: discovery (semantic_search, alternatives, leaderboard), evaluation (trust_score, trust_bulk, preview), history (endpoint_history), monitoring (watch lifecycle + events), and market context (ecosystem_stats). No obvious gaps exist for the service's purpose of assessing and monitoring x402 endpoints.

Maintenance

ActivityActive
ResponsivenessNo issues

Resources