# UK Data: CVEs and package popularity (remote · ukdata.reliness.co.uk)

Software vulnerabilities (CVEs) from the US NVD and package downloads for npm, PyPI and crates

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

## Components

- remote · `ukdata.reliness.co.uk`: 77/100 (this document), [markdown](https://verifymcp.io/servers/uk-co-reliness-dev-security/mcp-dev-security.md), [page](https://verifymcp.io/servers/uk-co-reliness-dev-security/mcp-dev-security)

## Channel facts

- Endpoint: `https://ukdata.reliness.co.uk/mcp/dev-security`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.5.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-21.

- **Endpoint Security**: 69/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 82/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 299 tokens (~74/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 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.
- **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 4 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 UK Data: CVEs and package popularity MCP server?

UK Data: CVEs and package popularity is a hosted endpoint at https://ukdata.reliness.co.uk/mcp/dev-security, 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 uk-co-reliness-dev-security 'https://ukdata.reliness.co.uk/mcp/dev-security'
```

### Cursor

```json
{
  "mcpServers": {
    "uk-co-reliness-dev-security": {
      "url": "https://ukdata.reliness.co.uk/mcp/dev-security"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "uk-co-reliness-dev-security": {
      "type": "http",
      "url": "https://ukdata.reliness.co.uk/mcp/dev-security"
    }
  }
}
```

### Codex

```toml
[mcp_servers.uk-co-reliness-dev-security]
url = "https://ukdata.reliness.co.uk/mcp/dev-security"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "uk-co-reliness-dev-security": {
      "type": "remote",
      "url": "https://ukdata.reliness.co.uk/mcp/dev-security",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add uk-co-reliness-dev-security --url 'https://ukdata.reliness.co.uk/mcp/dev-security' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  uk-co-reliness-dev-security:
    url: "https://ukdata.reliness.co.uk/mcp/dev-security"
```

### Netclaw

```json
{
  "McpServers": {
    "uk-co-reliness-dev-security": {
      "Transport": "http",
      "Url": "https://ukdata.reliness.co.uk/mcp/dev-security"
    }
  }
}
```

### Vellum

```bash
assistant mcp add uk-co-reliness-dev-security -t streamable-http -u 'https://ukdata.reliness.co.uk/mcp/dev-security'
```

### Other

```json
{
  "mcpServers": {
    "uk-co-reliness-dev-security": {
      "type": "http",
      "url": "https://ukdata.reliness.co.uk/mcp/dev-security"
    }
  }
}
```

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-21 (score 77, +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-11-18 (score 76, +1)

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

### 2026-11-16 (score 75, +1)

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

### 2026-11-14 (score 74, +1)

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

### 2026-11-12 (score 73, +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.

### 2026-11-10 (score 72, +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-11-08 (score 71, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-07 (score 70)

First indexed and scored.

## MCP tools (4)

### `cve_lookup` (~107 tokens)

Details of one specific CVE by its ID (e.g., CVE-2021-44228). Returns the vulnerability description, CVSS score, severity, published/modified dates, weakness type (CWE), and reference links for fixes or advisories from the NIST National Vulnerability Database. (cost: 1 credit)

Input parameters:

- `cve_id` (string): string, required, the CVE identifier, e.g. "CVE-2021-44228"

### `npm_stats` (~64 tokens)

Get download statistics for a JavaScript package on the npm registry. Returns the total download count for the last week to gauge popularity and usage trends. (cost: 1 credit)

Input parameters:

- `package` (string): string, required, npm package name, e.g. "react"

### `pypi_stats` (~67 tokens)

Get download statistics for a Python package from PyPI. Returns recent download counts for the last day, week, and month to measure library adoption. (cost: 1 credit)

Input parameters:

- `package` (string): string, required, PyPI package name, e.g. "requests"

### `crate_stats` (~61 tokens)

Get download statistics and metadata for a Rust crate from crates.io. Returns total and recent download counts along with the latest version number. (cost: 1 credit)

Input parameters:

- `crate` (string): string, required, Rust crate name, e.g. "serde"

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/uk-co-reliness-dev-security/mcp-dev-security#diagnostics

## Score history

- 2026-11-21: 77
- 2026-11-20: 76
- 2026-11-19: 76
- 2026-11-18: 76
- 2026-11-17: 75
- 2026-11-16: 75
- 2026-11-15: 74
- 2026-11-14: 74
- 2026-11-13: 73
- 2026-11-12: 73
- 2026-11-11: 72
- 2026-11-10: 72
- 2026-11-09: 71
- 2026-11-08: 71
- 2026-11-07: 70

## Common questions

### What is the UK Data: CVEs and package popularity MCP server?

UK Data: CVEs and package popularity is an MCP server listed in the public MCP registry as uk.co.reliness/dev-security. Software vulnerabilities (CVEs) from the US NVD and package downloads for npm, PyPI and crates. This page covers its hosted endpoint (https://ukdata.reliness.co.uk/mcp/dev-security).

### Is the UK Data: CVEs and package popularity MCP server safe to use?

UK Data: CVEs and package popularity scores 77 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 UK Data: CVEs and package popularity MCP server expose?

UK Data: CVEs and package popularity exposes 4 tools: cve_lookup, npm_stats, pypi_stats, crate_stats. Their descriptions and schemas cost roughly 299 tokens of context every time the server is loaded.

### Does the UK Data: CVEs and package popularity MCP server require authentication?

No. We connected to UK Data: CVEs and package popularity without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the UK Data: CVEs and package popularity MCP server still maintained?

UK Data: CVEs and package popularity is still listed as active in the MCP registry. We last reached this channel on 21 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 UK Data: CVEs and package popularity MCP server?

VerifyMCP ran 13 checks on UK Data: CVEs and package popularity, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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://ukdata.reliness.co.uk/mcp/dev-security
- Website: https://ukdata.reliness.co.uk/
- Changelog RSS feed: https://verifymcp.io/servers/uk-co-reliness-dev-security/mcp-dev-security.xml
- Changelog JSON feed: https://verifymcp.io/servers/uk-co-reliness-dev-security/mcp-dev-security/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/uk-co-reliness-dev-security/mcp-dev-security.json
- HTML version of this page: https://verifymcp.io/servers/uk-co-reliness-dev-security/mcp-dev-security
