Skip to main content
Glama
nirholas

x402-mcp

by nirholas
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to x402-mcp

No user-submitted related servers found.

    Related Servers

    • tradex

      benz16107
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables agents to discover and pay for AI services per call via USDC on Solana, supporting marketplace search, listing details, on-chain reputation, wallet info, and paid calls.
      30 npm
      MIT
    • Fluora MCP by fluora-ai

      Fluora MCPofficial

      fluora-ai
      F
      license
      Not graded
      quality
      F
      maintenance
      Enables AI agents to discover and pay for monetized services such as PDF processing and DeFi operations using USDC on the Base blockchain. It provides automatic payment processing and secure local wallet management for seamless integration with MCP-compatible clients.
      8 npm
      -

    • BotWallet MCP Server

      botwallet-co
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to manage USDC wallets on Solana, allowing them to send payments, create invoices, and access paid APIs within human-defined spending limits. It uses threshold signatures to provide agents with financial autonomy while ensuring secure oversight and transaction approval.
      36
      40 npm
      4
      Apache 2.0
    • mpp32-mcp-server by MPP32

      mpp32-mcp-serverofficial

      MPP32
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that allows AI agents to discover and pay for thousands of APIs (x402 on Solana/Base) using a single key, with automatic payment handling and a federated catalog of machine-payable endpoints.
      233
      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.3/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a distinct, non-overlapping purpose: searching services, inspecting costs, paying and calling, and checking wallet balance. No ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern (find_services, inspect_endpoint, pay_and_call, x402_wallet), making them predictable and easy to understand.

    Tool Count5/5

    Four tools is an ideal count for this focused domain—covering discovery, inspection, execution, and wallet status without bloat or deficiency.

    Completeness4/5

    The tool set covers the core payment workflow comprehensively, but lacks session management or history features, which are minor gaps for advanced use cases.

    Maintenance

    ActivityStale
    ResponsivenessSlow

    Resources