Skip to main content
Glama

Related Servers

Alternatives to agent402-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server providing 11 pay-per-call web intelligence tools (page reading, PDF extraction, RSS parsing, screenshots, summarization, structured data extraction) for AI agents, paid automatically in USDC via the x402 protocol on Base mainnet with no API keys required.
      20 npm
      MIT
    • A
      license
      B
      quality
      F
      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
      66 npm
      1
      MIT
    • 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
    • A
      license
      C
      quality
      F
      maintenance
      MCP server bringing 100+ x402-paid APIs to AI agents (Claude, Cursor, MCP-aware clients). Auto-discovers tools from CDP Bazaar; handles USDC micropayments on Base.
      100
      35 npm
      1
      MIT
    • 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.
      -

    TDQS

    A4.1/5.0

    Scored across 15 tools

    Disambiguation4/5

    Most tools have distinct purposes and the descriptions explicitly cross-reference the alternatives (web.search vs web.news vs web.answer; memory.read vs memory.write). However catalog.search, catalog.find, and route_and_execute all overlap on 'find/reach a tool,' and the discovery-vs-execute boundary requires careful reading to keep straight.

    Naming Consistency4/5

    The set mostly follows a clean namespace.action pattern (browser.render, memory.read, web.search, catalog.call, sellers.list). The lone deviation is route_and_execute, which drops the dotted convention while server.describe and payment.info keep it.

    Tool Count4/5

    15 tools is slightly heavy but justified by the server's dual role as both a flagship tool host and a gateway/broker to an external catalog. A few meta tools (server.describe, payment.info) are lightweight but earn their place for onboarding.

    Completeness4/5

    Core workflows are covered: search/answer/news, render, transcribe, memory read/write, market quote, catalog discovery/calling, routing, and seller listing. Minor gaps: delete is folded into memory.write, and frequently referenced tools (extract, stock-history, memory-recall) are only reachable indirectly via catalog.call.

    Maintenance

    ActivityActive
    ResponsivenessResponsive