# io.github.trondbjoroy/norway-location-transport-mcp (npm · norway-location-transport-mcp)

Norwegian transport (Entur) and geodata (Kartverket): trips, departures, addresses, elevation.

- Trust score: 83/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `norway-location-transport-mcp.met-mcp-worker.workers.dev`: 73/100, [markdown](https://verifymcp.io/servers/trondbjoroy-norway-location-transport-mcp/norway-location-transport-mcp-2.md), [page](https://verifymcp.io/servers/trondbjoroy-norway-location-transport-mcp/norway-location-transport-mcp-2)
- npm · `norway-location-transport-mcp`: 83/100 (this document), [markdown](https://verifymcp.io/servers/trondbjoroy-norway-location-transport-mcp/norway-location-transport-mcp.md), [page](https://verifymcp.io/servers/trondbjoroy-norway-location-transport-mcp/norway-location-transport-mcp)

## Channel facts

- Registry: `npm`
- Package: `norway-location-transport-mcp`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 96 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 27 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 78/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2570 tokens (~122/item across 21 items; 21 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 93/100
  - Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 21 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.trondbjoroy/norway-location-transport-mcp server?

io.github.trondbjoroy/norway-location-transport-mcp runs locally as an npm package, launched with npx -y norway-location-transport-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add trondbjoroy-norway-location-transport-mcp -- npx -y norway-location-transport-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "trondbjoroy-norway-location-transport-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "norway-location-transport-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "trondbjoroy-norway-location-transport-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "norway-location-transport-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add trondbjoroy-norway-location-transport-mcp -- npx -y norway-location-transport-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "trondbjoroy-norway-location-transport-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "norway-location-transport-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add trondbjoroy-norway-location-transport-mcp --command npx --arg -y --arg norway-location-transport-mcp
```

### Hermes

```yaml
mcp_servers:
  trondbjoroy-norway-location-transport-mcp:
    command: "npx"
    args: ["-y", "norway-location-transport-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "trondbjoroy-norway-location-transport-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "norway-location-transport-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add trondbjoroy-norway-location-transport-mcp -t stdio -c npx -a -y norway-location-transport-mcp
```

### Other

```json
{
  "mcpServers": {
    "trondbjoroy-norway-location-transport-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "norway-location-transport-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-19 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-07 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-04 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (21)

### `search_address` (~189 tokens)

Search Norwegian addresses

Search official Norwegian addresses (Kartverket) and get coordinates. Use `query` for free text, or the specific fields for a structured search. Wildcards with `*` are supported (e.g. street 'Storg*'). Returns coordinates, postal code, municipality, and cadastral numbers for each match.

Input parameters:

- `max_results` (integer): Maximum number of matches to return
- `municipality_number` (string): 4-digit municipality code (kommunenummer), e.g. '0301' for Oslo
- `number` (integer): House number (nummer)
- `postal_code` (string): Postal code (postnummer), e.g. '0155'
- `query` (string): Free-text address, e.g. 'Karl Johans gate 1, Oslo'. Supports the * wildcard.
- `street` (string): Street name (adressenavn). Supports the * wildcard.

### `find_addresses_near` (~119 tokens)

Find addresses near a coordinate

Find all official addresses within a radius of a coordinate (Kartverket). Each result includes its distance from the point. Good for 'what is at this location?'.

Input parameters:

- `latitude` (number, required): Latitude in decimal degrees (WGS84). Norway spans about 57–72°N.
- `longitude` (number, required): Longitude in decimal degrees (WGS84). Norway spans about 4–31°E.
- `max_results` (integer): Maximum number of addresses to return
- `radius_m` (integer): Search radius in metres

### `validate_address` (~75 tokens)

Validate and normalize an address

Check whether a free-text address exists in the official register and return its normalized form with coordinates. Uses fuzzy matching, so it also corrects small spelling errors. Returns `valid`, the best normalized match, and alternatives.

Input parameters:

- `address` (string, required): Address to validate, e.g. 'karl johans gt 1 oslo'

### `search_place_names` (~104 tokens)

Search Norwegian place names

Search official Norwegian place names (Kartverket Sentralt stedsnavnregister). Returns each name's feature type (e.g. Fjell, Innsjø, By), municipality, county, and coordinates. Supports the * wildcard and corrects small spelling errors.

Input parameters:

- `max_results` (integer): Maximum number of matches to return
- `query` (string, required): Place name to search for, e.g. 'Galdhøpiggen'. Supports the * wildcard.

### `find_place_names_near` (~112 tokens)

Find place names near a coordinate

Find the nearest official named features to a coordinate (Kartverket). Each result includes its feature type and distance from the point.

Input parameters:

- `latitude` (number, required): Latitude in decimal degrees (WGS84). Norway spans about 57–72°N.
- `longitude` (number, required): Longitude in decimal degrees (WGS84). Norway spans about 4–31°E.
- `max_results` (integer): Maximum number of features to return
- `radius_m` (integer): Search radius in metres

### `get_elevation` (~89 tokens)

Get elevation at a coordinate

Get the terrain elevation (metres above sea level) at a coordinate from the Norwegian national elevation model (Kartverket DTM). Covers mainland Norway.

Input parameters:

- `latitude` (number, required): Latitude in decimal degrees (WGS84). Norway spans about 57–72°N.
- `longitude` (number, required): Longitude in decimal degrees (WGS84). Norway spans about 4–31°E.

### `get_elevation_profile` (~99 tokens)

Get an elevation profile along a path

Sample the terrain elevation evenly along a path of coordinates (Kartverket DTM) and return the profile plus total distance, ascent, and descent. Useful for hikes and routes. Give the path vertices in order; `samples` controls resolution.

Input parameters:

- `path` (array, required): Ordered path vertices (at least 2). The path is sampled evenly between them.
- `samples` (integer): Number of evenly spaced points to sample along the whole path

### `transform_coordinates` (~187 tokens)

Transform coordinates between systems

Convert a coordinate between reference systems using Kartverket's transformer. Give EPSG codes for source and target. Axis order: x is easting (longitude for geographic systems), y is northing (latitude). Common EPSG codes: 4326 WGS84, 4258 EUREF89 (both lon/lat), 25832 UTM32/EUREF89, 25833 UTM33, 25835 UTM35 (east/north in metres).

Input parameters:

- `from_epsg` (integer, required): Source EPSG code, e.g. 4326
- `to_epsg` (integer, required): Target EPSG code, e.g. 25833
- `x` (number, required): Easting, or longitude for a geographic system (e.g. 4326/4258)
- `y` (number, required): Northing, or latitude for a geographic system

### `lookup_admin_unit` (~112 tokens)

Look up municipality and county

Find which municipality (kommune) and county (fylke) a location falls in, with official codes (Kartverket). Give either a coordinate or a free-text address.

Input parameters:

- `address` (string): Free-text address, used if no coordinate is given
- `latitude` (number): Latitude in decimal degrees (WGS84). Norway spans about 57–72°N.
- `longitude` (number): Longitude in decimal degrees (WGS84). Norway spans about 4–31°E.

### `lookup_property` (~154 tokens)

Look up property (matrikkel) info

Look up cadastral (matrikkel) identifiers for a property via the open address register (Kartverket): municipality number, gårdsnummer (gnr), bruksnummer (bnr), and festenummer. Give a free-text address or a coordinate. Full ownership data requires Kartverket's authenticated Matrikkel API; this returns the open address-linked identifiers.

Input parameters:

- `address` (string): Free-text address
- `latitude` (number): Latitude in decimal degrees (WGS84). Norway spans about 57–72°N.
- `longitude` (number): Longitude in decimal degrees (WGS84). Norway spans about 4–31°E.
- `max_results` (integer): Maximum number of properties to return

### `resolve_stop_place` (~87 tokens)

Resolve a place to a Stop Place ID

Turn a place or address into Entur Stop Place IDs (public transport stops/stations). Use the returned ID with the departure, trip, accessibility, quay, and fare-zone tools.

Input parameters:

- `max_results` (integer): Maximum number of stops to return
- `query` (string, required): Place or stop name, e.g. 'Oslo S' or 'Bergen busstasjon'

### `find_stops_near` (~99 tokens)

Find stop places near a coordinate

Reverse-geocode a coordinate to the nearest public transport stop places (Entur), each with its distance. Use the returned IDs with the departure and trip tools.

Input parameters:

- `latitude` (number, required): Latitude in decimal degrees (WGS84)
- `longitude` (number, required): Longitude in decimal degrees (WGS84)
- `max_results` (integer): Maximum number of stops to return
- `radius_m` (integer): Search radius in metres

### `plan_trip` (~289 tokens)

Plan a public transport trip

Plan a point-to-point public transport journey in Norway (Entur JourneyPlanner). Give each endpoint either as a Stop Place ID or as coordinates. Optionally set a departure or arrival time, filter transport modes, and set walk speed. Returns trip patterns with legs, modes, durations, and realtime times.

Input parameters:

- `arrive_by` (boolean): If true, date_time is the desired arrival time instead of departure time
- `date_time` (string): ISO 8601 time, e.g. '2026-08-24T09:00:00+02:00'. Defaults to now.
- `from_latitude` (number): Latitude in decimal degrees (WGS84)
- `from_longitude` (number): Longitude in decimal degrees (WGS84)
- `from_place` (string): Origin Stop Place ID (from resolve_stop_place)
- `num_trip_patterns` (integer): How many alternative trips to return
- `to_latitude` (number): Latitude in decimal degrees (WGS84)
- `to_longitude` (number): Longitude in decimal degrees (WGS84)
- `to_place` (string): Destination Stop Place ID
- `transport_modes` (array): Restrict to these transit modes, e.g. ['bus','tram']. Omit for all modes.
- `walk_speed` (number): Walking speed in metres per second (default ~1.3)

### `get_departures` (~96 tokens)

Get next departures from a stop

Get the next departures from a stop place (Entur), including realtime delays and cancellations. Each departure shows line, destination, scheduled and expected times, delay, platform, and whether it is cancelled.

Input parameters:

- `count` (integer): How many upcoming departures to return
- `stop_place_id` (string, required): Entur Stop Place ID, e.g. 'NSR:StopPlace:59872'. Get one from resolve_stop_place.

### `get_realtime_status` (~111 tokens)

Get realtime status for a stop or line

Get a realtime health summary. For a stop, pass stop_place_id: it summarizes how many upcoming departures are on time, delayed, or cancelled. For a line, pass line_id: it reports how many vehicles are currently active and their delays.

Input parameters:

- `line_id` (string): Line ID (e.g. 'ATB:Line:2_3', from get_departures) for a line-level summary
- `stop_place_id` (string): Stop Place ID for a stop-level summary

### `get_stop_accessibility` (~108 tokens)

Get stop accessibility

Get accessibility information for a stop place (Entur): per-quay (platform) wheelchair access, and a summary. Note: Entur's free API exposes wheelchair access per quay; deeper equipment detail (elevators, tactile guidance) is only in Entur's authenticated Stop Register API and is not available here.

Input parameters:

- `stop_place_id` (string, required): Entur Stop Place ID, e.g. 'NSR:StopPlace:59872'. Get one from resolve_stop_place.

### `list_quays` (~73 tokens)

List quays (platforms) for a stop

List all quays (platforms/stopping points) at a stop place (Entur), with their public codes, coordinates, and wheelchair access.

Input parameters:

- `stop_place_id` (string, required): Entur Stop Place ID, e.g. 'NSR:StopPlace:59872'. Get one from resolve_stop_place.

### `get_fare_zones` (~74 tokens)

Get fare zones for a stop

Get the fare (tariff) zone(s) a stop place belongs to (Entur). Fare zones set the ticket price for a journey.

Input parameters:

- `stop_place_id` (string, required): Entur Stop Place ID, e.g. 'NSR:StopPlace:59872'. Get one from resolve_stop_place.

### `find_shared_vehicles` (~147 tokens)

Find shared vehicles nearby

Find free-floating shared vehicles (city bikes, e-scooters, car share, mopeds) near a coordinate across all Norwegian operators (Entur Mobility). Each result shows the operator, type, battery, and location.

Input parameters:

- `count` (integer): Maximum number of vehicles to return
- `form_factors` (array): Filter by type. Common values: BICYCLE, SCOOTER, CAR, MOPED, CARGO_BICYCLE, OTHER.
- `latitude` (number, required): Latitude in decimal degrees (WGS84)
- `longitude` (number, required): Longitude in decimal degrees (WGS84)
- `range_m` (integer): Search radius in metres

### `find_docking_stations` (~100 tokens)

Find docking stations nearby

Find shared-mobility docking stations (e.g. city bike stations) near a coordinate (Entur Mobility), with available vehicle and free-dock counts per station.

Input parameters:

- `count` (integer): Maximum number of stations to return
- `latitude` (number, required): Latitude in decimal degrees (WGS84)
- `longitude` (number, required): Longitude in decimal degrees (WGS84)
- `range_m` (integer): Search radius in metres

### `get_vehicle_positions` (~146 tokens)

Get live vehicle positions

Get live positions of public transport vehicles (Entur realtime), filtered by operator codespace and/or line. Each vehicle shows its position, bearing, speed, and delay. Codespace examples: ATB (Trondheim), KOL (Stavanger), SKY (Bergen area). Get a line_id from get_departures.

Input parameters:

- `codespace_id` (string): Operator codespace, e.g. 'ATB'. Optional if line_id is given.
- `line_id` (string): Line ID, e.g. 'ATB:Line:2_3'. Optional if codespace_id is given.
- `max_results` (integer): Maximum number of vehicles to return

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/trondbjoroy-norway-location-transport-mcp/norway-location-transport-mcp#diagnostics

## Score history

- 2026-09-21: 83
- 2026-09-20: 83
- 2026-09-19: 83
- 2026-09-18: 82
- 2026-09-17: 82
- 2026-09-16: 81
- 2026-09-15: 81
- 2026-09-14: 80
- 2026-09-13: 80
- 2026-09-12: 79
- 2026-09-11: 79
- 2026-09-10: 78
- 2026-09-09: 78
- 2026-09-08: 77
- 2026-09-07: 77
- 2026-09-06: 76
- 2026-09-05: 76
- 2026-09-04: 76
- 2026-09-03: 75
- 2026-09-02: 75
- 2026-09-01: 74
- 2026-08-31: 74
- 2026-08-30: 70
- 2026-08-29: 70
- 2026-08-28: 70
- 2026-08-27: 70
- 2026-08-26: 70
- 2026-08-25: 69
- 2026-08-24: 69

## Common questions

### What is the io.github.trondbjoroy/norway-location-transport-mcp server?

io.github.trondbjoroy/norway-location-transport-mcp is listed in the public MCP registry as io.github.trondbjoroy/norway-location-transport-mcp. Norwegian transport (Entur) and geodata (Kartverket): trips, departures, addresses, elevation. This page covers its npm package (norway-location-transport-mcp).

### Is the io.github.trondbjoroy/norway-location-transport-mcp server safe to use?

io.github.trondbjoroy/norway-location-transport-mcp scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.github.trondbjoroy/norway-location-transport-mcp server expose?

io.github.trondbjoroy/norway-location-transport-mcp exposes 21 tools: search_address, find_addresses_near, validate_address, search_place_names, find_place_names_near, and 16 more. Their descriptions and schemas cost roughly 2,570 tokens of context every time the server is loaded.

### Is the io.github.trondbjoroy/norway-location-transport-mcp server still maintained?

io.github.trondbjoroy/norway-location-transport-mcp is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the io.github.trondbjoroy/norway-location-transport-mcp server under?

io.github.trondbjoroy/norway-location-transport-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/norway-location-transport-mcp
- Socket report: https://socket.dev/npm/package/norway-location-transport-mcp
- Repository: https://github.com/trondbjoroy/norway-location-transport-mcp
- Changelog RSS feed: https://verifymcp.io/servers/trondbjoroy-norway-location-transport-mcp/norway-location-transport-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/trondbjoroy-norway-location-transport-mcp/norway-location-transport-mcp.json
- HTML version of this page: https://verifymcp.io/servers/trondbjoroy-norway-location-transport-mcp/norway-location-transport-mcp