Remote MCP · Endpoint

Us Code MCP server

No. Us Code answered an MCP handshake 10 days ago.

UpLast checked 10 days ago

Server URL

https://gateway.pipeworx.io/us-code/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/us-code
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
104 ms
Tools exposed
47 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
US Code — the text of federal statutes, by citation.
Listing
From the official MCP registry (active).
Recent checks of Us Code
CheckedResultHandshake
10 days agoHandshake completed104 ms
10 days agoHandshake completed103 ms
11 days agoHandshake completed136 ms
12 days agoHandshake completed114 ms
14 days agoHandshake completed110 ms
14 days agoHandshake completed61 ms
15 days agoHandshake completed179 ms
17 days agoHandshake completed106 ms
19 days agoHandshake completed216 ms
21 days agoHandshake completed71 ms
24 days agoHandshake completed81 ms
26 days agoHandshake completed106 ms
28 days agoHandshake completed67 ms

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

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 Code and makes no claim about it beyond what these checks measured.