Server data from the Official MCP Registry
CIRCL Vulnerability-Lookup — aggregated vulnerability records
About
CIRCL Vulnerability-Lookup — aggregated vulnerability records
Remote endpoints: streamable-http: https://gateway.pipeworx.io/circl-vulnerability-lookup/mcp
Security Report
Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Package registry verified. Imported from the Official MCP Registry. Trust signals: trusted author (2292/2294 approved).
47 tools verified · Open access · 1 issue found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
Permissions Required
This plugin requests these system permissions. Most are normal for its category.
What You'll Need
Set these up before or after installing:
Environment variable: PIPEWORX_API_KEY
How to Install & Connect
Available as Local & Remote
This plugin can run on your machine or connect to a hosted endpoint. during install.
Documentation
View on GitHubFrom the project's GitHub README.
@pipeworx/circl-vulnerability-lookup
Vulnerability records from CIRCL's Vulnerability-Lookup service, which resolves one id against several upstream feeds at once — MITRE CVE, NVD, GitHub Security Advisories, PySec and vendor CSAF advisories.
Part of Pipeworx — an MCP gateway connecting AI agents to 1863+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
Tools
circl_vuln(id, include_raw?)— one vulnerability by id. AcceptsCVE-,GHSA-,PYSEC-and vendor advisory ids alike. Returns a normalised summary (title, description, CVSS score/vector, affected products, references, dates) plus the untouched upstream record.circl_vuln_search(vendor, product, limit?)— every vulnerability recorded against a CPE vendor/product pair, newest first, tagged with the feed each record came from.circl_vuln_recent(limit?)— the most recently published or updated records across every aggregated feed.
Auth
Keyless.
Data sources
- https://vulnerability.circl.lu/api/vulnerability/{id} — one record by id.
- https://vulnerability.circl.lu/api/search/{vendor}/{product} — search.
- https://vulnerability.circl.lu/api/last/{n} — recent records.
Operated by CIRCL (Computer Incident Response Center Luxembourg).
Traps
- An unknown id answers
{}with HTTP 200. That is a silent zero — parsed naively it reads as a successful empty record.circl_vulnthrows a named miss instead. - The real paths are not the ones the names suggest. Search is
/api/search/{vendor}/{product}and the recent feed is/api/last/{n}./api/vulnerability/search/...and/api/vulnerability/lastare both 404. - Records arrive in three different schemas, and one
/api/lastresponse mixes all three:- CVE JSON 5.x —
cveMetadata+containers.cna - OSV —
id/details/affected/severity - CSAF —
document/product_tree/vulnerabilitiessummarize()normalises the shared fields across all three;rawkeeps the original. Do not assumecontainers.cnaexists.
- CVE JSON 5.x —
- CVSS lives under a version-specific key (
cvssV3_1,cvssV4_0, …) insidecontainers.cna.metrics[], so the code scans the metric objects rather than reaching for a fixed path. OSV records carry only a vector string inseverity[].score, with no numeric base score. - Vendor/product are matched against CPE strings, not marketing names — use
microsoft/windows_10, notMicrosoft Windows 10. - CIRCL rate-limits by source IP, and publishes the limits at
https://vulnerability.circl.lu/.well-known/api-policy.json: 20 requests
per minute anonymously, 40 with an
X-API-KEY. It does sendRetry-After(observed: 59) plusX-RateLimit-Limit/-Remaining/-Reset, and the 429 error here quotes it. This pack is keyless and stays inside the anonymous bucket — one tool call is one upstream request. If we ever need the higher tier, it is a header, not a rebuild. - The 429 is per backend worker, not global. Measured 2026-09-17: three
consecutive anonymous requests from one IP reported
x-ratelimit-remainingof 0, then 19, then 3, and one URL kept 429-ing while the next id answered 200 instantly. So a 429 here frequently says nothing about your actual usage —circlJson()retries up to 3 times before surfacing it. Do not read a single 429 as "we are being throttled".
Related packs
nvd (NVD directly, platform-keyed) and osv (OSV.dev, open-source package
advisories) cover single upstreams. This pack is the cross-feed id resolver: use
it when you have an id and do not know which body published it.
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"circl-vulnerability-lookup": {
"url": "https://gateway.pipeworx.io/circl-vulnerability-lookup/mcp"
}
}
}
What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/circl-vulnerability-lookup/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1863+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
No MCP client? Call it over HTTP
curl -X POST https://gateway.pipeworx.io/v1/tools/circl_vuln \
-H 'Content-Type: application/json' \
-d '{"id":"CVE-2014-0160","include_raw":false}'
No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/circl_vuln. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
Run it from npm
@pipeworx/mcp-circl-vulnerability-lookup is a local stdio bridge to the Pipeworx gateway: your MCP client
starts it with npx, and it forwards every call to the same
https://gateway.pipeworx.io/circl-vulnerability-lookup/mcp endpoint shown above. It needs network access;
there is no offline mode.
{
"mcpServers": {
"circl-vulnerability-lookup": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-circl-vulnerability-lookup"]
}
}
}
Without a key it calls anonymously, capped at 50 calls a day. A free account
raises that to 200 a day: get a key at https://pipeworx.io/signup and add
"env": { "PIPEWORX_API_KEY": "<your key>" } to the server entry.
The key is sent as a Bearer token, the same way a hosted connection sends it,
so calls are metered and billed exactly as they are there.
It lists only this pack's tools by default. Set PIPEWORX_META_TOOLS=1 to
also list ask_pipeworx and the other gateway-wide tools.
Behind an HTTPS proxy: Node's built-in fetch does not read HTTPS_PROXY by
default. Newer Node releases honour it when NODE_USE_ENV_PROXY=1 is set; check
your Node version's documentation.
Using with ask_pipeworx
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Circl Vulnerability Lookup data" })
The gateway picks the right tool and fills the arguments automatically.
More
License
MIT
Reviews
No reviews yet
Be the first to review this server!
More Security MCP Servers
Toleno
Freeby Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
MCP Marketplace
Freeby mcp-marketplace · Developer Tools
Search and install MCP servers from inside your AI client.
mcp-creator-python
Freeby mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.
by Lharries · Communication
Read, search, and send WhatsApp messages through your AI assistant
FinAgent
Freeby mcp-marketplace · Finance
Free stock data and market news for any MCP-compatible AI assistant.
Memory
Freeby Modelcontextprotocol · Productivity
Knowledge graph-based persistent memory across sessions
