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.
      38 npm
      MIT
    • 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
      89 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.
      9 npm
      MIT
    • A
      license
      C
      quality
      D
      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
      47 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.2/5.0

    Scored across 15 tools

    Disambiguation4/5

    Most tools target distinct resources and actions, and descriptions clearly separate web.search, web.news, and web.answer. However, catalog.search and catalog.find both serve tool discovery and could be confused, despite their browse-vs-resolve descriptions.

    Naming Consistency4/5

    The predominant namespace.action pattern (web.search, memory.read, catalog.call) is highly readable and predictable. The deviations are route_and_execute (underscore, no dot) and a few nouns in the action slot (web.news, payment.info), which are minor but noticeable.

    Tool Count5/5

    15 tools is well within the ideal range and appropriately scoped for a server that provides flagship tools, catalog access, payment info, and external routing. Every tool serves a distinct purpose in the broader workflow.

    Completeness4/5

    The flagship set covers search, news, answer, rendering, quotes, transcription, and memory read/write. The memory descriptions reference memory-recall and memory-remember as separate tools not included, which is a minor gap but one agents could work around via catalog.call.

    Maintenance

    ActivityActive
    ResponsivenessResponsive