Skip to main content
Glama
hellosverre

kartverket-mcp

by hellosverre
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to kartverket-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
      38 npm
      MIT

    • datanorge

      tenki-labs
      A
      license
      A
      quality
      C
      maintenance
      An MCP server to find and fetch Norwegian open government data from data.norge.no. Enables search, metadata retrieval, and data download.
      5
      3
      MIT

    • 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

    • geocode-mcp

      danishashko
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for geocoding, reverse geocoding, place/POI search, and distance calculation using OpenStreetMap Nominatim, with no API key required.
      43 npm
      1
      MIT

    • chuk-mcp-geocoder

      IBM
      A
      license
      A
      quality
      C
      maintenance
      An MCP server providing geocoding and place discovery services via Nominatim and OpenStreetMap. It enables users to perform forward and reverse geocoding, extract bounding boxes, and find nearby places or administrative hierarchies.
      10
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a distinct purpose: forward and reverse geocoding for addresses, placename search, and elevation query. No overlap in functionality.

    Naming Consistency4/5

    Tools follow a clear pattern: coordinate-based queries use '<resource>_at_point' and text-based searches use 'search_<resource>'. While not all verb_noun, the pattern is predictable and consistent.

    Tool Count5/5

    With 4 tools, the set is well-scoped for a national geospatial server. Each tool covers a core function without unnecessary duplication.

    Completeness4/5

    Covers essential geospatial queries (address forward/reverse, placename search, elevation). Missing features like routing or structured geocoding, but core use cases are complete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources