Skip to main content
Glama
agentc22

x402engine-mcp

by agentc22
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to x402engine-mcp

No user-submitted related servers found.

    Related Servers

    • x402-mcp

      merkleworks
      A
      license
      Not graded
      quality
      F
      maintenance
      MCP server for the x402 protocol that lets AI agents discover and call payment-gated HTTP APIs automatically.
      82 npm
      Apache 2.0

    • AgentPay

      joepangallo
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for AgentPay — the payment gateway for autonomous AI agents. Fund a wallet once, give your agent the key, and it discovers, provisions, and pays for tool APIs on its own. One key, every tool.
      112 npm
      1
      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

    • @melis-ai/x402-tools-mcp

      mizukaizen
      A
      license
      B
      quality
      D
      maintenance
      An MCP server providing 22 pay-per-call utility tools for AI agents (scrape, validate, embed, store, moderate, notify, convert, prevent loops) without accounts or API keys, using USDC payments via the x402 protocol.
      17
      38 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

    B3.3/5.0

    Scored across 22 tools

    Disambiguation3/5

    Several crypto tools overlap: get_crypto_price and get_token_prices both return prices but differ by input (name vs contract), and get_crypto_markets, get_crypto_history, and get_trending_crypto all provide market data. Descriptions help distinguish them, but an agent could easily select the wrong one. Other domains (travel, IPFS, wallets) are clearly separate.

    Naming Consistency4/5

    Most tools follow a verb_noun pattern (transcribe_audio, get_crypto_price, generate_image, search_flights), but a few deviate like service_health (noun_noun) and get_from_ipfs (verb_preposition_noun). The overall style is fairly consistent and readable.

    Tool Count3/5

    With 22 tools, the server is on the heavier side, covering many unrelated domains (audio, crypto, images, travel, IPFS, wallets). It feels like a diverse API collection rather than a focused toolset, but each tool appears to earn a place for its specific purpose.

    Completeness3/5

    Each domain has reasonable but not exhaustive coverage: crypto has price/market/history/trending/search/categories, wallets have balances/transactions/pnl, travel has search but no booking, IPFS has pin/get but no unpin. The surface is usable but has minor gaps that an agent might need to work around.

    Maintenance

    ActivitySlowing
    ResponsivenessUnresponsive

    Resources