
Nve Mcp
Check Norwegian flood and landslide hazard exposure at a coordinate while scoping sites, insurance tech, or climate-risk features.
Overview
NVE MCP is a MCP server for the Validate phase that retrieves Norwegian NVE flood and landslide hazard data for a WGS84 coordinate.
What is this MCP server?
- Flood and landslide hazard information from NVE using WGS84 coordinates
- Supports diligence for construction, insurance, and municipal climate workflows
- stdio MCP package @nor-data/nve-mcp at version 0.1.2
- GitHub repo 3121n/nor-data-nve-mcp for transparency
- Designed alongside other @nor-data Norway geodata MCP servers
- Server version 0.1.2
- npm package @nor-data/nve-mcp with stdio transport
- Repository: github.com/3121n/nor-data-nve-mcp
What problem does it solve?
Scoping Norwegian hazard-aware products without NVE data means agents guess at flood and landslide risk instead of citing authoritative layers.
Who is it for?
Indie builders validating Norway-focused climate, insurance, or real-estate workflows that need flood and landslide signals early.
Skip if: Products outside Norway or teams that need engineering-grade geotechnical models rather than register-based hazard indicators.
What do I get? / Deliverables
After registration, your agent can pull NVE peril context per coordinate while you define risk features and compliance copy.
- MCP tools surfacing NVE flood and landslide hazard responses
- Scope notes tying product features to available NVE peril attributes
- Registered server entry aligned with server.schema.json 2025-12-11 metadata
Recommended MCP Servers
Journey fit
Validate fits because hazard layers inform whether a Norway-specific risk product is feasible before you invest in Build pipelines. Scope captures early decisions on which NVE peril types to surface and which user journeys require authoritative hazard flags.
How it compares
NVE hazard data MCP integration, not a Ship-phase security scanner or generic web automation tool.
Common Questions / FAQ
Who is nve-mcp for?
Developers and founders building Norway-centric apps who want agents to access NVE flood and landslide hazard information by coordinates.
When should I use nve-mcp?
Use it during validation and scoping when you need to test whether NVE peril data supports your MVP, pricing, or user promises.
How do I add nve-mcp to my agent?
Configure @nor-data/nve-mcp as a stdio MCP server in your agent, install via npm, and restart so NVE hazard tools are exposed.