Skip to main content
Glama
thebrierfox

The Stall

by thebrierfox
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to The Stall

No user-submitted related servers found.

    Related Servers

    • agentpay

      ronaldanton
      A
      license
      Not graded
      quality
      C
      maintenance
      Pay-per-call AI microservices settled in USDC on Base via the x402 (HTTP 402) protocol. 28 tools including web search, summarization, extraction, code review, deep research, crypto safety, sanctions screening and on-chain data — no accounts or API keys.
      5 npm
      Apache 2.0

    • CorteX402

      Ooak21
      A
      license
      A
      quality
      D
      maintenance
      Pay-per-call x402 data products on Base mainnet — sanctions screening, aviation weather, mortgage rates, US property dossier, title chain, wallet balance, and agent session auth. Every call settles in USDC with an on-chain receipt, no accounts or API keys.
      7
      40 npm
      MIT
    • Funding-mcp by namixai

      Funding-mcpofficial

      namixai
      A
      license
      A
      quality
      C
      maintenance
      Real-time perp market-data for AI trading agents — funding rates, funding-arb signals, open interest, volume, orderbook depth/slippage and oracle families across 25 venues, plus HIP-3 RWA coverage (tokenized stocks, metals, oil) that mainstream aggregators lack. x402-native pay-per-call (USDC on Base): one free funding screener tool + 11 paid tools with auto-pay.
      12
      15 npm
      2
      MIT

    • AI Data Marketplace

      jblaz6335
      A
      license
      A
      quality
      A
      maintenance
      I built this local stdio MCP adapter to discover, preview, and purchase live agent data APIs, including vendor risk, company intelligence, transaction preflight, and EVM reads. Free discovery and previews require no wallet. Optional paid calls settle in Base USDC through x402 v2; auto-pay is disabled by default.
      2
      64 npm
      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.2/5.0

    Scored across 210 tools

    Disambiguation2/5

    With 210 tools, many have overlapping purposes (e.g., multiple crypto mover tools, multiple DeFi yield tools, multiple equity price tools). An agent would struggle to choose between similar tools, and the abundance of 'packs' that combine endpoints further blurs distinctions.

    Naming Consistency3/5

    Tool names use a mostly consistent snake_case pattern and are descriptive, but there is variation between noun-heavy names and occasional verb-initial names (e.g., 'generate-meme', 'roast', 'ping'). The pattern is not fully uniform, but not chaotic.

    Tool Count1/5

    210 tools is far too many for a coherent server. This count overwhelms an agent with choices and indicates a lack of focused scope. The server appears to be a collection of disparate endpoints rather than a curated set for a specific domain.

    Completeness2/5

    While the tool surface covers many areas (crypto, equities, weather, news, etc.), there are significant gaps within each domain (e.g., no full transaction history for wallets, missing certain financial derivatives). The server feels like a grab bag rather than a complete solution for any single domain.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources