Shield vs MCP Tenant Isolation
A side-by-side look at the Shield 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 Shield 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 Shield when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
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 | 63/100 · Good | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 11 | 4 |
| Directory activity | 6 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 4 |
| Full listing | View Shield | View MCP Tenant Isolation |
Tools & capabilities
Shield tools
No tool names declared yet. Check the project README from 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.
Shield
{
"mcpServers": {
"aperionai-shield": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-postgres"
]
}
}
}
MCP Tenant Isolation
{
"mcpServers": {
"mcp-tenant-isolation": {
"command": "npx",
"args": [
"-y",
"mcp-tenant-isolation"
]
}
}
}
Frequently asked questions
Shield is categorized under Security and uses a local stdio subprocess. MCP Tenant Isolation belongs to Security and uses a local stdio subprocess. Pick Shield 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.
Shield is listed as free. Auth: no auth required. 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 aperionai-shield and mcp-tenant-isolation as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Shield has a quality signal of 63/100 (Good) with 6 views, 0 installs and 11 GitHub stars. MCP Tenant Isolation has 57/100 (Good) with 0 views, 0 installs and 4 GitHub stars.