Skip to main content
Glama
hypeprinter007-stack

anchor-x402-mcp

by hypeprinter007-stack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to anchor-x402-mcp

No user-submitted related servers found.

    Related Servers

    • 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.
      4 npm
      MIT

    • x402-bazaar-mcp

      sukrutkrdg
      A
      license
      B
      quality
      B
      maintenance
      MCP server exposing x402 Bazaar's paid Base APIs (token risk/honeypot, prices, gas, wallet intel, tx decode + AI utilities) as agent tools. Your agent pays per call in USDC over x402 — no API keys, no signup.
      17
      246 npm
      1
      MIT

    • x402-api

      fernsugi
      A
      license
      A
      quality
      D
      maintenance
      MCP server for pay-per-call DeFi and crypto data via x402 micropayments on Base. 8 endpoints: token prices, TVL, funding rates, token security, gas tracker, whale monitoring, wallet profiling, and yield scanning.
      8
      25 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
    • 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

    A3.7/5.0

    Scored across 14 tools

    Disambiguation2/5

    Multiple clusters have fuzzy boundaries: intel_wallet subsumes screen_wallet's sanctions verdict, roast/aura/grade all accept the same universal target inputs, and anchor_hash/attest_decision/oracle all produce dual-chain anchored proofs with only subtle workflow differences. Descriptions carry some disambiguating detail, but an agent could easily misselect between several pairs.

    Naming Consistency2/5

    Seven tools follow a clean verb_noun snake_case pattern (anchor_hash, decode_tx, parse_datetime), but the set also mixes in noun_noun names (token_price, intel_wallet) and five bare single-word names (roast, oracle, tldr, aura, grade). The lack of a uniform convention makes the tool surface feel like two or three different servers bolted together.

    Tool Count4/5

    14 tools is within a reasonable band and none are strictly redundant duplicates. However, the count is slightly inflated by unrelated mini-domains — anchoring infrastructure, wallet/chain data utilities, and LLM entertainment — which dilutes the server's focus.

    Completeness3/5

    For a server whose core promise is cryptographic proof, the anchor-and-prove lifecycle has an obvious gap: there is no verify_anchor or anchor-status tool to check that a previously anchored hash still exists on-chain, forcing agents to work around via decode_tx or explorer URLs. Individual utilities like resolve_name and token_price feel complete, but the wallet screening surface is awkwardly split between screen_wallet and intel_wallet.

    Maintenance

    ActivityActive
    ResponsivenessSlow

    Resources