API Tools

nohumans.directory

Search a registry of paid APIs and datasets, and fetch detailed records including endpoints, schemas, pricing, and reputation.

x402 supported1 endpoint2 known toolsFirst detected July 25, 2026Last detected July 29, 2026

ENDPOINT 1

https://api.nohumans.directory/mcp

No auth detected

MCP server metadata

Name: nohumans-directory
Version: 1.0.0

Capabilities

tools

Server instructions

nohumans.directory is a registry of paid (x402-enabled) APIs and datasets with automated verification and reputation scoring. Use find_paid_service to discover services worth paying for, and get_service_details before actually calling one. Trust signals: status 'verified' means the endpoint has sustained a recency-weighted probe success score above 0.8 (roughly sixteen consecutive clean probes) from our infrastructure; score is a recency-weighted probe success rate (0..1), blended with an on-chain-verified payer-report score once a listing has 3+ distinct reporting payers. Prefer verified listings with score >= 0.8. Prices are per-call, in the listed currency (usually USDC). This directory indexes services; it does not proxy or execute payments. To LIST a service in this directory, POST it to https://api.nohumans.directory/v1/listings (JSON; see https://nohumans.directory/llms.txt for a worked example) — new listings are probed every 15 minutes and earn 'verified' after a few hours of consistently healthy responses. After actually paying and calling a listed service, POST the transaction hash to https://api.nohumans.directory/v1/reports to report whether it delivered as expected — this is verified on-chain, not an honor system.

Known tools 2

find_paid_service

Search a verified registry of paid (x402) APIs and datasets.

Inferred read-only

get_service_details

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).

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.nohumans-directory]
url = "https://api.nohumans.directory/mcp"
enabled = true

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: nohumans-directory
Remote MCP URL: https://api.nohumans.directory/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

{
  "name": "nohumans-directory",
  "transport": "streamable-http",
  "url": "https://api.nohumans.directory/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for nohumans.directory was fetched 2026-07-26T00:47:51.808Z.

Trust status Neutral

nohumans.directory is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.