Skip to main content
Glama
dchu3

x402-agent-mcp

by dchu3
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to x402-agent-mcp

No user-submitted related servers found.

    Related Servers

    • opendexter by Dexter-DAO

      opendexterofficial

      Dexter-DAO
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables AI agents to search, pay for, and call paid APIs using the x402 protocol, with automatic USDC settlement.
      2
      MIT
    • mpp32-mcp-server by MPP32

      mpp32-mcp-serverofficial

      MPP32
      A
      license
      Not graded
      quality
      C
      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.
      234
      MIT

    • x402-json-repair-mcp

      ktcod
      F
      license
      Not graded
      quality
      B
      maintenance
      A small, autonomous, pay-per-call MCP server that AI agents discover and pay for per call, with revenue landing directly in a USDC wallet on Base via the x402 payment protocol.
      -

    • x402farm-mcp

      laurenthalbrun
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that provides AI agents with pay-per-call access to a suite of tools (honeypot check, token market, DeFi yields, etc.) via USDC on Base using the x402 protocol.
      3 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

    A3.9/5.0

    Scored across 8 tools

    Disambiguation4/5

    Each tool has a clearly defined role covering category listing, searching, describing, discovering, health-checking, and fetching. The main overlap is between discover_url and discover_urls, which are the same operation in single and batch form, but this is a reasonable convenience rather than a true ambiguity.

    Naming Consistency4/5

    All tools share the x402_ prefix and most use a verb or verb_noun pattern (list_categories, search, describe, discover_url, crawl_directory, fetch). The exceptions are health, which is a noun, and two discover verbs with slightly different forms, but the overall convention remains predictable.

    Tool Count5/5

    Eight tools is well within the ideal range for this domain. Each tool addresses a distinct stage of discovering, evaluating, and consuming x402 services without excessive redundancy or missing core functions.

    Completeness5/5

    The toolset covers the full lifecycle from discovery (search, crawl, list categories), to verification (health, describe, discover_url), to interaction (fetch with automatic payment handling). No obvious dead ends or missing capabilities are apparent for an agent needing to work with x402 endpoints.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive

    Resources