Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

nohumans.directory

REMOTE · API.NOHUMANS.DIRECTORY · SCANNED AUG 3

Curated, probe-verified directory of paid x402 APIs. Agents check it before spending money.

0 this week 58 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security46
Transport & Reachability100
Schema Quality & AI Usability63
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 576 tokens (~288/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · api.nohumans.directory

# add to Claude Code
claude mcp add --transport http directory-nohumans-registry https://api.nohumans.directory/mcp
# ~/.codex/config.toml
[mcp_servers.directory-nohumans-registry]
url = "https://api.nohumans.directory/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "directory-nohumans-registry": {
      "type": "remote",
      "url": "https://api.nohumans.directory/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add directory-nohumans-registry --url https://api.nohumans.directory/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  directory-nohumans-registry:
    url: "https://api.nohumans.directory/mcp"
// mcp.json
{
  "mcpServers": {
    "directory-nohumans-registry": {
      "type": "http",
      "url": "https://api.nohumans.directory/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Jul 26 −3
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Jul 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 27 Jul 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 57

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://api.nohumans.directory/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=nohumans.directory CN=WE1,O=Google Trust Services,C=US 18 Jul 2026 16 Oct 2026 ECDSA 256 ECDSA-SHA256 ff76dc58361767a413d6c03957754fb0
SANs: nohumans.directory, api.nohumans.directory, *.api.nohumans.directory
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b
DNSSEC insecure

Validation of api.nohumans.directory. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
directory. present 59725 8 Verified
nohumans.directory. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.nohumans.directory/mcp Verified 200
http (plaintext) http://api.nohumans.directory/mcp Inconclusive 405
MCP tools — 2 exposed · ~308 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
find_paid_service ~218

Search a verified registry of paid (x402) APIs and datasets. Returns ranked results: verified listings first, then by reputation score (0..1, recency-weighted probe success), then by ascending price. 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.

NameTypeReqDescription
categorystringExact category filter, dot-namespaced, e.g. 'data.fx', 'compute.translation'.
limitintegerMaximum results to return (default 10, cap 50).
max_pricenumberMaximum per-call price. Omit for no cap.
min_scorenumberMinimum reputation score, 0..1. Use 0.8 to only see reliably-passing services.
querystringFree-text search matched against service names and descriptions, e.g. 'fx rates', 'translation', 'weather'. Omit to browse.

No output schema declared.

No examples provided.

get_service_details ~90

Fetch the full record for one listing by id (from find_paid_service results): 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 and current reliability.

NameTypeReqDescription
idstringyesListing id, as returned by find_paid_service.

No output schema declared.

No examples provided.