io.github.vulnersCom/vulners-mcp
OCI · GHCR.IO/VULNERSCOM/VULNERS-MCP · 3 COMPONENTS
MCP server for the Vulners.com API
Available components
Last scanned (19 hours ago)
Scores higher than 51% of OCI 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 Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency32
- 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
- License check failed: no license is declared. See how to fix → Fail
- 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
- 67% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1564 tokens (~156/item across 10 items; 7 tools + 3 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 Management13
- Stability observed for 4 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 (29% 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
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.
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.
- 17 Oct 26 +2
- Stability: unverified → 0.10 ▲ functional
- 14 Oct 26 36
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 18 Oct 2026 · Analysed oci/ghcr.io/vulnerscom/vulners-mcp@1.15.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
audit_linux_packages ~305
Linux package audit (RPM/DEB) for a given distro + version. Analyze Linux package vulnerabilities against the Vulners database.
| Name | Type | Req | Description |
|---|---|---|---|
| include_candidates | – | – | Whether to include potential matches in results. If None, uses default behavior (typically false). |
| os | string | yes | Linux distribution identifier (e.g., ubuntu, debian, centos, rhel, fedora). Use get_supported_os() to see available options. |
| package | array | yes | Installed packages, each formatted EXACTLY as the target OS's own package manager lists them -- i.e. one line of the output produced by the command get_supported_os() returns for this OS. DEB-based d… |
| version | string | yes | Distribution version/release (e.g., 22.04, 12, 8, 40). Must match a supported version for the specified OS. |
No output schema declared.
No examples provided.
audit_software ~175
🔍 VERSION-SPECIFIC SOFTWARE AUDIT 🔍 Audit specific software versions for known vulnerabilities. Use this when you have exact software version information (e.g., Chrome 138.0.7204.184). NEVER use search_lucene for version-specific software audits.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | yes | Request body containing software list and audit parameters. Should include 'software' array with structured CPE objects (NOT CPE strings) and optional 'match' parameter ('partial' or 'full'). Each CP… |
No output schema declared.
No examples provided.
bulletin_by_id ~511
🚨 PRIMARY TOOL FOR KNOWN IDs 🚨 Fetch a bulletin by CVE or Vulners ID. Returns a COMPACT triage-card summary by default -- id, title, CVSS3, EPSS, CVE list, and a compact exploitation/AI signal -- NOT the full record. Pass fields=[...] to widen (e.g. add 'description', 'cvss', 'cvss2', 'affectedSoftware') or references=True for the linked-bulletin graph; requesting everything can be very large. Supports single ID or list of IDs. When list is provided, references are automatically set to False. NEVER use search_lucene for known IDs.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | – | – | Override the default COMPACT field projection to widen the response. Pass ['*'] to request every field Vulners has for the bulletin (can be very large for popular CVEs). Useful individual fields to a… |
| id | – | yes | Single CVE ID, Vulners ID, or bulletin ID to fetch, or a list of IDs. Supports CVE identifiers (CVE-2024-21762), vendor-specific IDs (RHSA-2024:1234), or Vulners internal IDs. When a list is provided… |
| references | boolean | – | Include the full reference graph (linked advisories, patches, related bulletins) for a SINGLE-ID lookup. Defaults to False: the compact default projection already covers the essentials (CVSS3, EPSS,… |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
get_supported_os ~28
List supported OS identifiers/versions for Linux package audit. Get available operating systems for vulnerability analysis.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
query_autocomplete ~75
Autocomplete helper for search inputs (vendors, products, CVEs, etc.). Get search suggestions from the Vulners database.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | yes | Request body containing autocomplete parameters. Should include 'query' field with partial search term (e.g., 'openssl', 'CVE-2024-', 'microsoft windows'). |
No output schema declared.
No examples provided.
search_cpe ~119
Find CPE strings by vendor+product (latest schema). Search for Common Platform Enumeration identifiers in the Vulners database.
| Name | Type | Req | Description |
|---|---|---|---|
| product | string | yes | Product name to search for (e.g., 'windows_10', 'chrome', 'http_server', 'java'). Case-insensitive. |
| size | – | – | Maximum number of CPE results to return. If None, uses server default. |
| vendor | string | yes | Vendor name to search for (e.g., 'microsoft', 'google', 'apache', 'oracle'). Case-insensitive. |
No output schema declared.
No examples provided.
search_lucene ~302
🔍 DISCOVERY TOOL FOR UNKNOWN VULNERABILITIES 🔍 Full-text search in Vulners Knowledge Base using Lucene syntax. Use ONLY when you don't have specific IDs or version information. NEVER use for known CVE/bulletin IDs - use bulletin_by_id instead. NEVER use for specific software versions (e.g., 'Chrome 138.0.7204.184') - use audit_software instead. 🚨 CRITICAL: For vendor/product searches, ALWAYS use cnaAffected.vendor and cnaAffected.product fields - the affectedSoftware field does NOT exist.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | – | – | Override the default curated per-hit field projection. Pass ['*'] for every field per hit (large responses). If omitted, a curated default is used: id, title, type, cvss, cvss3, epss, published, href… |
| query | string | yes | Lucene query string for searching vulnerabilities. Supports Boolean operators (AND, OR, NOT), field-specific queries, range searches, and wildcard matching. NEVER use for specific software versions -… |
| size | integer | – | Maximum number of results to return. Default is 20, hard-capped at 100 regardless of caller. |
| skip | integer | – | Number of results to skip for pagination. Default is 0. |
No output schema declared.
No examples provided.
How do I install the io.github.vulnersCom/vulners-mcp server?
io.github.vulnersCom/vulners-mcp runs locally as a container image, launched with docker run --rm -i -e VULNERS_API_KEY ghcr.io/vulnerscom/vulners-mcp:1.15.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/vulnerscom/vulners-mcp
claude mcp add vulnerscom-vulners-mcp -- docker run --rm -i -e VULNERS_API_KEY ghcr.io/vulnerscom/vulners-mcp:1.15.0
This image reads VULNERS_API_KEY. Set it in your client's env block for this server; docker run -e passes it through to the container.
What is the io.github.vulnersCom/vulners-mcp server?
io.github.vulnersCom/vulners-mcp is listed in the public MCP registry as io.github.vulnersCom/vulners-mcp. MCP server for the Vulners.com API. This page covers its container image (ghcr.io/vulnerscom/vulners-mcp).
Is the io.github.vulnersCom/vulners-mcp server safe to use?
io.github.vulnersCom/vulners-mcp scores 38 out of 100 on VerifyMCP. 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.vulnersCom/vulners-mcp server expose?
io.github.vulnersCom/vulners-mcp exposes 7 tools: bulletin_by_id, search_lucene, audit_software, get_supported_os, audit_linux_packages, and 2 more. Their descriptions and schemas cost roughly 1,515 tokens of context every time the server is loaded.
Is the io.github.vulnersCom/vulners-mcp server still maintained?
io.github.vulnersCom/vulners-mcp is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.