AtlaSent MCP Server vs Kakunin MCP
A side-by-side look at the AtlaSent MCP Server and Kakunin MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose AtlaSent MCP Server for security work as a local process; choose Kakunin MCP for security as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose AtlaSent MCP Server when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
ATLASENT_MODE, ATLASENT_API_KEY, ATLASENT_BASE_URL. - You want tools like
evaluate, verify_permit, deploy_service.
Choose Kakunin MCP when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
KAKUNIN_API_KEY, KAKUNIN_AGENT_ID. - You want tools like
verify_agent_scope, check_risk_score, audit_log_append.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Security | Security |
| Quality signal | 63/100 · Good | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Freemium | Freemium |
| Required env vars | ATLASENT_MODEATLASENT_API_KEYATLASENT_BASE_URL | KAKUNIN_API_KEYKAKUNIN_AGENT_ID |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 1 |
| Directory activity | 1 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | 20 | 3 |
| Full listing | View AtlaSent MCP Server | View Kakunin MCP |
Tools & capabilities
AtlaSent MCP Server tools 20
evaluateCall this BEFORE performing any sensitive action. Returns a Decision: `allow` (verify the returned permit_token at the execution boundary before proceeding), `deny` (you MUST NOT proceed), or `hold` (do not proceed; route for review).verify_permitCall this AFTER `evaluate` returns allow and BEFORE the protected native side effect. It verifies the permit for the presented execution context. Proceed only when `valid` is true; expired, invalid, replayed, mismatched, or error outcomes must block the action.deploy_serviceExample protected tool. Every call is authorized AND its Permit is verified by AtlaSent before the deploy runs. Denied, held, expired, replayed, mismatched, or unverifiable calls are blocked and never touch the target system.atlasent_evaluateEvaluate an action against your published AtlaSent policies. Returns allow/deny/hold/escalate with a permitToken on allow. Use this when ATLASENT_MODE=remote and you need to gate an action against your hosted policy engine. For agent.* actions the result may carry bound_payload_hash and bound_actor_id: pass them to verify_permit as payload_hash and actor_id, since the permit is bound to them.atlasent_list_policiesList all constraint bundles / policies for this organization.atlasent_list_audit_eventsRetrieve recent evaluation events from the audit log.atlasent_explain_authorityExplain why a principal currently has (or lacks) authority for a scope. Answers 'why may principal P exercise scope/action A in organization O right now?' — strictly read-only, does not change /v1-evaluate, /v1-verify-permit, or any deny/hold/allow semantics; it explains the same facts those paths already read. Every matched authority mechanism (direct_grant, delegation, role_capability) is reported as its own path entry; every excluded or ambiguous relationship is reported as its own unresolved finding.atlasent_integrity_auditAudit the organization's authority graph for internal inconsistency and return the report verbatim. Strictly read-only; changes no policy, permit, or decision. THIS IS NOT A PASS/FAIL HEALTH CHECK and the tool synthesizes no verdict of its own. Each finding carries a three-way `classification`: `defect` is a genuine inconsistency; `non_exercisable` is frequently the CORRECT, healthy state (e.g. an expired grant that is supposed to be expired) and must not be read as a failure; `unresolved` means the proposition COULD NOT BE VERIFIED and must never be treated as clean. Read `summary.audited_scope` before drawing any conclusion from an empty findings list — a short decision window is not an absence of findings. If the audit cannot complete, the server refuses rather than returning a partial report, and this tool surfaces that as an error — never an empty report.atlasent_list_permitsList issued permit tokens for audit and monitoring.atlasent_await_approvalWait for a person to approve or reject a held action in the AtlaSent console. Use the approval_request_id from a 'hold' result. This tool cannot approve anything; it only waits. If approved, it returns a permit_token that you MUST verify with verify_permit before running the action. Any other outcome (rejected, expired, timed out) means the action must not run.atlasent_lookup_actionLook up canonical action specifications from the Authorization Intelligence Library. Returns the permanent canon_id, gate flags (requires_human_approval, requires_mfa, requires_verified_actor, requires_state_snapshot), authorization pattern, risk posture, AI risk classification, regulatory mappings, evidence requirements, and the action's knowledge-graph relationships (what it requires and produces, and which frameworks / control objectives it satisfies) for every governed action type in the Canon. Use `slug` for an exact match (e.g. 'production.deploy') or `query` to describe what you want to do in plain language (e.g. 'deploy the api service to prod', 'grant admin access', 'close the books'). `query` is ranked offline against the vendored Canon and returns a `retrieval` block with `confidence` = confident | ambiguous | none — act only on `confident`; the tool never invents an action type, and a `none` result means the Canon has no such action (see the hint). Omit both to list the full Canon.atlasent_atlas_lookupLook up a canonical AtlaSent concept from the Knowledge Atlas — the compiled graph of the system's own vocabulary (Caller, Authority, Policy, Decision, Permit, Verification, Evidence, Audit Chain, Gate, Trust Root, ...). Returns the concept's canonical definition (its source-of-truth doc), its relationships (what it depends on and what depends on it), the surfaces that realize it, and its ADR / API / SDK / implementation anchors — so every AI host reasons from the same canonical knowledge instead of guessing. Use `id` for an exact concept id (e.g. 'permit', 'audit-chain', 'gate') or `query` for a case-insensitive substring search across id, term, and definition. Omit both to list every concept.- +8 more on the listing page
Kakunin MCP tools 3
verify_agent_scopeCheck 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_scoreRetrieve the agent's rolling 30-day risk score, band (`low`/`medium`/`high`), drift trend, and actionable guidance. No input required.audit_log_appendAppend 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.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
AtlaSent MCP Server
{
"mcpServers": {
"atlasent-mcp-server": {
"command": "npx",
"args": [
"-y",
"@atlasent/mcp-server"
],
"env": {
"ATLASENT_MODE": "YOUR_ATLASENT_MODE_HERE",
"ATLASENT_API_KEY": "YOUR_ATLASENT_API_KEY_HERE",
"ATLASENT_BASE_URL": "YOUR_ATLASENT_BASE_URL_HERE"
}
}
}
}
Kakunin MCP
{
"mcpServers": {
"kakunin-ai-kakunin-mcp": {
"command": "npx",
"args": [
"-y",
"@kakunin/mcp"
],
"env": {
"KAKUNIN_API_KEY": "YOUR_KAKUNIN_API_KEY_HERE",
"KAKUNIN_AGENT_ID": "YOUR_KAKUNIN_AGENT_ID_HERE"
}
}
}
}
Frequently asked questions
AtlaSent MCP Server is categorized under Security and uses a local stdio subprocess. Kakunin MCP belongs to Security and uses a local stdio subprocess. Pick AtlaSent MCP Server for security work and Kakunin MCP for security.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
AtlaSent MCP Server is listed as freemium — a free tier with paid plans. Kakunin MCP is listed as freemium — a free tier with paid plans. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add atlasent-mcp-server and kakunin-ai-kakunin-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, AtlaSent MCP Server has a quality signal of 63/100 (Good) with 1 views, 0 installs and 0 GitHub stars. Kakunin MCP has 59/100 (Good) with 5 views, 0 installs and 1 GitHub stars.