Helixar Security
REMOTE · MCP.HELIXAR.AI · SCANNED SEP 20
Security tools for AI agents: scan MCP servers, validate HDP delegation chains, audit releases.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability60
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 181 tokens (~90/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage72
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 17% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Helixar Security MCP server?
Helixar Security is a hosted endpoint at https://mcp.helixar.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.helixar.ai
claude mcp add --transport http ai-helixar-mcp 'https://mcp.helixar.ai/mcp'
{
"mcpServers": {
"ai-helixar-mcp": {
"url": "https://mcp.helixar.ai/mcp"
}
}
} {
"servers": {
"ai-helixar-mcp": {
"type": "http",
"url": "https://mcp.helixar.ai/mcp"
}
}
} [mcp_servers.ai-helixar-mcp] url = "https://mcp.helixar.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ai-helixar-mcp": {
"type": "remote",
"url": "https://mcp.helixar.ai/mcp",
"enabled": true
}
}
} openclaw mcp add ai-helixar-mcp --url 'https://mcp.helixar.ai/mcp' --transport streamable-http
mcp_servers:
ai-helixar-mcp:
url: "https://mcp.helixar.ai/mcp" {
"McpServers": {
"ai-helixar-mcp": {
"Transport": "http",
"Url": "https://mcp.helixar.ai/mcp"
}
}
} assistant mcp add ai-helixar-mcp -t streamable-http -u 'https://mcp.helixar.ai/mcp'
{
"mcpServers": {
"ai-helixar-mcp": {
"type": "http",
"url": "https://mcp.helixar.ai/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Aug 26 0
- Schema quality: unverified → fair ▲ functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://mcp.helixar.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=helixar.ai | CN=WE1,O=Google Trust Services,C=US | 23 Aug 2026 | 21 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 9acf0f0eab304fe81334c7f1abeb24fd |
| SANs: helixar.ai, mcp.helixar.ai, *.mcp.helixar.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.helixar.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| helixar.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.helixar.ai/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.helixar.ai/mcp | HTTPS enforced | 301 | https://mcp.helixar.ai/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
helixar_hdp_validate ~75
Validate an HDP delegation chain against IETF draft-helixar-hdp-agentic-delegation-00. Surfaces scope escalations, depth violations, expired hops, missing signatures. Every output cites the IETF draft and Zenodo DOI.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | object | yes | – |
| strict | boolean | – | – |
No output schema declared.
No examples provided.
helixar_inspect_mcp ~106
Scan an MCP server (URL or raw manifest JSON) against Helixar's Sentinel detection rules. Returns risk score, findings, and a Claude-generated security brief. Quick mode is free + authless (top 8 rules); deep mode runs all 26 rules with an api_key.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | – | – |
| context | string | – | – |
| mode | string | – | – |
| target | string | yes | MCP server URL or raw manifest JSON string |
No output schema declared.
No examples provided.
What is the Helixar Security MCP server?
Helixar Security is an MCP server listed in the public MCP registry as ai.helixar/mcp. Security tools for AI agents: scan MCP servers, validate HDP delegation chains, audit releases. This page covers its hosted endpoint (https://mcp.helixar.ai/mcp).
Is the Helixar Security MCP server safe to use?
Helixar Security scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Helixar Security MCP server expose?
Helixar Security exposes 2 tools: helixar_inspect_mcp, helixar_hdp_validate. Their descriptions and schemas cost roughly 181 tokens of context every time the server is loaded.
Does the Helixar Security MCP server require authentication?
No. We connected to Helixar Security without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Helixar Security MCP server still maintained?
Helixar Security is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.