Remote MCP · Endpoint
US federal rules taking effect MCP server
No. US federal rules taking effect answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://referencesource.org/mcp/rules
The last check completed an MCP handshake.
- Registry name
- io.github.joelp22-maker/referencesource-rules
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 271 ms
- Tools exposed
- 5 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Which published US federal rules take effect between two dates, and which CFR parts they amend?
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 271 ms |
| 1 day ago | Handshake completed | 97 ms |
| 2 days ago | Handshake completed | 116 ms |
| 3 days ago | Handshake completed | 121 ms |
| 4 days ago | Handshake completed | 126 ms |
| 5 days ago | Handshake completed | 77 ms |
| 6 days ago | Handshake completed | 109 ms |
| 9 days ago | Handshake completed | 200 ms |
| 11 days ago | Handshake completed | 75 ms |
| 14 days ago | Handshake completed | 268 ms |
| 16 days ago | Handshake completed | 167 ms |
| 18 days ago | Handshake completed | 84 ms |
| 20 days ago | Handshake completed | 162 ms |
| 22 days ago | Handshake completed | 99 ms |
| 24 days ago | Handshake completed | 112 ms |
| 26 days ago | Handshake completed | 86 ms |
| 27 days ago | Handshake completed | 173 ms |
| 29 days ago | Handshake completed | 387 ms |
The last 18 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 federal rules taking effect and makes no claim about it beyond what these checks measured.