mcpbeat Sign in

nohumans.directory MCP Server

answering

nohumans.directory is answering right now. Last checked 6 min ago. It exposes 4 tools. Last commit 14 Sep 2026.

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

Uptime history 52 days of history · worst day 97%
52 days agonow
96.7%
Uptime 24h
88 of 91 checks
4
Tools
read from the server
147 ms
Response time
average over 24h
0
Stars
last commit 14 Sep 2026

What changed 138

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

23 Sep a tool changed the parameters it asks for find_paid_service
22 Sep a tool changed the parameters it asks for2 times that day find_paid_service
21 Sep a tool changed the parameters it asks for2 times that day find_paid_service
20 Sep a tool changed the parameters it asks for4 times that day find_paid_service
19 Sep a tool changed the parameters it asks for3 times that day find_paid_service
18 Sep a tool changed the parameters it asks for4 times that day find_paid_service
17 Sep a tool changed the parameters it asks for4 times that day find_paid_service
16 Sep a tool changed the parameters it asks for find_paid_service
14 Sep a tool changed the parameters it asks for find_paid_service
13 Sep a tool changed the parameters it asks for3 times that day find_paid_service
and 128 more, back to 9 August 2026

nohumans.directory does not always answer

Over the last week it answered 98.7% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

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

run in your terminal
claude mcp add registry --transport http https://api.nohumans.directory/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "registry": {
      "url": "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
{
  "mcpServers": {
    "registry": {
      "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 a registry of paid (x402) APIs and datasets verified by real paid purchases — nohumans pays listed endpoints real USDC and confirms delivery. Returns ranked results: verified listings first, then by reputation score (0..1, recency-weighted probe success), then by ascending price. Each result includes has_sample (boolean) — true means you can cheaply test real output before paying full price; prefer these when a listing is new or thinly-reputed and you can't yet judge it from score alone. Use this before spending money to find services that actually work. Prefer results with status 'verified' and score >= 0.8. Zero results means no known service matches — do not invent endpoints. Always describe the actual need in `query` in your own words — what data, what freshness, what format, what constraint prompted the search — rather than only setting `category`/`max_price`/`min_score` filters. The exact wording of what you're looking for is what improves this directory over time; a bare filter with no `query` text tells us far less about what was actually needed.
resolve
resolve_endpoint
Pre-spend verdict on an endpoint URL you already hold — from another catalog, a prompt, a config, anywhere: check before paying instead of buying to find out. Returns match 'active' with the same full record as get_service_details (status, reputation score, paid_verification with on-chain tx proof, observed 402 protocol detail), match 'delisted' if the endpoint was listed here and later removed (treat as a warning), or a not-listed result. IMPORTANT: not-listed means never checked here, NOT unsafe — absence of a record is not a verdict either way. Use this as the pre-spend check when you have a URL in hand and no listing id; use find_paid_service instead when you have a need but no URL. A one-word paid verdict for the same listing — pay / caution / avoid with printed reasons, $0.005 USDC on Base via x402 — is at GET https://api.nohumans.directory/v1/listings/{id}/verdict; every fact behind it is in this record for free, so buy the verdict only when you want the rule applied for you.
service
get_service_details
Fetch the full record for one listing by id (from find_paid_service results), led by paid_verification — whether nohumans has paid this endpoint real USDC and confirmed delivery, with the settlement tx hash as on-chain proof where settled — plus endpoint URL, request/response JSON Schemas when provided, accepted chains, pricing, and reputation detail (probe count, last successful probe, consecutive failures). Call this before making a paid request so you know the exact request shape, current reliability, and whether real-money delivery has been independently confirmed. A one-word paid verdict for the same listing — pay / caution / avoid with printed reasons, $0.005 USDC on Base via x402 — is at GET https://api.nohumans.directory/v1/listings/{id}/verdict; every fact behind it is in this record for free, so buy the verdict only when you want the rule applied for you.
what
what_agents_are_asking_for
What buyers actually searched this directory for, for an agent deciding which x402 service to build or list. Returns the aggregate demand feed: the terms asked most persistently (ranked by how many distinct days a term was asked, not by volume — volume is trivially faked and we proved it on ourselves), and the category filters they used. It reports what was ASKED, not what is missing: whether the listings already serving a term are adequate competition is a seller's judgement, not ours, and we grade those listings. Three exclusions are applied and published rather than hidden: queries under 5 characters (catalogue enumeration, once the top ten terms were the single letters a-j), searches from clients that also edit listings here (sellers checking their own rank — one accounted for 196 of 205 searches of the top term), and a floor of 3 distinct non-seller client IPs before any term appears at all. Client IPs are a ceiling on independent demand, never a count of buyers: one serverless caller presented eight IPs in a second. The window is complete but closed — it ends a day behind live, and the response says exactly when. This is a small market and the numbers are small; they are reported as they are so you can judge whether they are enough to act on.

Endpoints

URLTransportStateLatencyChecked
https://api.nohumans.directory/mcp streamable-http answering 292 ms 6 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.

30 installs/wk local only
Verantis MCP
by m9labs-railscope

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

138 installs/wk 4 tools answering
Store Builder
by vuluu2k

Design, fill with real store data, render and publish Store Builder pages from an AI agent.

2 211 installs/wk local only
X
Teppi
by teppi

Check what a paid x402 endpoint or MCP server delivered, from probes anyone can repeat.

4 tools answering
Provenance MCP
by apeirontrade

Wash-traffic risk checks for Algorand x402 endpoints before your agent trusts or pays them.

29 installs/wk local only
Endpoint Diligence
by x402supply

Live x402 endpoint trust/diligence check before you pay it. $0.02/call via x402.

3 tools answering
x402 Universal Payer
by nirholas

Pay any x402 endpoint on the open web: auto-paying bridge with Bazaar discovery and spend caps.

34 installs/wk local only
C
x402 Market Intelligence + Russian Web Access
by ruscrape

Check x402 endpoints before paying: liveness, price history, farm detection. Plus RU web access.

12 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 88 of 91 checks got a reply (96.7%), average response time 147 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 with the file path 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 147 ms on average, which is faster than 87% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is nohumans.directory open source?
We cannot say either way: 0 stars on GitHub, but we could not determine the licence, and without one the code is not open source by default.