Developer · Remote MCP server
Helixar Security
Security tools for AI agents: scan MCP servers, validate HDP delegation chains, audit releases.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
ai.helixar/mcp- Version
- 0.0.1
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-04-27
- Updated
- 2026-04-27
- Publisher
- ai.helixar
- Namespace
- Namespace verified by the MCP Registry via the domain helixar.ai · how
- Website
- helixar.ai/connect
- Repository
- github.com/Helixar-AI/helixar-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.helixar.ai/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- helixar-security 0.0.1 · protocol 2025-06-18
- Tools discovered
- 2:
helixar_inspect_mcp,helixar_hdp_validate - Checked on
- 2026-10-05
How to connect Helixar Security
Helixar Security is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.helixar.ai/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| HEIDESDeterministic code analysis harness giving AI agents senses, memory and judgment for code. | Local · stdio |
| HeirmosPersistent memory shared across Claude, ChatGPT, Grok and other MCP clients. | Remote · HTTPLive check: sign-in required |
| Helena Good: Scientific Infrastructure SponsorshipFund or spread Helena's public scientific infrastructure to keep it free to use and independent. | Remote · HTTPLive check: ✓ handshake |
| HeliographRun commands on a machine you cannot SSH into. Air-gapped, bastion-only, change-controlled. | Local · stdio |
| Helm MCPThe full Helm CLI surface as 46 MCP tools, backed by the Helm v3 and v4 Go SDKs. | Local · stdio |
| HelmdeckSelf-hosted MCP server: sandboxed browser, desktop, vision, code-edit packs for any agent. | Local · stdio |
| Hemrock MCPHemrock financial modeling prompts: context primers, task prompts, checks, and best practices. | Remote · HTTPLive check: ✓ handshake |
| hepcloud.netManage HepCloud (Turkish cloud) servers and managed PostgreSQL from your AI assistant. OAuth 2.1. | Remote · HTTPLive check: sign-in required |