io.github.attestd-io/attestd-mcp
NPM · @ATTESTD/MCP · SCANNED SEP 22
CVE and supply chain checks for MCP clients. Covers infrastructure, PyPI, and npm packages.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 76 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 370 tokens (~123/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.attestd-io/attestd-mcp server?
io.github.attestd-io/attestd-mcp runs locally as an npm package, launched with npx -y @attestd/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @attestd/mcp
claude mcp add attestd-io-attestd-mcp -- npx -y @attestd/mcp
{
"mcpServers": {
"attestd-io-attestd-mcp": {
"command": "npx",
"args": [
"-y",
"@attestd/mcp"
]
}
}
} {
"servers": {
"attestd-io-attestd-mcp": {
"command": "npx",
"args": [
"-y",
"@attestd/mcp"
]
}
}
} codex mcp add attestd-io-attestd-mcp -- npx -y @attestd/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"attestd-io-attestd-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@attestd/mcp"
],
"enabled": true
}
}
} openclaw mcp add attestd-io-attestd-mcp --command npx --arg -y --arg @attestd/mcp
mcp_servers:
attestd-io-attestd-mcp:
command: "npx"
args: ["-y", "@attestd/mcp"] {
"McpServers": {
"attestd-io-attestd-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@attestd/mcp"
]
}
}
} assistant mcp add attestd-io-attestd-mcp -t stdio -c npx -a -y @attestd/mcp
{
"mcpServers": {
"attestd-io-attestd-mcp": {
"command": "npx",
"args": [
"-y",
"@attestd/mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 22 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Sept 2026 · Analysed npm/@attestd/mcp@0.2.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_batch_vulnerabilities ~131
Check 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.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | Products to check. Maximum 100 per call. Each item costs one API call. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | Number of items returned. |
| results | array | yes | – |
No examples provided.
check_package_vulnerability ~164
Check 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.
| Name | Type | Req | Description |
|---|---|---|---|
| product | string | yes | Package or product slug, e.g. "nginx", "runc", "@bitwarden/cli", "litellm" |
| version | string | yes | Exact version string, e.g. "1.20.0" |
| Name | Type | Req | Description |
|---|---|---|---|
| activelyExploited | boolean | – | True when the version appears in the CISA KEV catalog. |
| authenticationRequired | boolean | – | True only when all matching CVEs require authentication. |
| confidence | number | – | Synthesis confidence from 0.0 to 1.0. |
| cveIds | array | – | CVE IDs contributing to the risk assessment. |
| error | string | – | Error message when the tool returns isError. |
| fixedVersion | string | – | Earliest clean version to recommend. Omitted or null when unknown. |
| message | string | – | Explanation when outsideCoverage is true. |
| outsideCoverage | boolean | – | True when Attestd has no CVE data for this product. Unknown risk, not safe. |
| patchAvailable | boolean | – | True when a fixed version with no critical/high CVEs is known. |
| remoteExploitable | boolean | – | True when any matching CVE is remotely exploitable. |
| riskState | string | – | Risk band: "critical", "high", "elevated", "low", "none", or null when outside coverage. |
| supplyChainCompromised | boolean | – | True when a malicious PyPI or npm publish was detected. |
| supplyChainDescription | string | – | Human-readable supply-chain event description when present. |
| typosquat | object | – | Typosquat warning when the package name resembles a known product. |
No examples provided.
list_covered_products ~75
Returns infrastructure product slugs covered by Attestd for CVE checks. PyPI and npm packages also work with check_package_vulnerability even when absent from this list. Call this first if you are unsure whether an infrastructure slug is supported. Uses a static bundled list. No /v1/check API call for this tool.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | Number of covered infrastructure products. |
| products | array | yes | Covered products with slug and display name. |
No examples provided.
What is the io.github.attestd-io/attestd-mcp server?
io.github.attestd-io/attestd-mcp is listed in the public MCP registry as io.github.attestd-io/attestd-mcp. CVE and supply chain checks for MCP clients. Covers infrastructure, PyPI, and npm packages. This page covers its npm package (@attestd/mcp).
Is the io.github.attestd-io/attestd-mcp server safe to use?
io.github.attestd-io/attestd-mcp scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.attestd-io/attestd-mcp server expose?
io.github.attestd-io/attestd-mcp exposes 3 tools: check_package_vulnerability, list_covered_products, check_batch_vulnerabilities. Their descriptions and schemas cost roughly 370 tokens of context every time the server is loaded.
Is the io.github.attestd-io/attestd-mcp server still maintained?
io.github.attestd-io/attestd-mcp is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.attestd-io/attestd-mcp server under?
io.github.attestd-io/attestd-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.