# com.vulnrable/vulnrable (remote · vulnrable.com)

Security grades for MCP servers and npm/PyPI packages, ranked by CISA KEV and EPSS.

- Trust score: 74/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `vulnrable.com`: 74/100 (this document), [markdown](https://verifymcp.io/servers/com-vulnrable-vulnrable/api-mcp.md), [page](https://verifymcp.io/servers/com-vulnrable-vulnrable/api-mcp)

## Channel facts

- Endpoint: `https://vulnrable.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-11-05.

- **Endpoint Security**: 57/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 4 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.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 392 tokens (~98/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 93/100
  - Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 83/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 50% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the com.vulnrable/vulnrable MCP server?

com.vulnrable/vulnrable is a hosted endpoint at https://vulnrable.com/api/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 com-vulnrable-vulnrable 'https://vulnrable.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-vulnrable-vulnrable": {
      "url": "https://vulnrable.com/api/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.com-vulnrable-vulnrable]
url = "https://vulnrable.com/api/mcp"
```

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  com-vulnrable-vulnrable:
    url: "https://vulnrable.com/api/mcp"
```

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "com-vulnrable-vulnrable": {
      "type": "http",
      "url": "https://vulnrable.com/api/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-11-04 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-24 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-22 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

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

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (4)

### `check_package` (~70 tokens)

Security assessment of one npm or PyPI package: letter grade, findings, known vulnerabilities, deprecation status, and — for MCP servers in our directory — the real resolved dependency count. Use before recommending or installing a package.

Input parameters:

- `ecosystem` (string, required)
- `name` (string, required): Exact package name

### `list_mcp_servers` (~90 tokens)

The MCP server directory with real resolved dependency counts. Use when recommending an MCP server, or to compare how much third-party code candidates pull into the agent. For a graded security assessment of one server, call check_package.

Input parameters:

- `sort_by` (string): total_packages sorts heaviest first
- `understates_only` (boolean): Only servers whose count understates real surface (mostly prebuilt binaries)

### `check_cve` (~73 tokens)

Details for one CVE or GHSA identifier, including whether CISA lists it as actively exploited (KEV) and its EPSS exploitation probability. Use to judge real-world urgency.

Input parameters:

- `id` (string, required): e.g. CVE-2024-3094 or GHSA-xxxx-xxxx-xxxx

### `latest_vulns` (~62 tokens)

Recently published vulnerabilities from the tracked pool, ranked KEV-first then by EPSS. Use for "what should I worry about this week".

Input parameters:

- `kev_only` (boolean)
- `limit` (integer)
- `min_severity` (string)

## Diagnostics

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

## Score history

- 2026-11-05: 74
- 2026-11-04: 74
- 2026-11-03: 73
- 2026-11-02: 73
- 2026-11-01: 72
- 2026-10-31: 72
- 2026-10-30: 71
- 2026-10-29: 71
- 2026-10-28: 71
- 2026-10-27: 70
- 2026-10-26: 70
- 2026-10-25: 69
- 2026-10-24: 69
- 2026-10-23: 68
- 2026-10-22: 68
- 2026-10-21: 67
- 2026-10-20: 67
- 2026-10-19: 66
- 2026-10-18: 66
- 2026-10-17: 65
- 2026-10-16: 65
- 2026-10-15: 64
- 2026-10-14: 64
- 2026-10-13: 64
- 2026-10-12: 63
- 2026-10-10: 62
- 2026-10-08: 61

## Common questions

### What is the com.vulnrable/vulnrable MCP server?

com.vulnrable/vulnrable is an MCP server listed in the public MCP registry as com.vulnrable/vulnrable. Security grades for MCP servers and npm/PyPI packages, ranked by CISA KEV and EPSS. This page covers its hosted endpoint (https://vulnrable.com/api/mcp).

### Is the com.vulnrable/vulnrable MCP server safe to use?

com.vulnrable/vulnrable scores 74 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 com.vulnrable/vulnrable MCP server expose?

com.vulnrable/vulnrable exposes 4 tools: check_package, list_mcp_servers, check_cve, latest_vulns. Their descriptions and schemas cost roughly 295 tokens of context every time the server is loaded.

### Does the com.vulnrable/vulnrable MCP server require authentication?

No. We connected to com.vulnrable/vulnrable without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the com.vulnrable/vulnrable MCP server still maintained?

com.vulnrable/vulnrable is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the com.vulnrable/vulnrable MCP server?

VerifyMCP ran 12 checks on com.vulnrable/vulnrable, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about com.vulnrable/vulnrable: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://vulnrable.com/api/mcp
- Website: https://vulnrable.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-vulnrable-vulnrable/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-vulnrable-vulnrable/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-vulnrable-vulnrable/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-vulnrable-vulnrable/api-mcp