US Codex
REMOTE · USCODEX.ORG · 2 COMPONENTS · SCANNED SEP 29
Federal law: US Code, CFR, public laws, bills and executive orders, cross-linked and versioned.
Available components
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. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the US Codex MCP server?
US Codex is a hosted endpoint at https://uscodex.org/mcp/sse, 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.
remote · uscodex.org
claude mcp add --transport http org-uscodex-uscodex 'https://uscodex.org/mcp/sse'
{
"mcpServers": {
"org-uscodex-uscodex": {
"url": "https://uscodex.org/mcp/sse"
}
}
} {
"servers": {
"org-uscodex-uscodex": {
"type": "http",
"url": "https://uscodex.org/mcp/sse"
}
}
} [mcp_servers.org-uscodex-uscodex] url = "https://uscodex.org/mcp/sse"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"org-uscodex-uscodex": {
"type": "remote",
"url": "https://uscodex.org/mcp/sse",
"enabled": true
}
}
} openclaw mcp add org-uscodex-uscodex --url 'https://uscodex.org/mcp/sse' --transport streamable-http
mcp_servers:
org-uscodex-uscodex:
url: "https://uscodex.org/mcp/sse" {
"McpServers": {
"org-uscodex-uscodex": {
"Transport": "http",
"Url": "https://uscodex.org/mcp/sse"
}
}
} assistant mcp add org-uscodex-uscodex -t streamable-http -u 'https://uscodex.org/mcp/sse'
{
"mcpServers": {
"org-uscodex-uscodex": {
"type": "http",
"url": "https://uscodex.org/mcp/sse"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 25 Sept 26 55
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 29 Sept 2026 · Probed https://uscodex.org/mcp/sse
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=uscodex.org | CN=WE1,O=Google Trust Services,C=US | 18 Aug 2026 | 16 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 54e14cbce83d9f420e1d5428379db73c |
| SANs: uscodex.org, *.uscodex.org | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of uscodex.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| org. | present | 26974 | 8 | Verified |
| uscodex.org. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| sse | https://uscodex.org/mcp/sse | Verified | 200 | |
| http (plaintext) | http://uscodex.org/mcp/sse | HTTPS enforced | 301 | https://uscodex.org/mcp/sse |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
citations ~191
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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`. |
No output schema declared.
No examples provided.
compare ~213
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
fetch ~339
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
history ~155
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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`. |
No output schema declared.
No examples provided.
search ~166
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Words, a "quoted phrase", NOT before a word to exclude it, or a citation. |
| title | string | – | For a code, search one title ("11", "40"). |
No output schema declared.
No examples provided.
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/sse).
Is the US Codex MCP server safe to use?
US Codex scores 57 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.