services.gera/mcp-gera-indices
NPM · @GERA-SERVICES/MCP-GERA-INDICES · SCANNED SEP 24
Discover, resolve & cite Gera named UK NHS/OGL public-data indices with real source provenance.
Available components
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 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 79 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 658 tokens (~131/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 Management80
- Stability observed for 24 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 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
How do I install the services.gera/mcp-gera-indices server?
services.gera/mcp-gera-indices runs locally as an npm package, launched with npx -y @gera-services/mcp-gera-indices. 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-indices
claude mcp add services-gera-mcp-gera-indices -- npx -y @gera-services/mcp-gera-indices
{
"mcpServers": {
"services-gera-mcp-gera-indices": {
"command": "npx",
"args": [
"-y",
"@gera-services/mcp-gera-indices"
]
}
}
} {
"servers": {
"services-gera-mcp-gera-indices": {
"command": "npx",
"args": [
"-y",
"@gera-services/mcp-gera-indices"
]
}
}
} codex mcp add services-gera-mcp-gera-indices -- npx -y @gera-services/mcp-gera-indices
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"services-gera-mcp-gera-indices": {
"type": "local",
"command": [
"npx",
"-y",
"@gera-services/mcp-gera-indices"
],
"enabled": true
}
}
} openclaw mcp add services-gera-mcp-gera-indices --command npx --arg -y --arg @gera-services/mcp-gera-indices
mcp_servers:
services-gera-mcp-gera-indices:
command: "npx"
args: ["-y", "@gera-services/mcp-gera-indices"] {
"McpServers": {
"services-gera-mcp-gera-indices": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@gera-services/mcp-gera-indices"
]
}
}
} assistant mcp add services-gera-mcp-gera-indices -t stdio -c npx -a -y @gera-services/mcp-gera-indices
{
"mcpServers": {
"services-gera-mcp-gera-indices": {
"command": "npx",
"args": [
"-y",
"@gera-services/mcp-gera-indices"
]
}
}
} 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.
- 24 Sept 26 −3
- Stability: pass → 0.80 functional
- 23 Sept 26 0
- Stability: 0.97 → pass security
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +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.
- 18 Sept 26 +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.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
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 24 Sept 2026 · Analysed npm/@gera-services/mcp-gera-indices@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 →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
get_index Get one Gera index in full (with provenance + citation) ~134
Return everything about one named index: its full description, the real published standard the 0-100 score is scaled against, geographic coverage, the canonical page URL, the methodology URL, the underlying dataset’s full provenance (name, publisher, source URL, licence), the corridor-safe recruitment cross-links, related indices, and a ready-to-use cite_as string. Pass an index id from list_indices, or use resolve_index to turn a plain-language name into an id first.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Index id, e.g. "nhs-cancer-waiting-times-index" (from list_indices / resolve_index). |
No output schema declared.
No examples provided.
get_index_recruitment Get the recruitment / workforce cross-links for an index ~130
For a given index, return the corridor-safe recruitment context: why the index is a hiring-demand signal, the professions it points at, live Gera pathway-information page URLs, and example UK-inbound source countries. Every response carries the mandatory safeguard disclaimer (Gera does not actively recruit from WHO 2023 safeguard-list countries) and, where relevant, a profession-scope guard (e.g. registered nurses only for social care). This is pathway INFORMATION for individuals who independently choose to migrate — never active recruitment.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Index id (from list_indices / resolve_index). |
No output schema declared.
No examples provided.
list_index_sources List every index’s underlying data source + licence ~73
Return the provenance spine: for every named index, its name, the exact underlying dataset name, the publisher, the canonical source URL, the licence + licence URL, and a ready-to-use cite_as string. Use this to attribute or fact-check any Gera index against its real, named public source in one call.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_indices List Gera’s named public-data indices ~183
List the catalog of Gera named data indices — the editorial 0-100 scores Gera publishes over real, named UK open datasets (NHS England, NHSBSA, CQC, NHS Employers). For each: id (use it with get_index / get_index_recruitment), name, topic, status (live | planned), a one-line description, canonical page URL, the source publisher + URL, and licence. Use this first to discover what is available, then resolve_index for a plain-language name, get_index for one index in full. All underlying data is Open Government Licence v3.0 (or otherwise open) with attribution.
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | – | Optional status filter. Defaults to all. |
| topic | string | – | Optional topic filter, e.g. "cancer", "diagnostics", "workforce", "urgent-care". |
No output schema declared.
No examples provided.
resolve_index Resolve a plain-language name to a Gera index ~138
Turn a natural-language phrase — e.g. "the Gera NHS Cancer Waiting Times Index", "62-day cancer standard", "dental deserts", "ambulance response times" — into the best-matching named index(es), ranked. Returns each candidate’s id, name, match confidence, canonical URL and one-line description, so you can then call get_index for the winner. Use this when a user references an index by description rather than by its exact id.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max candidates to return (1-10). Defaults to 3. |
| query | string | yes | A plain-language index name or description to match. |
No output schema declared.
No examples provided.
What is the services.gera/mcp-gera-indices server?
services.gera/mcp-gera-indices is listed in the public MCP registry as services.gera/mcp-gera-indices. Discover, resolve & cite Gera named UK NHS/OGL public-data indices with real source provenance. This page covers its npm package (@gera-services/mcp-gera-indices).
Is the services.gera/mcp-gera-indices server safe to use?
services.gera/mcp-gera-indices scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 September 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-indices server expose?
services.gera/mcp-gera-indices exposes 5 tools: list_indices, get_index, resolve_index, get_index_recruitment, list_index_sources. Their descriptions and schemas cost roughly 658 tokens of context every time the server is loaded.
Is the services.gera/mcp-gera-indices server still maintained?
services.gera/mcp-gera-indices is still listed as active in the MCP registry. We last reached this channel on 24 September 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-indices server under?
services.gera/mcp-gera-indices declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.