Remote MCP · Endpoint
Collar Guardrail — Pre-Trade Risk Layer MCP server
Yes, as of 1 hour ago: the server returned an HTTP error.
DownLast checked 1 hour ago
Server URL
https://api.collarguardrail.com/mcp-http/mcp
The last check failed: the server returned an HTTP error.
- Registry name
- io.github.aiguardrail/backend
- Transport
- Streamable HTTP
- Protocol negotiated
- Not measured yet
- Handshake latency
- —
- Tools exposed
- 6 tools
- Uptime, last 30 days
- 88.9% from 18 checks
- Described by its publisher as
- Deterministic pre-trade risk checks for AI agents on Robinhood Chain. Returns allow/warn/deny.
- Website
- https://collarguardrail.com/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Failed - the server returned an HTTP error | — |
| 1 day ago | Failed - the server returned an HTTP error | — |
| 3 days ago | Handshake completed | 325 ms |
| 3 days ago | Handshake completed | 327 ms |
| 4 days ago | Handshake completed | 164 ms |
| 5 days ago | Handshake completed | 317 ms |
| 7 days ago | Handshake completed | 234 ms |
| 10 days ago | Handshake completed | 191 ms |
| 12 days ago | Handshake completed | 317 ms |
| 15 days ago | Handshake completed | 208 ms |
| 17 days ago | Handshake completed | 154 ms |
| 19 days ago | Handshake completed | 138 ms |
| 21 days ago | Handshake completed | 353 ms |
| 23 days ago | Handshake completed | 341 ms |
| 25 days ago | Handshake completed | 328 ms |
| 26 days ago | Handshake completed | 142 ms |
| 28 days ago | Handshake completed | 337 ms |
| 29 days ago | Handshake completed | 309 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 27 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 Collar Guardrail — Pre-Trade Risk Layer and makes no claim about it beyond what these checks measured.