Skip to main content
Glama
the402ai

the402-mcp-server

by the402ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to the402-mcp-server

No user-submitted related servers found.

    Related Servers

    • xpay

      xona-labs
      A
      license
      Not graded
      quality
      D
      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.
      335 npm
      1
      MIT
    • minia2a-mcp by minia2a-org

      minia2a-mcpofficial

      minia2a-org
      A
      license
      Not graded
      quality
      F
      maintenance
      MCP server for the x402 micropayment marketplace minia2a.uk, enabling AI agents to discover, call, and pay for 1,700+ services using USDC micropayments with no API keys or subscriptions. Supports registration, credits, service browsing, and autonomous calling with Claude Code auto-mode.
      759 npm
      1
      MIT
    • 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
      51 npm
      1
      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 30 tools

    Disambiguation3/5

    There is some ambiguity between 'purchase_service' and 'subscribe_to_plan', 'manage_product' covers multiple actions (create/update/delete) which could be split, and 'referrals' bundles multiple sub-actions. However, most tools are targeted at distinct resources/actions (e.g., thread operations, service CRUD).

    Naming Consistency4/5

    Most tools follow the verb_noun pattern (e.g., get_service, create_service, list_purchases, update_profile). Minor deviations include 'referrals' (noun instead of verb) and 'balance_history' (noun instead of check_balance), but the pattern is largely consistent.

    Tool Count4/5

    30 tools is on the higher end but justified given the server covers multiple domains (services, subscriptions, products, threads, payments, profiles, platform info). The count is dense but not excessive for the breadth.

    Completeness5/5

    The tool surface covers the full lifecycle: listing services, purchasing, negotiating, delivering, verifying, canceling; managing subscriptions and products; handling balance and earnings; and viewing platform info. No obvious gaps for the stated purpose of executing transactions via the402.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources