Remote MCP · Endpoint

US Federal Regulations (CFR) MCP server

Yes, as of 20 hours ago: the server returned an HTTP error.

DownLast checked 20 hours ago

Server URL

https://rules.openkrill.app/mcp

The last check failed: the server returned an HTTP error.

Registry name
app.openkrill/rules
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
5 tools
Uptime, last 30 days
92.3% from 13 checks
Described by its publisher as
Read a CFR or eCFR section, or search US federal regulations and the Federal Register.
Listing
From the official MCP registry (active).
Recent checks of US Federal Regulations (CFR)
CheckedResultHandshake
20 hours agoFailed - the server returned an HTTP error—
3 days agoHandshake completed136 ms
5 days agoHandshake completed184 ms
8 days agoHandshake completed155 ms
10 days agoHandshake completed147 ms
12 days agoHandshake completed227 ms
14 days agoHandshake completed61 ms
16 days agoHandshake completed53 ms
17 days agoHandshake completed26 ms
19 days agoHandshake completed66 ms
20 days agoHandshake completed52 ms
21 days agoHandshake completed33 ms
24 days agoHandshake completed48 ms

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

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 Federal Regulations (CFR) and makes no claim about it beyond what these checks measured.