nohumans.directory

directory.nohumansPublished by nohumans.directoryOfficial publisherv1.3.0Updated Oct 25, 2026

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

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingFinanceDeveloper Tools

Overview

AI-generated overview

A free remote directory that lets an assistant find, vet and reverse-look-up paid x402 API services before spending USDC on them.

What you can do
Search paid x402 services by query, category, price ceiling and minimum reliability score, with ranked results showing status, score, evidence tier and price. Read a full listing record: request and response schemas, sample query, observed 402 terms, reputation detail and paid-verification evidence. Check an endpoint URL you already hold against the directory for an active, delisted or unknown verdict. See aggregate demand: what agents searched for, ranked by distinct days asked, with matching listings.
When to use it
Use it when an assistant is about to call a paid x402 endpoint and wants to compare candidates or confirm an endpoint it already holds actually delivers before paying. Also useful for sellers deciding which x402 service to build or list.
Requirements
Remote streamable HTTP endpoint; no install, API key, signup or account. Clients without remote HTTP support can bridge it through the npx mcp-remote package, which needs Node.js. Network access to the directory is required.
Before you install
The directory is read-only and free, but its verdicts are dated evidence, not a safety rating; an unknown or not-listed result means never checked, not unsafe. Listings involve real USDC payments to third-party endpoints, so paying them is a separate spending decision. Demand data is aggregated and excludes some queries.

Installation

In SourceWeft

  1. Open nohumans.directory in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/directory.nohumans%2Fregistry/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

README

nohumans.directory — MCP Server

Find and vet paid x402 API services before an agent spends money on them.

A discovery and trust layer for paid x402 services. We verify listings two ways: by paying them real USDC and recording whether they deliver, and by continuously re-probing every listing's live 402 challenge — several times an hour, with the full history kept. Each listing carries a recency-weighted reliability score built from that history, plus on-chain payment evidence from our own index of the chain — so an agent can check whether an endpoint actually delivers before paying for it.

Free. No API key. No signup. No account.

Live stats: https://nohumans.directory/stats · REST API: https://api.nohumans.directory

Why this exists

Most x402 directories are catalogs: they list what exists. Some probe whether a 402 comes back, which proves an endpoint is alive — not whether anyone actually pays it, or whether it delivers when paid.

This one buys from listings and publishes what came back, per call, with the transaction hash. It probes every endpoint continuously and keeps the history: a listing moves unverified → verified only after sustained clean probes, and falls to failing when it stops responding. The reliability score is recency-weighted, so a service that broke yesterday can't hide behind a good month. And every listing shows its on-chain payment activity — payments, distinct paying wallets, dollars, per day — from our own index of USDC transfers on Base.

Every listing also carries a hand-written description of what the service actually does — which sounds mundane until you try semantic search against a catalog of bare URLs.

Installation

Remote server, streamable HTTP. No install, no build step, no credentials.

Claude Code

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

Claude Desktop / any stdio-only client

json
{  "mcpServers": {    "nohumans": {      "command": "npx",      "args": ["mcp-remote", "https://api.nohumans.directory/mcp"]    }  }}

Direct remote connection

https://api.nohumans.directory/mcp

Transport: streamable-http · Authentication: none · Cost: free

Agent Skill

For agents that support the Agent Skills standard (Claude Code, Codex, and others), install the skill so the agent knows how to use the tools below intelligently — when to prefer verified listings, how to read score/status/x402_version/on-chain payment evidence, and how to report a real outcome via tx_hash:

bash
mkdir -p ~/.claude/skills/nohumans-directorycurl -o ~/.claude/skills/nohumans-directory/SKILL.md \  https://raw.githubusercontent.com/jalcodev/nohumans-mcp/main/skills/nohumans-directory/SKILL.md

Tools

find_paid_service

Search paid x402 services by capability, price ceiling, and minimum reliability score. Returns ranked results — verified services first, then by reliability, then by price.

ParameterTypeDescription
querystringFree-text search across service names and descriptions
categorystringExact category filter, e.g. data.fx, infra.trust
max_pricenumberMaximum price per call, in USDC
min_scorenumberMinimum reliability score, 0-1
limitnumberMax results, 1-50 (default 10)

get_service_details

Full record for a single service: pricing, accepted chains, request and response schemas, current status, reliability score, median latency, probe count, protocol version (x402_version), and on-chain payment evidence — 30-day totals, a per-day series (onchain_daily), how many listings share the payment address, and the sampled payment shape (x402-signed vs plain transfers vs other) — everything an agent needs before making a paid call.

ParameterTypeDescription
idstringListing ID, as returned by find_paid_service

resolve_endpoint

The reverse lookup: you already hold an endpoint URL — from another catalog, a prompt, a config file — and want this directory's verdict on it before paying. Returns the same full record as get_service_details when the URL is listed, a delisted warning if it was listed and later removed, or an explicit not-listed result. Not-listed means never checked here, not unsafe.

ParameterTypeDescription
urlstringThe endpoint URL exactly as held, query string included

what_agents_are_asking_for

For sellers: the aggregate demand feed — what buyers searched this directory for, ranked by how many distinct days a term was asked (not by volume, which is trivially faked). Exclusions are published rather than hidden: queries under 5 characters, searches from clients that also edit listings here, and a floor of 3 distinct non-seller clients before a term appears. The window ends a day behind live and the response says when. Same data as GET /v1/demand.

No parameters.

Example

An agent that needs FX rates and won't pay more than half a cent, and refuses to touch anything with a reliability score under 0.9:

Source: README.md at commit f7e95b5

Tools

4

find_paid_service

Find a 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), 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.

Parameterslimitquerydetailcategoryprotocolmax_pricemin_scorempp_method

get_service_details

Get a paid service's full record

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.

Parametersidrequired

resolve_endpoint

Check an endpoint URL before paying

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.

Parametersurlrequired

what_agents_are_asking_for

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 a week behind live while the paid tier is on sale (a day when it is not; delay_hours and window_ends_at in the response say which); 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.

Parameterslimitoffset

Version history

1
  1. v1.3.0LatestSep 16, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Nohumans integrations

GridHub Electricity Market Data

Published by GitHub account jalcodev

Hosted MCP server giving assistants live and historical electricity prices, demand and carbon intensity for 25 grid zones, with zone comparison and freshness.

Streamable HTTPWeb executable
Finance6 toolsOct 24, 2026