Kakunin vs Monitor
A side-by-side look at the Kakunin and Monitor MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Kakunin for monitoring work as a local process; choose Monitor for monitoring as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Kakunin when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
- 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.
Choose Monitor when
- You need dedicated capabilities in the Monitoring domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Monitoring | Monitoring |
| Quality signal | 52/100 · Good | 64/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Freemium |
| Required env vars | KAKUNIN_API_KEYKAKUNIN_AGENT_ID | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 1,309 |
| Directory activity | 1 views 0 installs 0 upvotes | 5 views 0 installs 0 upvotes |
| Tools | 3 | Not listed |
| Full listing | View Kakunin | View Monitor |
Tools & capabilities
Kakunin 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.
Monitor tools
No tool names declared yet. Check the project README from the listing page.
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.
Kakunin
{
"mcpServers": {
"kakunin-2": {
"command": "npx",
"args": [
"-y",
"@kakunin/mcp"
],
"env": {
"KAKUNIN_API_KEY": "YOUR_KAKUNIN_API_KEY_HERE",
"KAKUNIN_AGENT_ID": "YOUR_KAKUNIN_AGENT_ID_HERE"
}
}
}
}
Monitor
{
"mcpServers": {
"betterdb-inc-monitor": {
"command": "npx",
"args": [
"-y",
"@betterdb/monitor"
]
}
}
}
Frequently asked questions
Kakunin is categorized under Monitoring and uses a local stdio subprocess. Monitor belongs to Monitoring and uses a local stdio subprocess. Pick Kakunin for monitoring work and Monitor for monitoring.
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.
Kakunin has no declared pricing — check the project's own site. Monitor 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 kakunin-2 and betterdb-inc-monitor as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Kakunin has a quality signal of 52/100 (Good) with 1 views, 0 installs and 1 GitHub stars. Monitor has 64/100 (Good) with 5 views, 0 installs and 1,309 GitHub stars.