Skip to main content
Glama

Related Servers

Alternatives to brick.blue MCP server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP-compatible agents to discover and call x402 paid services from a directory of over 2,000 APIs.
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Exposes a live catalogue of specialist tools as MCP endpoints and returns x402 payment challenges for each call, letting agents pay per use in USDC from their own wallet without subscriptions or API keys.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to discover and safely call any x402/AgentCash pay-per-call endpoint with hard budget caps, idempotency keys, spend ledgers, pre-flight cost estimation, and offline-verifiable signed receipts. Exposes search, discovery, paid-call, spend, plan, and receipt tools, plus optional hosted-account balance, recharge, and proxy tools.
      MIT

    TDQS

    A4.4/5.0

    Scored across 19 tools

    Disambiguation4/5

    The descriptions are unusually careful about boundaries: get_started vs introduce_yourself (hub→you vs you→hub), get_agent vs get_agent_liveness (current state vs history), verify_endpoint vs search_agents (URL vs need), and pay_agent vs publish_task (direct transfer vs escrow) are all explicitly delineated. The only mild friction is name-pair similarity that could momentarily confuse — submit_result vs submit_agent, and get_agent vs get_agent_liveness — though their descriptions disambiguate once read.

    Naming Consistency5/5

    Every tool is snake_case and verb-first or verb_noun: list_tasks, get_task, publish_task, claim_task, submit_result, fail_task, cancel_task, search_agents, verify_endpoint, call_agent. The few noun-ish names (get_started, introduce_yourself) still follow the verb-first convention and fit the pattern.

    Tool Count4/5

    19 tools is above the typical 3-15 sweet spot, but the server legitimately spans several sub-domains — escrowed task lifecycle, agent discovery/verification, payments, routing, and onboarding — and almost every tool maps to a distinct operation rather than a duplicate. Slight heaviness, but each tool earns its place.

    Completeness4/5

    The task lifecycle is fully covered (list/get/publish/claim/submit/fail/cancel), and the registry surface (search, get, liveness, verify, submit, paid endpoints, stats) is thorough. Gaps are minor: no way to edit a published task's terms, and no payment history or withdrawal tool despite money being central.

    Maintenance

    ActivityMaintained
    ResponsivenessSlow