# nohumans.directory (remote · api.nohumans.directory)

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

- Trust score: 58/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `api.nohumans.directory`: 58/100 (this document), [markdown](https://verifymcp.io/servers/directory-nohumans-registry/api.md), [page](https://verifymcp.io/servers/directory-nohumans-registry/api)

## Channel facts

- Endpoint: `https://api.nohumans.directory/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

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

### Codex

```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
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add directory-nohumans-registry --url https://api.nohumans.directory/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  directory-nohumans-registry:
    url: "https://api.nohumans.directory/mcp"
```

### Other

```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 recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 58, +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.

### 2026-07-31 (score 57, −3)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 60, +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.

### 2026-07-28 (score 59, +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.

### 2026-07-27 (score 58, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 57)

First indexed and scored.

## MCP tools (2)

### `find_paid_service` (~218 tokens)

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.

Input parameters:

- `category` (string): Exact category filter, dot-namespaced, e.g. 'data.fx', 'compute.translation'.
- `limit` (integer): Maximum results to return (default 10, cap 50).
- `max_price` (number): Maximum per-call price. Omit for no cap.
- `min_score` (number): Minimum reputation score, 0..1. Use 0.8 to only see reliably-passing services.
- `query` (string): Free-text search matched against service names and descriptions, e.g. 'fx rates', 'translation', 'weather'. Omit to browse.

### `get_service_details` (~90 tokens)

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.

Input parameters:

- `id` (string, required): Listing id, as returned by find_paid_service.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/directory-nohumans-registry/api#diagnostics

## Score history

- 2026-08-03: 58
- 2026-08-02: 57
- 2026-08-01: 57
- 2026-07-31: 57
- 2026-07-30: 60
- 2026-07-29: 59
- 2026-07-28: 59
- 2026-07-27: 58
- 2026-07-26: 57

## Links

- Remote endpoint: https://api.nohumans.directory/mcp
- Repository: https://github.com/jalcodev/nohumans-mcp
- Website: https://nohumans.directory/
- Changelog RSS feed: https://verifymcp.io/servers/directory-nohumans-registry/api/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/directory-nohumans-registry/api/changelog.json
- HTML version of this page: https://verifymcp.io/servers/directory-nohumans-registry/api