Data · Remote MCP server
US Codex
Federal law: US Code, CFR, public laws, bills and executive orders, cross-linked and versioned.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
org.uscodex/uscodex- Version
- 1.0.0
- Status
- Active
- Category
- data
- Transport
- Streamable HTTP, SSE (HTTP + Server-Sent Events)
- Published
- 2026-09-25
- Updated
- 2026-09-25
- Publisher
- org.uscodex
- Namespace
- Namespace verified by the MCP Registry via the domain uscodex.org · how
- Website
- uscodex.org/mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://uscodex.org/mcp | None |
| SSE (HTTP + Server-Sent Events) | https://uscodex.org/mcp/sse | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Endpoint
https://uscodex.org/mcp(HTTP)- Reachable
- Yes (HTTP 200)
- Handshake
- uscodex 0.1.0 · protocol 2025-06-18
- Tools discovered
- 5:
search,fetch,citations,history,compare - Checked on
- 2026-10-05
- Endpoint
https://uscodex.org/mcp/sse(SSE)- Reachable
- Yes (HTTP 200)
- SSE stream
- Opened and named its message endpoint (not used further)
- Checked on
- 2026-10-05
How to connect US Codex
US Codex is a remote MCP server: there is nothing to install. Its endpoint is https://uscodex.org/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
It also lists an endpoint on the older SSE transport https://uscodex.org/mcp/sse. Clients that support remote servers generally still accept SSE endpoints, though the protocol now favours Streamable HTTP.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More data servers
| Server | Runs |
|---|---|
| Url Ai MCPUrl Ai MCP server. Tools: parse url, shorten url data, check url safety. Built by MEOK AI Labs. | Local · stdio |
| US Building Permit AggregatorPull recent building permits from 9 US cities in a unified schema from official open-data portals. | Remote · HTTPLive check: sign-in required |
| US Census Bureau DataQuery US Census Bureau data: demographics, economics, and housing statistics. | Remote · HTTPLive check: sign-in required |
| US Code Federal StatutesSearch and read U.S. Code statutes with legal and inline citations linking to uscode.ecfr.io. | Remote · HTTPLive check: ✓ handshake |
| US Economic Releases (CPI, Payrolls, Fed) - buy per-query in-session (fedwatch)CPI, payrolls, unemployment, Fed statements. $0.05/query, free testnet funds in-session. | Remote · HTTPLive check: ✓ handshake |
| Us Eli MCPUS law MCP: bills, US Code, Federal Register, executive orders, case law (state+federal), eCFR. | Local · stdio |
| US Government DataUS government open-data APIs as MCP tools: EPA, FEMA, USGS, NOAA, FDIC, HUD, CMS and more. | Local · stdio |
| US MacroUS macroeconomic data from FRED: inflation, employment, growth, housing, rates, recession signals. | Local · stdio |