Skip to main content
Glama
Sign In
nohumans-mcp

nohumans-mcp

by jalcodev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to nohumans-mcp

No user-submitted related servers found.

    Related Servers

    • x402 Atlas

      89rat
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to search and verify machine-payable HTTP 402/x402 APIs using live probe data, providing ranked results by liveness, uptime, price, and trustworthiness.
      -

    • Paddock

      unblinkr
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to verify that an x402 API is live, real, and fairly priced before authorizing a payment, and to query live market data on agent commerce across Base and Solana. Exposes twelve tools covering pre-payment checks, provider ranking, liveness lookups, market snapshots and diffs, circular-settlement and whale signals, token metrics, provider revenue, and monthly report data, with free, free-key, and paid x402 tiers.
      MIT

    • agent-tools-mcp

      JoursBleu
      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

    • x402-discovery-mcp

      rplryan
      A
      license
      A
      quality
      D
      maintenance
      Discovers and routes across 251+ x402-enabled payment services with smart routing strategies (cheapest, fastest, most trusted) and signed attestations. Provides real-time health monitoring, facilitator compatibility checks, and service quality scoring for the x402 agent payment ecosystem.
      5
      4
      MIT

    • x402-discovery

      rplryan
      A
      license
      Not graded
      quality
      D
      maintenance
      Discovers and queries x402-payable APIs at runtime — enables autonomous agents to find, evaluate, and pay for services via USDC micropayments on Base without API keys or subscriptions.
      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

    A4.1/5.0

    Scored across 4 tools

    Disambiguation4/5

    Each tool has a clear primary axis: search by need, fetch by id, resolve by URL, and read aggregate demand terms. The only friction is between get_service_details and resolve_endpoint, since resolve_endpoint also returns 'the listing's full record' for a known URL, so an agent holding both an id and a URL could hesitate between them. Descriptions do enough to resolve this in practice.

    Naming Consistency4/5

    Three tools follow a clean verb_noun snake_case pattern (find_paid_service, get_service_details, resolve_endpoint). The fourth, what_agents_are_asking_for, breaks the pattern with a full question-phrase name, which is memorable and readable but inconsistent with the rest of the set.

    Tool Count4/5

    Four read-only tools for a directory search/vetting server is tight and well-scoped, with no filler tools. It sits near the thin end of the range, and a couple of capabilities (e.g. listing/comparing) are absent rather than extra.

    Completeness4/5

    The discover → inspect → verify lifecycle is covered: search, detail by id, resolve an externally held URL, plus a seller-side demand signal. The obvious gap is that the surface is purely read-only — there is no tool to submit/register a listing or to actually probe/sample a paid endpoint, which the descriptions repeatedly gesture at ('has_sample', 'a cheap preview exists') without exposing.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Resources