Skip to main content
Glama
Sign In
402MCP

402MCP

by 402MCP
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to 402MCP

No user-submitted related servers found.

    Related Servers

    • metered-mcp

      notecash
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to make per-call paid tool requests over HTTP 402, with request-bound payments and replay protection, while returning auditable provenance and self-checks for every answer.
      MIT

    • Interline

      Choppaaahh
      A
      license
      A
      quality
      F
      maintenance
      A neutral, non-custodial payment router for AI agents: it discovers which payment rails a paid endpoint accepts (x402 on Base/EVM, Solana, MPP), then pays across them using the caller's own wallet key. Three tools — discover_payment_rails, pay_for_resource, payment_history.
      4
      MIT

    • tryx402

      crypto-yannso
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to discover and safely call any x402/AgentCash pay-per-call endpoint with hard budget caps, idempotency keys, spend ledgers, pre-flight cost estimation, and offline-verifiable signed receipts. Exposes search, discovery, paid-call, spend, plan, and receipt tools, plus optional hosted-account balance, recharge, and proxy tools.
      MIT

    • tab

      paidwithtab
      A
      license
      Not graded
      quality
      B
      maintenance
      Exposes MCP tools that let an agent search a catalog, inspect a paid service's pricing, fetch it with payment handled automatically, and check its remaining budget and active spending limits. Payments are authorized against a signed mandate from the owner, so agents can buy API access over HTTP 402 without ever holding the owner's private key.
      563 npm
      MIT

    • mcp.cashu.exchange

      Amperstrand
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to discover payable real-world services — such as EV charging and food — through a unified registry and downstream gateway, then complete payments via swappable rails. Exposes tools for listing services and federated downstream servers, searching nearby chargers, and obtaining payment quotes or card credentials for agent-driven checkout.
      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
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A4.2/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct action within the HTTP 402 workflow: decoding a challenge, probing a URL, fetching protocol reference, searching the registry, getting a specific solution, getting the top-ranked solution, and recommending by requirements. The solution-retrieval tools are differentiated by input and purpose, so an agent can select appropriately.

    Naming Consistency5/5

    All seven names use snake_case with a clear verb_noun pattern (decode_402_challenge, get_solution, search_402_solutions, etc.). The numeric token 402 is consistently placed, making the set predictable.

    Tool Count5/5

    Seven tools is well within the ideal 3-15 range for a focused decision-support server. Each tool has a clear role in the 402 workflow, with no redundant or filler entries.

    Completeness4/5

    The surface covers challenge decoding, probing, scheme reference, solution search, top-solution retrieval, targeted recommendation, and detailed solution retrieval, which is strong coverage for decision support. Minor gaps remain around payment execution, receipt or credential verification after payment, and registry mutation, but these may be intentionally out of scope.

    Maintenance

    ActivityMaintained
    ResponsivenessLimited data

    Resources