Hejdar Mcp vs Kakunin Mcp — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Hejdar Mcp vs Kakunin Mcp
In-depth architectural comparison of the Hejdar Mcp and Kakunin Mcp MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Hejdar Mcp
Security · Local stdio
Quality: 40/100 (Fair) | Auth: API Key required
Kakunin Mcp
Security · Local stdio
Quality: 51/100 (Good) | Auth: API Key required
Verdict Summary: Choose Hejdar Mcp if you need specialized Security tools running via a local process. Choose Kakunin Mcp if your workspace requires Security integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Hejdar Mcp when:
You need dedicated capabilities in the Security domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: HEJDAR_API_KEY, HEJDAR_API_URL.
Primary tools included: Evaluate actions of types READ, WRITE, DELETE, TRANSFER, EXECUTE, Return policy decision with reason, policy ID, and risk level, Supports free-form context metadata for evaluation.
Runtime policy enforcement for AI agents. Evaluate actions against organization policies before execution, with observe and enforce modes.
Compliance and identity for AI agents — verify an agent's certificate scope, read its behavioral risk score, and append to an immutable audit trail. X.509 identity issued via AWS KMS; MiCA / EU AI Act aligned. npx -y @kakunin/mcp
Hejdar Mcp is categorized under Security and uses a local stdio subprocess. In contrast, Kakunin Mcp belongs to Security using local stdio subprocess. Select Hejdar Mcp when you need capabilities focused on security and Kakunin Mcp when you require tools for security.
Check whether this agent is authorised to perform an action before executing it. Verifies the active X.509 certificate, permitted_actions scope, financial limits, and revocation status.
check_risk_score
Retrieve the agent's rolling 30-day risk score, band (`low`/`medium`/`high`), drift trend, and actionable guidance. No input required.
audit_log_append
Append a behavioral event to the agent's immutable audit log. Returns risk score + transaction ID. Events scoring ≥ 0.85 auto-trigger a certificate revocation check.