Skip to main content
Glama
fernsugi

x402-api

by fernsugi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to x402-api

No user-submitted related servers found.

    Related Servers

    • x402farm-mcp

      laurenthalbrun
      A
      license
      Not graded
      quality
      D
      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.
      6 npm
      MIT

    • x402 Crypto MCP Server

      yunaremaia
      A
      license
      A
      quality
      B
      maintenance
      MCP server that aggregates x402 crypto services as tools for AI agents, providing prices, sentiment, funding rates, and technical indicators with x402 pay-per-call on Base.
      6
      1,535 npm
      MIT

    • AlphaPipeline

      parkyucheol-del
      A
      license
      A
      quality
      A
      maintenance
      Pay-per-call ($0.005-$0.03 USDC) market, on-chain, and prediction-market data API for AI agents and trading bots via x402 — no signup, no API key. Remote MCP server, 18 tools: token security (honeypot/liquidity/counterfeit checks), Hyperliquid oracle-gap risk, kimchi premium, funding APR, DEX slippage, Polymarket arbitrage/liquidity audits, Hyperliquid HIP-4 odds.
      2
      18
      1
      MIT
    • oom-x402-mcp by OrdersOfMagnitudeLLC

      oom-x402-mcpofficial

      OrdersOfMagnitudeLLC
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server exposing 1,000+ pay-per-call API endpoints across agent infrastructure (memory, coordination, secrets, verification), data, compute, finance, weather, geography, and reference categories — payments via x402 protocol in USDC on Base.
      -
    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.1/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a clearly distinct data domain: spot prices, gas, DEX quotes, token security, whale holders, yields, funding rates, and wallet profiles. The descriptions explicitly state what each returns and what it excludes, leaving no ambiguity about when to use one over another.

    Naming Consistency4/5

    All names use snake_case and follow a verb_noun pattern, but the verb set is mixed (get_, scan_, track_, profile_). The variety is semantically justified by each tool's purpose, though it is not a single uniform pattern.

    Tool Count5/5

    Eight tools is an ideal size for a crypto data API, covering diverse data needs without redundancy. Each tool earns its place by providing a distinct data type.

    Completeness4/5

    The surface covers market data, security, yields, funding, and wallet basics, which is strong for a micropayment API. Minor gaps exist, such as historical price data and deeper wallet analytics, but the descriptions acknowledge provider limits and agents can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources