nohumans.directory MCP Server

by nohumans Your server? Claim it

answering

nohumans.directory is answering right now. Last checked 7 min ago. It exposes 4 tools. Last commit 3 Nov 2026.

We buy from x402 endpoints with real USDC and publish delivery outcomes. Check before you spend.

Uptime history 91 days of history · worst day 93%

91 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

202 ms

Response time

average over 24h

Stars

last commit 3 Nov 2026

What changed 300

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 9 August 2026. No other catalogue keeps this.

13 Nov a tool changed the parameters it asks for find_paid_service

12 Nov a tool changed the parameters it asks for2 times that day find_paid_service

11 Nov a tool changed the parameters it asks for2 times that day find_paid_service

10 Nov a tool changed the parameters it asks for2 times that day find_paid_service

9 Nov a tool changed the parameters it asks for3 times that day find_paid_service

8 Nov a tool description was rewritten what_agents_are_asking_for

7 Nov a tool changed the parameters it asks for find_paid_service

6 Nov a tool changed the parameters it asks for find_paid_service

5 Nov a tool changed the parameters it asks for3 times that day find_paid_service

4 Nov a tool changed the parameters it asks for4 times that day find_paid_service

and 290 more, back to 9 August 2026

Nothing serious here today

Today is the operative word: we check nohumans.directory every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

Settings → Connectors → Add custom connector, then paste this address

https://api.nohumans.directory/mcp

~/.codex/config.toml

[mcp_servers.registry]
url = "https://api.nohumans.directory/mcp"

.cursor/mcp.json

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

.vscode/mcp.json

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

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

paid

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), latest_purchase_delivered (false = our most recent paid purchase took real USDC and did not deliver: do not pay it), has_sample (a cheap preview exists), price. Relevance comes from the query text; a specific need in plain words matches best. Zero results means nothing listed matches. Results are dated evidence, not guarantees. Returns a summary per listing; detail='full' returns every field. Free, read-only.

resolve

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 dated evidence, not a safety rating. Free, read-only.

service

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 proven). Useful before paying: it shows the exact request shape and current reliability. Every timestamp has an _iso twin; on-chain counts describe the seller's wallet, usually shared by several listings, not this endpoint. Free, read-only.

what

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 asked does not mean nothing serves it. The window ends live, rebuilt hourly (no delay since 2026-11-08; delay_hours and window_ends_at in the response say so); test traffic, sellers searching their own listings and identifying terms are excluded; floor: a term appears once at least 1 distinct non-seller client IP asked it. Client counts are IP ceilings, never buyer counts. Paged: limit (default 25), offset, next_offset. Free, read-only.

Endpoints

URL	Transport	State	Latency	Checked
https://api.nohumans.directory/mcp	streamable-http	answering	160 ms	7 min ago

Alternatives to nohumans.directory

same job, measured the same way

Deadchannel

by plus8bit

Check an x402 endpoint before you pay it: verdict, risk score and what is wrong. $0.005 in USDC.

47 installs/wk local only

X402 Trust MCP

by jonasfuchss

Discover x402 endpoints and check their trust score before your agent pays them.

170 installs/wk local only

402xAgent

by withgrokbot

Check an x402 endpoint before your agent pays: pay, skip or recheck, with Ed25519-signed receipts.

12 tools answering

Settled

by settled

Check x402 endpoints before your agent pays: payTo, paid test purchases, payee and buyer reports

160 installs/wk 18 tools answering

Objective Trust

by anhmtk

Ranks MCP endpoints by health and your own outcomes before you pay.

3 tools answering

probe402-check

by probe402

Ask probe402's public record about an x402 or MPP endpoint before an agent pays it.

40 installs/wk local only

Nooscape MCP

by runtimeadmin

Read-only facts with dates about AI agents, wallets and endpoints from Nooscape's public record.

181 installs/wk local only

Verantis MCP

by m9labs-railscope

Verified directory for machine payments (x402 & MPP): check services and wallets before agents pay.

130 installs/wk 4 tools answering

nohumans.directory — questions

Answers built from our own checks of this server.

What can nohumans.directory do?

It exposes 4 tools, read directly from the server on our last check. Among them: find_paid_service, get_service_details, resolve_endpoint, what_agents_are_asking_for. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is nohumans.directory working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 202 ms. The bar chart above shows every period we have measured.

How do I connect nohumans.directory?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does nohumans.directory need an API key?

No. nohumans.directory completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is nohumans.directory?

It answers our handshake in 202 ms on average, which is faster than 72% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is nohumans.directory open source?

The code is open source: it is published under the MIT licence, written in JavaScript and 0 stars on GitHub. The licence covers the code in the repository, not the hosted service at api.nohumans.directory, which runs on its operator's own terms.