Remote MCP · Endpoint
Helixar Security MCP server
No. Helixar Security answered an MCP handshake 2 hours ago.
UpLast checked 2 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
- 384 ms
- Tools exposed
- 2 tools
- Uptime, last 30 days
- 94.4% from 18 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 |
|---|---|---|
| 2 hours ago | Handshake completed | 384 ms |
| 1 day ago | Handshake completed | 159 ms |
| 3 days ago | Handshake completed | 380 ms |
| 3 days ago | Handshake completed | 261 ms |
| 4 days ago | Handshake completed | 280 ms |
| 5 days ago | Handshake completed | 357 ms |
| 7 days ago | Handshake completed | 54 ms |
| 10 days ago | Handshake completed | 170 ms |
| 12 days ago | Handshake completed | 136 ms |
| 15 days ago | Handshake completed | 317 ms |
| 17 days ago | Handshake completed | 177 ms |
| 19 days ago | Handshake completed | 491 ms |
| 21 days ago | Handshake completed | 293 ms |
| 23 days ago | Handshake completed | 231 ms |
| 25 days ago | Handshake completed | 163 ms |
| 26 days ago | Handshake completed | 38 ms |
| 28 days ago | Handshake completed | 203 ms |
| 29 days ago | Failed - the check failed for an unclassified reason | — |
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 Helixar Security and makes no claim about it beyond what these checks measured.