Skip to main content
Glama
entroute

EntRoute MCP

Official
by entroute

Related Servers

Alternatives to EntRoute MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Open-source MCP server exposing the Agent402.Tools catalog: 500+ deterministic pay-per-call tools for AI agents, including browser rendering, web search, PDFs, OCR, LLM inference, code execution, live financial/crypto/macro data, SEC EDGAR, and wallet-keyed memory. Free via proof-of-work, or pay per call in USDC across ten chains via the x402 protocol. No API keys, no signups
      15
      8
      AGPL 3.0
    • 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.
      -
    • 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
      33 npm
      1
      MIT
    • 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.
      83 npm
      Apache 2.0
    • A
      license
      A
      quality
      D
      maintenance
      An MCP server that lets your AI coding agent (Claude Code, OpenClaw, Codex, Cursor, etc.) discover and pay on-chain agents registered on ERC-8004, using Coinbase's official x402 protocol. No smart account. No bundler. No relay. Just your EOA, an HTTPS request, and an automatic 402 → sign → retry flow.
      3
      5
      MIT

    TDQS

    A4.3/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clear and distinct purpose: list_capabilities for discovery, discover_paid_api for endpoint search, and call_paid_api for execution. No overlap exists.

    Naming Consistency4/5

    Naming follows a consistent verb_noun pattern (list_capabilities, discover_paid_api, call_paid_api). Slight inconsistency: 'discover' and 'list' are different verbs but both are clear.

    Tool Count5/5

    Three tools cover the entire workflow of discovering and calling paid APIs without unnecessary additions. The count is well-scoped for the domain.

    Completeness4/5

    Covers the full lifecycle: list capabilities, discover endpoints, and call them. Minor gap: no tool for viewing payment history or managing wallets, but that may be out of scope.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive