Nve Mcp

io.github.3121nPublished by GitHub account 3121nv0.1.2Updated Oct 24, 2026

Norwegian flood & landslide hazard data from NVE, by WGS84 coordinate.

VerifiedSTDIODesktop onlyLocation & LifestyleData & Analytics

Overview

AI-generated overview

Local MCP server that looks up Norwegian flood and landslide hazard data from NVE's open map services by WGS84 coordinate.

What you can do
Look up flood susceptibility at a coordinate, including coverage checks and the detailed 200-year flood zone where mapped, with a TEK17 reference. Look up landslide susceptibility at a coordinate: snow and rock slides, soil and debris slides, and quick-clay hazard zones, each with a mapped-area check. Decode landslide type codes from both NVE and NGU code sets. Return a source link, thematic map view and licence with each data point, and state explicitly that susceptibility is not the same as a hazard zone.
When to use it
Useful when an assistant needs to check flood or landslide susceptibility for a specific address or coordinate in Norway, for example in property, planning or due-diligence questions, and when it matters whether an area is unmapped rather than safe.
Requirements
Runs as a local stdio process installed from the npm package @nor-data/nve-mcp; the README shows installing, building and starting it with Node.js. Network access to NVE's ArcGIS REST map services is needed. No accounts, API keys or environment variables are declared.
Before you install
Results are point lookups against open NVE/NGU data and are informational only; the README stresses that susceptibility is not a hazard zone and that no hit outside a mapped area means unmapped, not safe. Verify against official sources before relying on it for safety or regulatory decisions.

Installation

In SourceWeft

  1. Open Nve Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

@nor-data/nve-mcp

MCP-server som wrapper NVE sine åpne kartdata (kart.nve.no/enterprise ArcGIS REST) for punktoppslag på naturfare. Bygget for Konsept 12 («Hva gjør naboene?») — feltene flood_risk og landslide_risk i 12-feltmatrisen.

Verktøy

hent_flomaktsomhet(lat, lon)

  • Flom-aktsomhetsområde (landsdekkende GIS-analyse, Flomaktsomhet/1)
  • Dekningssjekk (Flomaktsomhet/2) — skiller «ingen treff» fra «ikke analysert»
  • Detaljert 200-årsflomsone (Flomsoner2/17) + analysert-område-sjekk (Flomsoner2/0) der detaljert flomsonekart finnes (TEK17 §7-2-referanse)

hent_skredaktsomhet(lat, lon)

  • Snø-/steinskred aktsomhet (SkredSnoSteinAkt/0) + kartlagt-sjekk (lag 1)
  • Jord-/flomskred aktsomhet (JordFlomskredAktsomhet/1 — lag 0 er raster, ikke spørrbart)
  • Kvikkleire faregradssoner (SkredKvikkleire2/0) + kartlagt-sjekk (lag 2)
  • Skredtype-koder dekodes (begge NVE/NGU-domener: korte koder 1–99 og fulle koder 110–200)

Designprinsipper (fra Konsept 12-syntesen)

  • Brukeren er tolkeren: output forklarer eksplisitt at aktsomhet ≠ faresone
  • Synlig usikkerhet: dekningslag rapporteres alltid — «ingen treff» utenfor kartlagt område betyr «ikke kartlagt», ikke «trygt»
  • Kildelenke per datapunkt: hver respons inkluderer tjeneste-URL + temakart-innsyn + lisens

Verifisert (5. juni 2026)

TestpunktForventetResultat
Lillestrøm (59.956, 11.046)flom-treff✅ FlomAktsomhetOmr + utenfor 200-årssone (detaljkart finnes)
Thorvald Meyers gate 2C, Oslorent✅ ingen treff, innenfor analysert område
Ytterholtet 1, Sørreisasnø/stein-treff✅ PotensieltSkredfareOmr («Snø og steinskred»)
Gjerdrum (60.063, 11.036)kvikkleire-treff✅ UtlosningOmr

Bruk

bash
npm install && npm run buildnode dist/index.js   # stdio MCPnode test-e2e.mjs    # ende-til-ende-test

Registrert i ~/.claude.json som nve. Lisens: MIT. Data: NVE/NGU åpne data (NLOD/CC BY).

Source: README.md at commit 22bf419

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.2LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.