io.github.attestd-io/attestd-mcp
NPM · @ATTESTD/MCP · SCANNED AUG 3
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree. 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 26 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @attestd/mcp
claude mcp add attestd-io-attestd-mcp -- npx -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": {
"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.
- 2 Aug 26 +30
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: 100 → unverified ▼ functional
- MCP protocol: unverified → pass ▲ functional
- Maintenance: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- License: unverified → pass ▲ functional
- Schema quality: unverified → excellent ▲ functional
- Licence: MIT functional
- 1 Aug 26 +15
- Malware scan: unverified → pass ▲ security
- 31 Jul 26 −7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +3
- Malware scan: pass → unverified ▼ security
- Dependency health: partial → unverified ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- 28 Jul 26 −21
- Tool coverage: 100 → unverified ▼ functional
- Dependency health: unverified → partial ▲ functional
- First check of Schema quality: unverified functional
- 27 Jul 26 46
First indexed and scored.
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 3 Aug 2026 · Analysed npm/@attestd/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 95 packages
95 packages in the resolved dependency tree · 94 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
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.