Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

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

+3 this week 77 Trust /100

Last scanned (11 hours ago)

Scores higher than 67% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Security

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security69
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • 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. See how to fix → View diagnostics → Partial
  • HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability82
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 299 tokens (~74/item across 4 items; 4 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
  • Stability observed for 14 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 +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.

  • 18 Nov 26 +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.

  • 16 Nov 26 +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.

  • 14 Nov 26 +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.

  • 12 Nov 26 +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.

  • 10 Nov 26 +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.

  • 8 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 7 Nov 26 70

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://ukdata.reliness.co.uk/mcp/dev-security

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=reliness.co.uk CN=WE1,O=Google Trust Services,C=US 4 Nov 2026 2 Feb 2027 ECDSA 256 ECDSA-SHA256 f1d4f4e9f24c919b0e13c306162294a4
SANs: reliness.co.uk, ukdata.reliness.co.uk, *.ukdata.reliness.co.uk
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of ukdata.reliness.co.uk. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
uk. DS published 43876 8 Verified
co.uk. DS published 11810 8 Verified
reliness.co.uk. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://ukdata.reliness.co.uk/mcp/dev-security Verified 200
http (plaintext) http://ukdata.reliness.co.uk/mcp/dev-security Served over HTTP 200
MCP tools · 4 exposed · ~299 tokens

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 →

Tool Tokens
crate_stats ~61

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)

NameTypeReqDescription
cratestring–string, required, Rust crate name, e.g. "serde"

No output schema declared.

No examples provided.

cve_lookup ~107

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)

NameTypeReqDescription
cve_idstring–string, required, the CVE identifier, e.g. "CVE-2021-44228"

No output schema declared.

No examples provided.

npm_stats ~64

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)

NameTypeReqDescription
packagestring–string, required, npm package name, e.g. "react"

No output schema declared.

No examples provided.

pypi_stats ~67

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)

NameTypeReqDescription
packagestring–string, required, PyPI package name, e.g. "requests"

No output schema declared.

No examples provided.

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.

remote · ukdata.reliness.co.uk

# add to Claude Code
claude mcp add --transport http uk-co-reliness-dev-security 'https://ukdata.reliness.co.uk/mcp/dev-security'
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.