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.

services.gera/mcp-gera-data

NPM · @GERA-SERVICES/MCP-GERA-DATA

Discover & query Gera's 30 attested open UK/US government datasets, each with signed provenance.

0 this week 74 Trust /100

Last scanned (18 hours ago)

Scores higher than 49% of npm servers

Category Data and Analytics

Trust breakdown (7 categories)

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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
  • Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 137 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability76
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 729 tokens (~145/item across 5 items; 5 tools + 0 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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 (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

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.

  • 19 Nov 26 +1
    • Stability: 0.97 → pass security
  • 18 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 12 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 +1

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

  • 8 Nov 26 −2
    • Stability: pass → 0.87 functional
  • 2 Nov 26 +1
    • Stability: 0.97 → pass security
  • 1 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 26 Oct 26 +1
    • Stability: 0.97 → pass security
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 · Analysed npm/@gera-services/mcp-gera-data@1.0.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 93 packages
Packages resolved 93
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~729 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
get_attestation ~151

Return the cryptographically signed Gera Vouch attestation for a dataset version: a claim object (dataset id, version, row count, SHA-256 content hash over the rows, source, source URL, licence, attribution, as-of, issuer), an Ed25519 signature, and the public key + verification recipe. Any party re-canonicalises the claim (sorted-key UTF-8 JSON) and verifies the signature against the public key — proving the dataset content came from the named source under the named licence and was not altered. This is a proof-of-provenance receipt; it is NOT a warranty of fitness for purpose.

NameTypeReqDescription
idstringyesDataset id (from list_datasets).

No output schema declared.

No examples provided.

get_dataset ~122

Return everything about one dataset EXCEPT its rows: title, description, coverage, full provenance (source, URL, licence, attribution, as-of, derivation notes), the complete column schema, the row count, and a compact attestation summary (content hash + key id) so you know it is signed. Pass a dataset id from list_datasets. Use query_dataset to fetch the rows, get_attestation for the full signed receipt.

NameTypeReqDescription
idstringyesDataset id, e.g. "uk-council-tax" (from list_datasets).

No output schema declared.

No examples provided.

get_vouch_public_key ~69

Return the Ed25519 public key (+ key_id and verification recipe) used to sign every Gera Vouch dataset attestation, so any party can independently verify a get_attestation receipt. This is the same Gera public key the Gera Data API and Gera Verify MCP publish.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_datasets ~135

List the catalog of verified open datasets Gera serves: for each, the id (use it with the other tools), title, source publisher, source URL, licence, reference period (as-of), row count, coverage, and the queryable columns (id, label, type, unit, whether filterable/sortable). Use this first to discover what data is available, then call get_dataset / query_dataset / get_attestation by id. All data is public-domain / OGL v3.0 / CC-BY with attribution.

NameTypeReqDescription
countrystring–Optional filter by country/coverage. Defaults to all.

No output schema declared.

No examples provided.

query_dataset ~252

Fetch verified rows from a dataset with optional single-column filter, sort, and pagination — same semantics as the Gera Data API. filter_column must be a filterable column; for number columns the filter is an exact match, for string columns a case-insensitive substring match. sort_by must be a sortable column. Returns the page of rows plus total/totalPages and the dataset version, so a returned value can be cited precisely (dataset id + version + source). Default page_size 50, max 500. For a full-dataset content hash, page through all rows or use get_attestation.

NameTypeReqDescription
filter_columnstring–Filterable column id to filter on. Omit for no filter.
filter_valuestring–Value to match (exact for number columns, substring for string columns).
idstringyesDataset id (from list_datasets).
pageinteger–1-based page number. Defaults to 1.
page_sizeinteger–Rows per page (1-500). Defaults to 50.
sort_bystring–Sortable column id to sort by.
sort_dirstring–Sort direction. Defaults to asc.

No output schema declared.

No examples provided.

Install

How do I install the services.gera/mcp-gera-data server?

services.gera/mcp-gera-data runs locally as an npm package, launched with npx -y @gera-services/mcp-gera-data. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @gera-services/mcp-gera-data

# add to Claude Code
claude mcp add services-gera-mcp-gera-data -- npx -y @gera-services/mcp-gera-data
Common questions

What is the services.gera/mcp-gera-data server?

services.gera/mcp-gera-data is listed in the public MCP registry as services.gera/mcp-gera-data. Discover & query Gera's 30 attested open UK/US government datasets, each with signed provenance. This page covers its npm package (@gera-services/mcp-gera-data).

Is the services.gera/mcp-gera-data server safe to use?

services.gera/mcp-gera-data scores 74 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 2026. It declares no install or post-install scripts. 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 services.gera/mcp-gera-data server expose?

services.gera/mcp-gera-data exposes 5 tools: list_datasets, get_dataset, query_dataset, get_attestation, get_vouch_public_key. Their descriptions and schemas cost roughly 729 tokens of context every time the server is loaded.

Is the services.gera/mcp-gera-data server still maintained?

services.gera/mcp-gera-data 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 licence is the services.gera/mcp-gera-data server under?

services.gera/mcp-gera-data declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the services.gera/mcp-gera-data server?

VerifyMCP ran 15 checks on services.gera/mcp-gera-data, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about services.gera/mcp-gera-data: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.