Skip to main content
Glama
3121n

@nor-data/nabolag-mcp

by 3121n
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to @nor-data/nabolag-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

    • @nor-data/udir-mcp

      3121n
      A
      license
      A
      quality
      D
      maintenance
      MCP server that wraps UDIR's open registries for Norwegian schools (NSR) and kindergartens (NBR), enabling search by municipality and retrieval of full details including coordinates and enrollment.
      4
      57 npm
      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

    • datanorge

      tenki-labs
      A
      license
      A
      quality
      D
      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

    • nor-data/nve-mcp

      3121n
      A
      license
      A
      quality
      D
      maintenance
      MCP server that wraps NVE's open GIS data to provide flood risk and landslide risk point lookups, with explicit uncertainty reporting (e.g., 'no data' vs 'safe') and source references.
      2
      51 npm
      MIT
    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 3 tools

    Disambiguation5/5

    Each tool targets a distinct domain: green areas, public transport, and traffic noise. There is no functional overlap, and the descriptions clearly differentiate their purposes.

    Naming Consistency5/5

    All three tools follow a consistent 'hent_<topic>' pattern (Norwegian for 'get'), making the tool names predictable and easy to understand as a set.

    Tool Count5/5

    With 3 tools, the server is lean but well-scoped for its purpose of providing core neighborhood data. Each tool addresses an important aspect without unnecessary bloat.

    Completeness4/5

    The set covers three essential urban environment aspects (green space, transit, noise). While additional tools (e.g., schools, amenities) could improve completeness, the current surface is sensible and actionable for typical queries.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources