Attestd MCP vs MCP Tenant Isolation
A side-by-side look at the Attestd MCP 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 Attestd MCP 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 Attestd MCP when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
ATTESTD_API_KEY. - You want tools like
check_package_vulnerability, list_covered_products, check_batch_vulnerabilities.
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 | 60/100 · Good | 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 | ATTESTD_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 4 |
| Directory activity | 3 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 4 | 4 |
| Full listing | View Attestd MCP | View MCP Tenant Isolation |
Tools & capabilities
Attestd MCP tools 4
check_package_vulnerabilityCheck whether a software package or infrastructure product version has known CVE vulnerabilities or a confirmed supply chain compromise. Call this before adding, updating, or recommending any npm, PyPI, or infrastructure dependency, including mid-conversation when a developer asks about installing or upgrading a package. outsideCoverage=true means Attestd has no data for that product; treat as unknown risk, not safe. Covers infrastructure products (nginx, PostgreSQL, Redis, Docker, Kubernetes, etc.) and PyPI/npm packages.list_covered_productsReturns Attestd-covered products for CVE checks. With an API key, returns live data from GET /v1/products (CVE infrastructure slugs plus monitored supply chain packages). Without a key, returns the static bundled infrastructure list. PyPI and npm packages also work with check_package_vulnerability even when absent from this list.check_batch_vulnerabilitiesCheck up to 100 software packages or infrastructure products in a single request. Each item is billed as one API call. Use this instead of multiple check_package_vulnerability calls when you need to audit a lockfile, manifest, or dependency list. Items outside Attestd coverage return outsideCoverage=true and should be treated as unknown risk, not safe. A 429 is returned before any results are delivered if the batch would exceed your monthly quota; no calls are billed in that case.get_cve_detailsReturn full details for a single CVE id (CVSS, EPSS, KEV status, affected products). Use when you need context on a specific CVE before recommending a patch or explaining risk to a developer.
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.
Attestd MCP
{
"mcpServers": {
"attestd-mcp": {
"command": "npx",
"args": [
"-y",
"@attestd/mcp"
],
"env": {
"ATTESTD_API_KEY": "YOUR_ATTESTD_API_KEY_HERE"
}
}
}
}
MCP Tenant Isolation
{
"mcpServers": {
"mcp-tenant-isolation": {
"command": "npx",
"args": [
"-y",
"mcp-tenant-isolation"
]
}
}
}
Frequently asked questions
Attestd MCP is categorized under Security and uses a local stdio subprocess. MCP Tenant Isolation belongs to Security and uses a local stdio subprocess. Pick Attestd MCP 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.
Attestd MCP 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 attestd-mcp and mcp-tenant-isolation as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Attestd MCP has a quality signal of 60/100 (Good) with 3 views, 0 installs and 0 GitHub stars. MCP Tenant Isolation has 57/100 (Good) with 0 views, 0 installs and 4 GitHub stars.