Remote MCP · Endpoint

Us Code MCP server

No. Us Code answered an MCP handshake 1 day ago.

UpLast checked 1 day 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
57 ms
Tools exposed
39 tools
Uptime, last 30 days
93.8% from 16 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
1 day agoHandshake completed57 ms
3 days agoHandshake completed61 ms
5 days agoHandshake completed54 ms
7 days agoHandshake completed54 ms
8 days agoHandshake completed60 ms
9 days agoHandshake completed70 ms
12 days agoHandshake completed47 ms
13 days agoFailed - the request timed out—
15 days agoHandshake completed65 ms
17 days agoHandshake completed38 ms
18 days agoHandshake completed40 ms
19 days agoHandshake completed44 ms
20 days agoHandshake completed57 ms
20 days agoHandshake completed39 ms
21 days agoHandshake completed48 ms
23 days agoHandshake completed60 ms

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

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.