Skip to content
US Codex logo

US Codex MCP server

Which servers in the official MCP registry are US Codex's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-19

← Back to US Codex

Whose server it is
  • Registry nameorg.uscodex/uscodexverified in the MCP registry

The registry name sits under uscodex.org. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-19
  • Stateanswerschecked 2026-10-19
  • Tools5
  • Server calls itselfuscodex
  • Server version0.1.0
  • Protocol version2025-06-18

On 2026-10-19 the server answered initialize and tools/list without a sign-in. First answer in 315 ms.

Measured dailydaily checks: 2, the first on 2026-10-19
  • Answeredmeasuring2 of the 7 daily checks it takes to print a share
  • Median first answer355 ms
  • Space in an agent's context≈ 1,178 tokensthe definitions of all its tools (5), which an agent carries on every turn
  • Tool definitionsB · 83 of 100
  • Not saying whether it only reads or can destroy: 5 of 5

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The state of vendors' MCP servers: method and numbers →

Tools it offers5 tools · read 2026-10-19
  • search

    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…

  • fetch

    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"…

  • citations

    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.

  • history

    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…

  • compare

    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.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "uscodex": {
      "type": "http",
      "url": "https://uscodex.org/mcp"
    }
  }
}

OpenAPI spec

10 paths, read 2026-10-19. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.