# io.github.vulnersCom/vulners-mcp (remote · mcp.vulners.com)

MCP server for the Vulners.com API

- Trust score: 68/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- remote · `mcp.vulners.com`: 68/100 (this document), [markdown](https://verifymcp.io/servers/vulnerscom-vulners-mcp/mcp.md), [page](https://verifymcp.io/servers/vulnerscom-vulners-mcp/mcp)
- oci · `ghcr.io/vulnerscom/vulners-mcp`: 38/100, [markdown](https://verifymcp.io/servers/vulnerscom-vulners-mcp/ghcr-io-vulnerscom-vulners-mcp.md), [page](https://verifymcp.io/servers/vulnerscom-vulners-mcp/ghcr-io-vulnerscom-vulners-mcp)
- pypi · `vulners-mcp`: 0/100, [markdown](https://verifymcp.io/servers/vulnerscom-vulners-mcp/vulners-mcp.md), [page](https://verifymcp.io/servers/vulnerscom-vulners-mcp/vulners-mcp)

## Channel facts

- Endpoint: `https://mcp.vulners.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.15.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-18.

- **Endpoint Security**: 66/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 66/100
  - 67% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (29% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.vulnersCom/vulners-mcp server?

io.github.vulnersCom/vulners-mcp is a hosted endpoint at https://mcp.vulners.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http vulnerscom-vulners-mcp 'https://mcp.vulners.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "vulnerscom-vulners-mcp": {
      "url": "https://mcp.vulners.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "vulnerscom-vulners-mcp": {
      "type": "http",
      "url": "https://mcp.vulners.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.vulnerscom-vulners-mcp]
url = "https://mcp.vulners.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "vulnerscom-vulners-mcp": {
      "type": "remote",
      "url": "https://mcp.vulners.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add vulnerscom-vulners-mcp --url 'https://mcp.vulners.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  vulnerscom-vulners-mcp:
    url: "https://mcp.vulners.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "vulnerscom-vulners-mcp": {
      "Transport": "http",
      "Url": "https://mcp.vulners.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add vulnerscom-vulners-mcp -t streamable-http -u 'https://mcp.vulners.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "vulnerscom-vulners-mcp": {
      "type": "http",
      "url": "https://mcp.vulners.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-17 (score 68, +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.

### 2026-10-15 (score 67, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-14 (score 66)

First indexed and scored.

## MCP tools (7)

### `bulletin_by_id` (~511 tokens)

🚨 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.

Input parameters:

- `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` (required): 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,…

Output parameters:

- `result`

### `search_lucene` (~302 tokens)

🔍 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.

Input parameters:

- `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, required): 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.

### `audit_software` (~175 tokens)

🔍 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.

Input parameters:

- `body` (object, required): 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…

### `get_supported_os` (~28 tokens)

List supported OS identifiers/versions for Linux package audit. Get available operating systems for vulnerability analysis.

### `audit_linux_packages` (~305 tokens)

Linux package audit (RPM/DEB) for a given distro + version. Analyze Linux package vulnerabilities against the Vulners database.

Input parameters:

- `include_candidates`: Whether to include potential matches in results. If None, uses default behavior (typically false).
- `os` (string, required): Linux distribution identifier (e.g., ubuntu, debian, centos, rhel, fedora). Use get_supported_os() to see available options.
- `package` (array, required): 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, required): Distribution version/release (e.g., 22.04, 12, 8, 40). Must match a supported version for the specified OS.

### `query_autocomplete` (~75 tokens)

Autocomplete helper for search inputs (vendors, products, CVEs, etc.). Get search suggestions from the Vulners database.

Input parameters:

- `body` (object, required): Request body containing autocomplete parameters. Should include 'query' field with partial search term (e.g., 'openssl', 'CVE-2024-', 'microsoft windows').

### `search_cpe` (~119 tokens)

Find CPE strings by vendor+product (latest schema). Search for Common Platform Enumeration identifiers in the Vulners database.

Input parameters:

- `product` (string, required): 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, required): Vendor name to search for (e.g., 'microsoft', 'google', 'apache', 'oracle'). Case-insensitive.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/vulnerscom-vulners-mcp/mcp#diagnostics

## Score history

- 2026-10-18: 68
- 2026-10-17: 68
- 2026-10-16: 67
- 2026-10-15: 67
- 2026-10-14: 66

## Common questions

### 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 hosted endpoint (https://mcp.vulners.com/mcp).

### Is the io.github.vulnersCom/vulners-mcp server safe to use?

io.github.vulnersCom/vulners-mcp scores 68 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.

### Does the io.github.vulnersCom/vulners-mcp server require authentication?

No. We connected to io.github.vulnersCom/vulners-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### 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.

## Links

- Remote endpoint: https://mcp.vulners.com/mcp
- Repository: https://github.com/vulnersCom/vulners-mcp
- Changelog RSS feed: https://verifymcp.io/servers/vulnerscom-vulners-mcp/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/vulnerscom-vulners-mcp/mcp.json
- HTML version of this page: https://verifymcp.io/servers/vulnerscom-vulners-mcp/mcp