Helixar Security

Security tools for AI agents: scan MCP servers, validate HDP delegation chains, audit releases.

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
83%
Naming quality
80%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~402Tokens (tool definitions)
~1.6 KBTypical response size
Minimal attention impact (0.31% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

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

Remote endpoints

https://mcp.helixar.ai/mcpstreamable-http

What it can do

Tool inventory

Tools (2)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢helixar_inspect_mcp(target, mode, context, api_key)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "target": {
      "type": "string",
      "minLength": 1,
      "description": "MCP server URL or raw manifest JSON string"
    },
    "mode": {
      "type": "string",
      "enum": [
        "quick",
        "deep"
      ],
      "default": "quick"
    },
    "context": {
      "type": "string"
    },
    "api_key": {
      "type": "string"
    }
  },
  "required": [
    "target"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}
⚪helixar_hdp_validate(chain, strict)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "chain": {
      "type": "object",
      "properties": {
        "root_principal": {
          "type": "string"
        },
        "hops": {
          "type": "array",
          "items": {
            "type": "object",
            "properties": {
              "delegator": {
                "type": "string",
                "minLength": 1
              },
              "delegatee": {
                "type": "string",
                "minLength": 1
              },
              "scope": {
                "type": "array",
                "items": {
                  "type": "string"
                },
                "default": []
              },
              "expires_at": {
                "type": "string"
              },
              "signature": {
                "type": "string"
              },
              "purpose": {
                "type": "string"
              }
            },
            "required": [
              "delegator",
              "delegatee"
            ],
            "additionalProperties": false
          },
          "default": []
        },
        "max_hops": {
          "type": "integer",
          "exclusiveMinimum": 0
        }
      },
      "additionalProperties": false
    },
    "strict": {
      "type": "boolean",
      "default": false
    }
  },
  "required": [
    "chain"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded2 tools
verifiedversion not recorded2 tools
verifiedversion not recorded2 tools
verifiedversion not recorded2 tools
verifiedversion not recorded2 tools
verifiedversion not recorded2 tools