Remote MCP · Endpoint
RegLayer Instant Decision Briefs MCP server
No. RegLayer Instant Decision Briefs answered an MCP handshake 2 hours ago.
UpLast checked 2 hours 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
- 559 ms
- Tools exposed
- 10 tools
- Uptime, last 30 days
- 100% from 18 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 |
|---|---|---|
| 2 hours ago | Handshake completed | 559 ms |
| 2 days ago | Handshake completed | 1.07 s |
| 4 days ago | Handshake completed | 508 ms |
| 6 days ago | Handshake completed | 554 ms |
| 7 days ago | Handshake completed | 638 ms |
| 9 days ago | Handshake completed | 554 ms |
| 10 days ago | Handshake completed | 858 ms |
| 11 days ago | Handshake completed | 520 ms |
| 13 days ago | Handshake completed | 965 ms |
| 15 days ago | Handshake completed | 486 ms |
| 17 days ago | Handshake completed | 952 ms |
| 18 days ago | Handshake completed | 466 ms |
| 19 days ago | Handshake completed | 437 ms |
| 20 days ago | Handshake completed | 537 ms |
| 21 days ago | Handshake completed | 719 ms |
| 21 days ago | Handshake completed | 566 ms |
| 23 days ago | Handshake completed | 40 ms |
| 25 days ago | Handshake completed | 577 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 18 responding of 18.
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.