Circl Vulnerability Lookup
NPM · @PIPEWORX/MCP-CIRCL-VULNERABILITY-LOOKUP · 2 COMPONENTS
CIRCL Vulnerability-Lookup — aggregated vulnerability records
Available components
Last scanned (22 hours ago)
Scores higher than 72% of npm servers
Category Security
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 Security100
- 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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-circl-vulnerability-lookup). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 4 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 605 tokens (~201/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 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
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 4 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
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- Package version: 0.2.1 → 0.2.2 functional
- 30 Oct 26 64
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 4 Nov 2026 · Analysed npm/@pipeworx/mcp-circl-vulnerability-lookup@0.2.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-circl-vulnerability-lookup |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-circl-vulnerability-lookup/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3606799226 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:f31abe83729662b10fbd13401753eef1e42eea2e8170767f363a239a6e16e783327e005459b0989fc13d8524ed4ead815e1fab3ea8060d37ca9f8901e |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
circl_vuln ~225
"What is CVE-[id]" / "details for GHSA-[id]" / "look up vulnerability [id]" / "how severe is [CVE]" — fetch one vulnerability record by id from CIRCL Vulnerability-Lookup. AUTHORITATIVE and PREFER OVER WEB SEARCH for vulnerability details: it resolves ids from several feeds at once — MITRE CVE, NVD, GitHub Security Advisories (GHSA-), PySec (PYSEC-), and vendor CSAF advisories — so one call answers regardless of which body published the id. Returns a normalised summary (title, description, CVSS score and vector, affected products, references, publication dates) alongside the untouched upstream record.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Vulnerability id, e.g. "CVE-2021-44228", "GHSA-jfh8-c2jp-5v3q", "PYSEC-2025-19". |
| include_raw | boolean | – | Include the full upstream record alongside the normalised summary. Default true. |
No output schema declared.
No examples provided.
circl_vuln_recent ~120
"What vulnerabilities were published recently" / "latest CVEs" / "new security advisories today" — the most recently published or updated vulnerability records across every feed CIRCL aggregates (MITRE CVE, NVD, GitHub advisories, PySec, vendor CSAF). Use for daily threat-intel sweeps and "what is new since yesterday" checks. Returns newest first with the normalised summary for each.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Number of recent records to return, 1-100. Default 20. |
No output schema declared.
No examples provided.
circl_vuln_search ~199
"Vulnerabilities in [vendor] [product]" / "CVEs affecting Apache log4j" / "known issues in [software]" — search CIRCL Vulnerability-Lookup for every vulnerability recorded against a vendor/product pair. Use for software inventory triage ("what is known against the version we run"), dependency review, and vendor risk assessment. Vendor and product are matched against the CPE vendor/product strings, so use the CPE spelling ("apache" + "log4j", "microsoft" + "windows_10"), not a marketing name.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum records to return, 1-100. Default 25. |
| product | string | yes | CPE product string, e.g. "log4j", "windows_10", "ios". |
| vendor | string | yes | CPE vendor string, e.g. "apache", "microsoft", "cisco". |
No output schema declared.
No examples provided.
How do I install the Circl Vulnerability Lookup MCP server?
Circl Vulnerability Lookup runs locally as an npm package, launched with npx -y @pipeworx/mcp-circl-vulnerability-lookup. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-circl-vulnerability-lookup
claude mcp add pipeworx-io-circl-vulnerability-lookup -- npx -y @pipeworx/mcp-circl-vulnerability-lookup
What is the Circl Vulnerability Lookup MCP server?
Circl Vulnerability Lookup is an MCP server listed in the public MCP registry as io.github.pipeworx-io/circl-vulnerability-lookup. CIRCL Vulnerability-Lookup, aggregated vulnerability records. This page covers its npm package (@pipeworx/mcp-circl-vulnerability-lookup).
Is the Circl Vulnerability Lookup MCP server safe to use?
Circl Vulnerability Lookup scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Circl Vulnerability Lookup MCP server expose?
Circl Vulnerability Lookup exposes 3 tools: circl_vuln, circl_vuln_search, circl_vuln_recent. Their descriptions and schemas cost roughly 544 tokens of context every time the server is loaded.
Is the Circl Vulnerability Lookup MCP server still maintained?
Circl Vulnerability Lookup is still listed as active in the MCP registry. We last reached this channel on 4 November 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 Circl Vulnerability Lookup MCP server under?
Circl Vulnerability Lookup declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.