Skip to main content
Glama
3121n

nor-data/nve-mcp

by 3121n
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to nor-data/nve-mcp

No user-submitted related servers found.

    Related Servers

    • kartverket-mcp

      3121n
      A
      license
      A
      quality
      D
      maintenance
      MCP server that wraps Kartverket's open APIs for Norwegian geographic data including place names, addresses, elevation, municipalities, properties, statistical districts, and building points. Requires no authentication.
      7
      32
      MIT
    • floodwise by qinisolabs

      floodwiseofficial

      qinisolabs
      A
      license
      A
      quality
      B
      maintenance
      MCP server to look up long-term flood risk for England postcodes using official Environment Agency data, and validate UK postcodes.
      2
      31
      1
      Apache 2.0

    • fema-nfhl-mcp-server

      Graysonf12
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server that queries FEMA's National Flood Hazard Layer (NFHL) for flood zone information, including flood zone codes, Base Flood Elevation, FIRM panel numbers, and identifies LOMRs/LOMAs from provided coordinates, enabling automated flood risk lookups.
      -

    • datakilder-mcp

      smlhus1
      A
      license
      B
      quality
      A
      maintenance
      MCP server providing typed tools for Norwegian public data sources, enabling natural language queries to official datasets like SSB, Brønnøysund, MET, Kartverket, Entur, and more, without requiring API keys.
      47
      MIT
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    A4.2/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools address entirely different hazard types (flood vs landslide), with no overlap in their functionality. Clear distinction.

    Naming Consistency5/5

    Both tools follow the same 'hent_' + hazard type pattern, using snake_case and Norwegian, providing a predictable naming convention.

    Tool Count4/5

    With only 2 tools, the server is very narrow in scope. However, this may be appropriate for a focused hazard query service, though it feels slightly thin.

    Completeness3/5

    The server covers the two main hazard queries (flood and landslide) but lacks other potential hazard types (e.g., storm surge, wildfire) and has no data manipulation tools. Adequate for its stated purpose but not comprehensive.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources