MCP Tenant Isolation vs Vet
A side-by-side look at the MCP Tenant Isolation and Vet MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Tenant Isolation for security work as a local process; choose Vet for security. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
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.
Choose Vet when
- You need dedicated capabilities in the Security domain.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Security | Security |
| Quality signal | 57/100 · Good | 55/100 · Good |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 4 | 1,117 |
| Directory activity | 1 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | 4 | Not listed |
| Full listing | View MCP Tenant Isolation | View Vet |
Tools & capabilities
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.
Vet 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.
MCP Tenant Isolation
{
"mcpServers": {
"mcp-tenant-isolation": {
"command": "npx",
"args": [
"-y",
"mcp-tenant-isolation"
]
}
}
}
Vet
No confirmed install command for Vet yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
MCP Tenant Isolation is categorized under Security and uses a local stdio subprocess. Vet belongs to Security and uses an install path we have not confirmed yet. Pick MCP Tenant Isolation for security work and Vet 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. Vet has no confirmed install command yet — follow its own setup instructions.
MCP Tenant Isolation has no declared pricing — check the project's own site. Vet is listed as free. Auth: no auth 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 mcp-tenant-isolation and safedep-vet as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Tenant Isolation has a quality signal of 57/100 (Good) with 1 views, 0 installs and 4 GitHub stars. Vet has 55/100 (Good) with 4 views, 0 installs and 1,117 GitHub stars.