Remote MCP · Endpoint
RegLayer Instant Decision Briefs MCP server
No. RegLayer Instant Decision Briefs answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://reglayer.ai/mcp
The last check completed an MCP handshake.
- Registry name
- ai.reglayer/instant-decision-briefs
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 532 ms
- Tools exposed
- 10 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Company-specific regulatory assessments for concrete business questions, as structured data or PDF.
- Website
- https://reglayer.ai/agents
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 532 ms |
| 12 hours ago | Handshake completed | 161 ms |
| 1 day ago | Handshake completed | 1.20 s |
| 2 days ago | Handshake completed | 744 ms |
| 4 days ago | Handshake completed | 680 ms |
| 4 days ago | Handshake completed | 529 ms |
| 5 days ago | Handshake completed | 518 ms |
| 7 days ago | Handshake completed | 1.18 s |
| 8 days ago | Handshake completed | 516 ms |
| 11 days ago | Handshake completed | 909 ms |
| 13 days ago | Handshake completed | 514 ms |
| 16 days ago | Handshake completed | 183 ms |
| 18 days ago | Handshake completed | 904 ms |
| 20 days ago | Handshake completed | 559 ms |
| 22 days ago | Handshake completed | 1.07 s |
| 24 days ago | Handshake completed | 508 ms |
| 26 days ago | Handshake completed | 554 ms |
| 28 days ago | Handshake completed | 638 ms |
| 29 days ago | Handshake completed | 554 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 RegLayer Instant Decision Briefs and makes no claim about it beyond what these checks measured.