Remote MCP · Endpoint
FRTracker — Federal Regulatory Research MCP server
No. FRTracker — Federal Regulatory Research answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://frtracker.app/mcp
The last check completed an MCP handshake.
- Registry name
- app.frtracker/regulatory-research
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-03-26
- Handshake latency
- 62 ms
- Tools exposed
- 10 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Source-linked US federal regulations: CFR provision history, obligations, rules, comments.
- Repository
- https://github.com/ajleahey/frtracker
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 62 ms |
| 10 hours ago | Handshake completed | 678 ms |
| 1 day ago | Handshake completed | 76 ms |
| 2 days ago | Handshake completed | 460 ms |
| 4 days ago | Handshake completed | 57 ms |
| 4 days ago | Handshake completed | 440 ms |
| 5 days ago | Handshake completed | 62 ms |
| 6 days ago | Handshake completed | 60 ms |
| 8 days ago | Handshake completed | 496 ms |
| 11 days ago | Handshake completed | 72 ms |
| 13 days ago | Handshake completed | 85 ms |
| 16 days ago | Handshake completed | 330 ms |
| 18 days ago | Handshake completed | 119 ms |
| 20 days ago | Handshake completed | 650 ms |
| 22 days ago | Handshake completed | 82 ms |
| 24 days ago | Handshake completed | 487 ms |
| 26 days ago | Handshake completed | 386 ms |
| 27 days ago | Handshake completed | 40 ms |
| 29 days ago | Handshake completed | 362 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 31 responding of 31.
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 FRTracker — Federal Regulatory Research and makes no claim about it beyond what these checks measured.