Keel vs MCP Tenant Isolation
A side-by-side look at the Keel and MCP Tenant Isolation MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Keel for security work as a local process; choose MCP Tenant Isolation 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 Keel when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- You want tools like
begin_engagement, draft_waves, execute_wave.
Choose MCP Tenant Isolation when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- You want tools like
scan_tenant_isolation, list_tenant_isolation_rules, explain_tenant_isolation_rule.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Security | Security |
| Quality signal | 49/100 · Fair | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 4 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 13 | 4 |
| Full listing | View Keel | View MCP Tenant Isolation |
Tools & capabilities
Keel tools 13
begin_engagementRegister scope and traffic ceilingsdraft_wavesPropose reachability + template micro-waves; no trafficexecute_waveQueue one background jobwave_statusStage, progress, result; omit `job_id` to listcancel_waveStop a queued or running scannerquery_cardsPrioritized semantic cardssecond_lookRe-run only the originating Nuclei templateassess_exploitabilityCandidate impact, missing evidence, negative control, playbooksstate_impactRecord a hunter hypothesisdraft_proofAllowlisted proof plan; no trafficexecute_proofRun the GET-only playbookengagement_healthCooldowns, budgets, pending waves- +1 more on the listing page
MCP Tenant Isolation tools 4
scan_tenant_isolationScan a project path. Returns structured findings with completeness, coverage, concern families, and receipt.list_tenant_isolation_rulesReturns all 57 rules with metadata. Filterable by category.explain_tenant_isolation_ruleReturns rule details, OWASP mapping, CWE IDs, fix suggestions.suppress_tenant_isolation_findingAdd a suppression with reason, approver, controls, and expiry.
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.
Keel
{
"mcpServers": {
"keel": {
"command": "uvx",
"args": [
"keel"
]
}
}
}
MCP Tenant Isolation
{
"mcpServers": {
"mcp-tenant-isolation": {
"command": "npx",
"args": [
"-y",
"mcp-tenant-isolation"
]
}
}
}
Frequently asked questions
Keel is categorized under Security and uses a local stdio subprocess. MCP Tenant Isolation belongs to Security and uses a local stdio subprocess. Pick Keel for security work and MCP Tenant Isolation 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.
Keel has no declared pricing — check the project's own site. MCP Tenant Isolation has no declared pricing — check the project's own site. 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 keel and mcp-tenant-isolation as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Keel has a quality signal of 49/100 (Fair) with 0 views, 0 installs and 2 GitHub stars. MCP Tenant Isolation has 57/100 (Good) with 0 views, 0 installs and 4 GitHub stars.