io.github.3121n/nve-mcp
NPM · @NOR-DATA/NVE-MCP · SCANNED SEP 20
Norwegian flood & landslide hazard data from NVE, by WGS84 coordinate.
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 Security93
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known medium-severity CVE affects stream-json 1.9.1, reached via apify > @crawlee/core > stream-json. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 76 of 262 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- 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 104 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 326 tokens (~163/item across 2 items; 2 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 Management87
- Stability observed for 26 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 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 io.github.3121n/nve-mcp server?
io.github.3121n/nve-mcp runs locally as an npm package, launched with npx -y @nor-data/nve-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @nor-data/nve-mcp
claude mcp add 3121n-nve-mcp -- npx -y @nor-data/nve-mcp
{
"mcpServers": {
"3121n-nve-mcp": {
"command": "npx",
"args": [
"-y",
"@nor-data/nve-mcp"
]
}
}
} {
"servers": {
"3121n-nve-mcp": {
"command": "npx",
"args": [
"-y",
"@nor-data/nve-mcp"
]
}
}
} codex mcp add 3121n-nve-mcp -- npx -y @nor-data/nve-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"3121n-nve-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@nor-data/nve-mcp"
],
"enabled": true
}
}
} openclaw mcp add 3121n-nve-mcp --command npx --arg -y --arg @nor-data/nve-mcp
mcp_servers:
3121n-nve-mcp:
command: "npx"
args: ["-y", "@nor-data/nve-mcp"] {
"McpServers": {
"3121n-nve-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@nor-data/nve-mcp"
]
}
}
} assistant mcp add 3121n-nve-mcp -t stdio -c npx -a -y @nor-data/nve-mcp
{
"mcpServers": {
"3121n-nve-mcp": {
"command": "npx",
"args": [
"-y",
"@nor-data/nve-mcp"
]
}
}
} 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.
- 20 Sept 26 +1
- Security disclosure: fail → unverified ▼ functional
- 18 Sept 26 −2
- Stability: pass → 0.80 functional
- 17 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 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.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 −2
- Stability: pass → 0.80 functional
- 10 Sept 26 0
- Stability: 0.97 → pass security
- 8 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
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 20 Sept 2026 · Analysed npm/@nor-data/nve-mcp@0.1.2
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-528h-pc64-c93x | CVE-2026-71429 | medium | CVSS:3.1/AV:L/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 262 packages
| Packages resolved | 262 |
|---|---|
| Deprecated | 1 |
| Stale | 76 |
| 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 →
hent_flomaktsomhet ~162
Sjekk om et koordinat (WGS84) ligger i NVE sitt flom-aktsomhetsområde (landsdekkende GIS-analyse) og i detaljert kartlagt flomsone (200-årsflom) der slik finnes. Returnerer også om punktet er innenfor analysert/kartlagt område, slik at 'ingen treff' kan skilles fra 'ikke kartlagt'. Kilde: NVE (kart.nve.no), åpne data.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | Breddegrad (WGS84, f.eks. 59.93 for Oslo) |
| lon | number | yes | Lengdegrad (WGS84, f.eks. 10.76 for Oslo) |
No output schema declared.
No examples provided.
hent_skredaktsomhet ~164
Sjekk om et koordinat (WGS84) ligger i NVE sine skred-aktsomhetsområder: snø-/steinskred, jord-/flomskred og kvikkleire (faregradssoner). Returnerer treff per skredtype med dekodet skredtype og kartleggingsstatus, slik at 'ingen treff' kan skilles fra 'ikke kartlagt'. Kilde: NVE/NGU (kart.nve.no), åpne data.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | Breddegrad (WGS84, f.eks. 59.93 for Oslo) |
| lon | number | yes | Lengdegrad (WGS84, f.eks. 10.76 for Oslo) |
No output schema declared.
No examples provided.
What is the io.github.3121n/nve-mcp server?
io.github.3121n/nve-mcp is listed in the public MCP registry as io.github.3121n/nve-mcp. Norwegian flood & landslide hazard data from NVE, by WGS84 coordinate. This page covers its npm package (@nor-data/nve-mcp).
Is the io.github.3121n/nve-mcp server safe to use?
io.github.3121n/nve-mcp scores 82 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 20 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 io.github.3121n/nve-mcp server expose?
io.github.3121n/nve-mcp exposes 2 tools: hent_flomaktsomhet, hent_skredaktsomhet. Their descriptions and schemas cost roughly 326 tokens of context every time the server is loaded.
Is the io.github.3121n/nve-mcp server still maintained?
io.github.3121n/nve-mcp is still listed as active in the MCP registry. We last reached this channel on 20 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 io.github.3121n/nve-mcp server under?
io.github.3121n/nve-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.