Remote MCP · Endpoint
Helixar Security MCP server
No. Helixar Security answered an MCP handshake 8 hours ago.
UpLast checked 8 hours ago
Server URL
https://mcp.helixar.ai/mcp
The last check completed an MCP handshake.
- Registry name
- ai.helixar/mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 293 ms
- Tools exposed
- 2 tools
- Uptime, last 30 days
- 88.2% from 17 checks
- Described by its publisher as
- Security tools for AI agents: scan MCP servers, validate HDP delegation chains, audit releases.
- Website
- https://helixar.ai/connect
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 8 hours ago | Handshake completed | 293 ms |
| 2 days ago | Handshake completed | 231 ms |
| 4 days ago | Handshake completed | 163 ms |
| 5 days ago | Handshake completed | 38 ms |
| 7 days ago | Handshake completed | 203 ms |
| 8 days ago | Failed - the check failed for an unclassified reason | — |
| 9 days ago | Handshake completed | 69 ms |
| 12 days ago | Handshake completed | 83 ms |
| 13 days ago | Handshake completed | 189 ms |
| 15 days ago | Handshake completed | 298 ms |
| 16 days ago | Handshake completed | 137 ms |
| 17 days ago | Handshake completed | 143 ms |
| 18 days ago | Handshake completed | 40 ms |
| 19 days ago | Handshake completed | 164 ms |
| 20 days ago | Failed - the check failed for an unclassified reason | — |
| 21 days ago | Handshake completed | 151 ms |
| 23 days ago | Handshake completed | 187 ms |
The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 17.
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 Helixar Security and makes no claim about it beyond what these checks measured.