Skip to content
x402 Directory logo

x402 Directory MCP server

Which servers in the official MCP registry are x402 Directory's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-26

← Back to x402 Directory

Whose server it is
  • Registry namedirectory.nohumans/registryverified in the MCP registry

The registry name sits under nohumans.directory. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-26
  • Stateanswerschecked 2026-10-26
  • Tools4
  • Server calls itselfnohumans-directory
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-26 the server answered initialize and tools/list without a sign-in. First answer in 162 ms.

Should an agent connect itNot proven either way yet
  • Its tools do every use case we checked: search paid x402 services by the need they cover; look up a service's full record by its id.
  • Checked on 1 of the 7 days it takes to judge reliability.

Once connected

  • For "search paid x402 services by the need they cover", the likely first call is find_paid_service.
  • For "look up a service's full record by its id", the likely first call is get_service_details.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 1, the first on 2026-10-26
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
  • What an agent can do with it2 of 2 use cases
  • Answeredmeasuring1 of the 7 daily checks it takes to print a share
  • Median first answer142 ms
  • Space in an agent's context≈ 1,118 tokensthe definitions of all its tools (4), which an agent carries on every turn
  • Tool definitionsA · 100 of 100
  • Typed results4 of 4 toolsdeclared outputSchema: results come typed, read once
  • Every tool passes all six checks.

What an agent can do with it

  • not sure · check a paid API's delivery record before paying
  • can do · search paid x402 services by the need they cover
  • can do · look up a service's full record by its id

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers4 tools · read 2026-10-26
  • find_paid_service

    Search paid x402 APIs and datasets by need. Ranked: verified first, then probe score, then price. Each result carries what you choose on: status, score (0..1), evidence_tier, paid_verified (we bought it with real USDC and it delivered)…

  • get_service_details

    Full record for one listing id: request and response schemas, sample_query, observed 402 terms (network, payTo, scheme, x402 version), reputation detail, and paid_verification (our latest real USDC purchase, with its settlement tx where…

  • resolve_endpoint

    Check an endpoint URL you already hold before paying it. Returns match 'active' with the listing's full record, 'delisted' (listed here, later removed), or 'unknown' (never checked here; absence is not a verdict either way). The record is…

  • what_agents_are_asking_for

    What agents searched this directory for, for deciding which x402 service to build or list. Terms ranked by how many distinct days they were asked, each with catalogue_top: the listings our own search already returns for it. A term being…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "registry": {
      "type": "http",
      "url": "https://api.nohumans.directory/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http nohumans https://api.nohumans.directory/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://api.nohumans.directory/mcp as a custom connector in the settings.

OpenAPI spec

22 paths, read 2026-10-26. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.