Remote MCP · Endpoint

US Codex MCP server

No. US Codex answered an MCP handshake 16 minutes ago.

UpLast checked 16 minutes ago

Server URL

https://uscodex.org/mcp

The last check completed an MCP handshake.

Registry name
org.uscodex/uscodex
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
52 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Federal law: US Code, CFR, public laws, bills and executive orders, cross-linked and versioned.
Listing
From the official MCP registry (active).
Recent checks of US Codex
CheckedResultHandshake
16 minutes agoHandshake completed52 ms
8 days agoHandshake completed84 ms
9 days agoHandshake completed89 ms
11 days agoHandshake completed96 ms
12 days agoHandshake completed95 ms
13 days agoHandshake completed407 ms
14 days agoHandshake completed156 ms
14 days agoHandshake completed83 ms
16 days agoHandshake completed163 ms
19 days agoHandshake completed125 ms
21 days agoHandshake completed208 ms
24 days agoHandshake completed770 ms
26 days agoHandshake completed34 ms
28 days agoHandshake completed40 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with US Codex and makes no claim about it beyond what these checks measured.