Registry MCP server
{
"mcpServers": {
"nohumans-registry": {
"type": "http",
"url": "https://api.nohumans.directory/mcp"
}
}
}{
"mcpServers": {
"nohumans-registry": {
"type": "http",
"url": "https://api.nohumans.directory/mcp"
}
}
}{
"mcpServers": {
"nohumans-registry": {
"type": "http",
"url": "https://api.nohumans.directory/mcp"
}
}
}{
"servers": {
"nohumans-registry": {
"type": "http",
"url": "https://api.nohumans.directory/mcp"
}
}
}{
"mcpServers": {
"nohumans-registry": {
"type": "http",
"url": "https://api.nohumans.directory/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 1.3.0
What it does
A discovery and verification service for paid x402 API endpoints. It tests listings by making real USDC payments, records delivery outcomes with transaction hashes, and continuously probes endpoints to build reliability scores. Intended for agents that need to evaluate whether a paid service actually works before spending money on it.
- Search for a paid x402 service by capability and price, filtered by minimum reliability score to avoid unproven providers.
- Check the full performance history and on-chain payment activity of a specific service before making a paid call to it.
- Verify whether an endpoint URL from another source is listed here, delisted, or unknown before committing payment.
Tools this server exposes
| Tool | Does |
|---|---|
| find_paid_service | Search for paid x402 services by free-text query, category, price ceiling, and minimum reliability score; returns results ranked by verification status and scor |
| get_service_details | Fetch the full record for a service: pricing, accepted chains, schemas, current status, reliability score, latency, probe history, and on-chain payment evidence |
| resolve_endpoint | Look up a URL to see whether it is listed in this directory, delisted, or unknown; returns the full service record if found. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.