Skip to main content
Glama

Related Servers

Alternatives to nooscape-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables agents and capital allocators to query read-only on-chain and venue evidence about a counterparty before paying or hiring it, and about a vault before depositing, with each figure timestamped and sourced.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents and systems to look up an agent endpoint URL and receive a machine-readable trust decision — reliability evidence, endpoint ownership verification, confidence, and reasons — before deciding whether to interact with it. Lookups are read-only, require no API key, and never contact the target endpoint during the check.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables read-only, keyless queries of timestamped, definition-backed data about AI agent payments and activity on Base, including rankings, agent records, detections, metric histories, and evidence-pack pricing, from MCP clients or the terminal.
      6
      25
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to look up token risk verdicts and ERC20 facts, wallet snapshots, gas prices, transaction summaries, and Basename resolution on the Base network. Each call is paid in USDC over x402 from a dedicated wallet the user controls, with per-call price caps and a session budget.
      102 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to get read-only trust verdicts on knowledge records by evaluating evidence maturity, provenance, intended use, risk level, and scope before deciding whether knowledge may be used.
      MIT

    TDQS

    A3.9/5.0

    Scored across 4 tools

    Disambiguation4/5

    search_agents (find) vs get_agent (full record) vs get_agent_history (time-series events) vs check (cross-resource risk facts) are mostly distinct. get_agent and check overlap on facts like evidence level, first-seen and ratings, though check's payment-gated, wallet/url-capable framing helps separate them.

    Naming Consistency4/5

    search_agents, get_agent, get_agent_history follow a clear verb_noun pattern with a consistent agent subject. The bare verb 'check' is a minor deviation but remains readable and unambiguous in context.

    Tool Count4/5

    Four tools is on the lean side but well-matched to a read-only agent-intelligence surface: search, detail, history and risk check. Nothing obviously redundant, though it sits near the thin end.

    Completeness4/5

    Search, single-record retrieval, historical events and a multi-resource risk check give good coverage of the stated lookup domain. Gaps are minor—no dedicated wallet/endpoint listing tools, but check partly covers those via mix.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues