# US Codex (remote · uscodex.org)

Federal law: US Code, CFR, public laws, bills and executive orders, cross-linked and versioned.

- Trust score: 63/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-29

## Components

- remote · `uscodex.org`: 63/100 (this document), [markdown](https://verifymcp.io/servers/org-uscodex-uscodex/uscodex.md), [page](https://verifymcp.io/servers/org-uscodex-uscodex/uscodex)
- remote · `uscodex.org`: 57/100, [markdown](https://verifymcp.io/servers/org-uscodex-uscodex/uscodex-2.md), [page](https://verifymcp.io/servers/org-uscodex-uscodex/uscodex-2)

## Channel facts

- Endpoint: `https://uscodex.org/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-09-29.

- **Endpoint Security**: 57/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 5 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 is enforced; there's no plaintext access path.
  - 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**: 68/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1153 tokens (~230/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the US Codex MCP server?

US Codex is a hosted endpoint at https://uscodex.org/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http org-uscodex-uscodex 'https://uscodex.org/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "org-uscodex-uscodex": {
      "url": "https://uscodex.org/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "org-uscodex-uscodex": {
      "type": "http",
      "url": "https://uscodex.org/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.org-uscodex-uscodex]
url = "https://uscodex.org/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "org-uscodex-uscodex": {
      "type": "remote",
      "url": "https://uscodex.org/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add org-uscodex-uscodex --url 'https://uscodex.org/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  org-uscodex-uscodex:
    url: "https://uscodex.org/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "org-uscodex-uscodex": {
      "Transport": "http",
      "Url": "https://uscodex.org/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add org-uscodex-uscodex -t streamable-http -u 'https://uscodex.org/mcp'
```

### Other

```json
{
  "mcpServers": {
    "org-uscodex-uscodex": {
      "type": "http",
      "url": "https://uscodex.org/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-09-28 (score 63, +1)

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

### 2026-09-26 (score 62, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-25 (score 61)

First indexed and scored.

## MCP tools (5)

### `search` (~166 tokens)

Search the full text of federal law: United States Code, Code of Federal Regulations, Public Laws, Congressional Bills, Executive Orders. Results are ranked across every corpus unless `corpus` narrows them, each with its citation, a link and the matching words. A query that is only a citation returns that document instead.

Input parameters:

- `corpus` (string): Search one corpus only.
- `date` (string): For a code, search it as it stood on this date (YYYY-MM-DD).
- `page` (integer): Page of results, 20 to a page.
- `query` (string, required): Words, a "quoted phrase", NOT before a word to exclude it, or a citation.
- `title` (string): For a code, search one title ("11", "40").

### `fetch` (~339 tokens)

Read a document or page of the site as markdown: a code section with its notes, a title's or unit's contents, a public law, a bill (at any version), an executive order. Paths also reach the corpus indexes ("/usc", "/pl?congress=118", "/bills?congress=119", "/eo") and each code's releases ("/usc/releases"). Links in the markdown are paths this tool accepts.

Input parameters:

- `citation` (string): A citation ("26 U.S.C. 61(a)", "40 CFR 60.1", "Pub. L. 119-21", "H.R. 1", "E.O. 14000"). Give this or `path`.
- `notes` (boolean): Include a section's source credit, notes and footnotes.
- `path` (string): A page of the site, as its path or full URL ("/usc/26/61", "/pl/119/21"). Give this or `citation`.
- `provision` (string): Part of the document: in a code section, a provision and everything under it ("a-1" for (a)(1)) or a run of them ("a..c"); in a law, bill or order, a heading's {#anchor} ("tI-stA-s10101") or a provis…
- `release` (string): For a code, the release to read it at: a release point ("119-21") or a date (YYYY-MM-DD) for the release in force then. Defaults to the latest.

### `citations` (~191 tokens)

What cites a document: each corpus's citations of a code section, law, bill or order, with the words that cite it, and for a statute the regulations issued under it. Lists come 50 at a time; `list` and `offset` page through one.

Input parameters:

- `citation` (string): A citation ("26 U.S.C. 61(a)", "40 CFR 60.1", "Pub. L. 119-21", "H.R. 1", "E.O. 14000"). Give this or `path`.
- `list` (string): One list only, by the corpus that cites.
- `offset` (integer): With `list`, where in it to start.
- `path` (string): A page of the site, as its path or full URL ("/usc/26/61", "/pl/119/21"). Give this or `citation`.

### `history` (~155 tokens)

How a document came to be: for a code section, the laws that enacted and amended it and every release that changed its text; for a law or bill, its legislative history, each version linked to its text and to what changed from the one before.

Input parameters:

- `citation` (string): A citation ("26 U.S.C. 61(a)", "40 CFR 60.1", "Pub. L. 119-21", "H.R. 1", "E.O. 14000"). Give this or `path`.
- `path` (string): A page of the site, as its path or full URL ("/usc/26/61", "/pl/119/21"). Give this or `citation`.

### `compare` (~213 tokens)

What changed in a code section between two releases: each provision added, removed, changed or renumbered, the edits marked <del> and <ins>. To compare versions of a bill, take the 'what changed' link from its history.

Input parameters:

- `citation` (string): A citation ("26 U.S.C. 61(a)", "40 CFR 60.1", "Pub. L. 119-21", "H.R. 1", "E.O. 14000"). Give this or `path`.
- `from` (string): Release point or date to compare from. Defaults to the release before `to`.
- `only_edits` (boolean): Only the provisions that changed, not the whole text.
- `path` (string): A page of the site, as its path or full URL ("/usc/26/61", "/pl/119/21"). Give this or `citation`.
- `to` (string): Release point or date to compare to. Defaults to the latest.

## Diagnostics

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

## Score history

- 2026-09-29: 63
- 2026-09-28: 63
- 2026-09-27: 62
- 2026-09-26: 62
- 2026-09-25: 61

## Common questions

### What is the US Codex MCP server?

US Codex is an MCP server listed in the public MCP registry as org.uscodex/uscodex. Federal law: US Code, CFR, public laws, bills and executive orders, cross-linked and versioned. This page covers its hosted endpoint (https://uscodex.org/mcp).

### Is the US Codex MCP server safe to use?

US Codex scores 63 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the US Codex MCP server expose?

US Codex exposes 5 tools: search, fetch, citations, history, compare. Their descriptions and schemas cost roughly 1,064 tokens of context every time the server is loaded.

### Does the US Codex MCP server require authentication?

No. We connected to US Codex without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the US Codex MCP server still maintained?

US Codex is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://uscodex.org/mcp
- Website: https://uscodex.org/mcp
- Changelog RSS feed: https://verifymcp.io/servers/org-uscodex-uscodex/uscodex.xml
- Changelog JSON feed: https://verifymcp.io/servers/org-uscodex-uscodex/uscodex.json
- HTML version of this page: https://verifymcp.io/servers/org-uscodex-uscodex/uscodex