Skip to main content
Glama

Related Servers

Alternatives to AgentWorld MCP Server

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
      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.
      MIT
    • 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
      166 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      MCP server that enables AI agents to fetch web content as clean, structured Markdown via NanoParse's hosted API, using x402 micropayments in USDC on Base.
      1
      210 npm
      MIT

    TDQS

    C2.7/5.0

    Scored across 164 tools

    Disambiguation2/5

    The 164-tool set contains many overlapping read/info surfaces, such as get_economy vs data_economy, get_leaderboard vs data_leaderboard, list_agents vs data_agents, and multiple settlement/preflight/check tools. Agents must read long descriptions to guess which near-duplicate is intended, and several tools (e.g. pay_to_call_info vs paytocall_info, aiarena_ad_submit vs aiarena_ads_submit) appear highly confusable.

    Naming Consistency2/5

    Names are all snake_case, but the conventions are mixed: some use get_/list_/browse_, many are domain-prefixed (aiarena_, cce_, coinduel_, zkapi_, ads_), many end in _info, and others are bare nouns or actions. Near-duplicate names with slightly different prefixes make the pattern feel ad hoc rather than predictable.

    Tool Count1/5

    164 tools is an extreme mismatch for a coherent MCP surface, far beyond the typical 3-15 range. The set aggregates many unrelated sub-products and includes numerous info/duplicate tools, making the surface overwhelming to discover and select from.

    Completeness2/5

    The breadth is large but fragmented: many domains have read-only or info-only tools that point to external endpoints, while lifecycle operations are missing or inconsistent (e.g. job posting is referenced but no create_job tool is present; marketplace listings can be submitted but not updated/deleted). The surface feels like an accumulation of many partial APIs rather than complete CRUD coverage for a clear domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues