Helixar Platform MCP server

Which servers in the official MCP registry are Helixar Platform's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-13

← Back to Helixar Platform

Whose server it is

Registry nameai.helixar/mcpverified in the MCP registry

The registry name sits under helixar.ai. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-13

Stateanswerschecked 2026-10-13
Tools2
Server calls itselfhelixar-security
Server version0.0.1
Protocol version2025-06-18

On 2026-10-13 the server answered initialize and tools/list without a sign-in. First answer in 567 ms.

Tools it offers2 tools · read 2026-10-13

helixar_inspect_mcp
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…
helixar_hdp_validate
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.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "helixar": {
      "type": "http",
      "url": "https://mcp.helixar.ai/mcp"
    }
  }
}

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.