io.github.trondbjoroy/norway-location-transport-mcp
REMOTE · NORWAY-LOCATION-TRANSPORT-MCP.MET-MCP-WORKER.WORKERS.DEV · 2 COMPONENTS · SCANNED SEP 21
Norwegian transport (Entur) and geodata (Kartverket): trips, departures, addresses, elevation.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 21 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 21 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the io.github.trondbjoroy/norway-location-transport-mcp server?
io.github.trondbjoroy/norway-location-transport-mcp is a hosted endpoint at https://norway-location-transport-mcp.met-mcp-worker.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · norway-location-transport-mcp.met-mcp-worker.workers.dev
claude mcp add --transport http trondbjoroy-norway-location-transport-mcp 'https://norway-location-transport-mcp.met-mcp-worker.workers.dev/mcp'
{
"mcpServers": {
"trondbjoroy-norway-location-transport-mcp": {
"url": "https://norway-location-transport-mcp.met-mcp-worker.workers.dev/mcp"
}
}
} {
"servers": {
"trondbjoroy-norway-location-transport-mcp": {
"type": "http",
"url": "https://norway-location-transport-mcp.met-mcp-worker.workers.dev/mcp"
}
}
} [mcp_servers.trondbjoroy-norway-location-transport-mcp] url = "https://norway-location-transport-mcp.met-mcp-worker.workers.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"trondbjoroy-norway-location-transport-mcp": {
"type": "remote",
"url": "https://norway-location-transport-mcp.met-mcp-worker.workers.dev/mcp",
"enabled": true
}
}
} openclaw mcp add trondbjoroy-norway-location-transport-mcp --url 'https://norway-location-transport-mcp.met-mcp-worker.workers.dev/mcp' --transport streamable-http
mcp_servers:
trondbjoroy-norway-location-transport-mcp:
url: "https://norway-location-transport-mcp.met-mcp-worker.workers.dev/mcp" {
"McpServers": {
"trondbjoroy-norway-location-transport-mcp": {
"Transport": "http",
"Url": "https://norway-location-transport-mcp.met-mcp-worker.workers.dev/mcp"
}
}
} assistant mcp add trondbjoroy-norway-location-transport-mcp -t streamable-http -u 'https://norway-location-transport-mcp.met-mcp-worker.workers.dev/mcp'
{
"mcpServers": {
"trondbjoroy-norway-location-transport-mcp": {
"type": "http",
"url": "https://norway-location-transport-mcp.met-mcp-worker.workers.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +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.
- 17 Sept 26 +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.
- 15 Sept 26 +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.
- 13 Sept 26 +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.
- 11 Sept 26 +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.
- 9 Sept 26 +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.
- 7 Sept 26 +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.
- 4 Sept 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Probed https://norway-location-transport-mcp.met-mcp-worker.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=met-mcp-worker.workers.dev | CN=WE1,O=Google Trust Services,C=US | 22 Aug 2026 | 20 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | ae2b9dbe6b89a9510ecaa2cd9041abb2 |
| SANs: met-mcp-worker.workers.dev, *.met-mcp-worker.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of norway-location-transport-mcp.met-mcp-worker.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://norway-location-transport-mcp.met-mcp-worker.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://norway-location-transport-mcp.met-mcp-worker.workers.dev/mcp | Inconclusive | 405 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
find_addresses_near Find addresses near a coordinate ~119
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?'.
| Name | Type | Req | Description |
|---|---|---|---|
| latitude | number | yes | Latitude in decimal degrees (WGS84). Norway spans about 57–72°N. |
| longitude | number | yes | 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 |
No output schema declared.
No examples provided.
find_docking_stations Find docking stations nearby ~100
Find shared-mobility docking stations (e.g. city bike stations) near a coordinate (Entur Mobility), with available vehicle and free-dock counts per station.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | Maximum number of stations to return |
| latitude | number | yes | Latitude in decimal degrees (WGS84) |
| longitude | number | yes | Longitude in decimal degrees (WGS84) |
| range_m | integer | – | Search radius in metres |
No output schema declared.
No examples provided.
find_place_names_near Find place names near a coordinate ~112
Find the nearest official named features to a coordinate (Kartverket). Each result includes its feature type and distance from the point.
| Name | Type | Req | Description |
|---|---|---|---|
| latitude | number | yes | Latitude in decimal degrees (WGS84). Norway spans about 57–72°N. |
| longitude | number | yes | 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 |
No output schema declared.
No examples provided.
find_shared_vehicles Find shared vehicles nearby ~147
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Latitude in decimal degrees (WGS84) |
| longitude | number | yes | Longitude in decimal degrees (WGS84) |
| range_m | integer | – | Search radius in metres |
No output schema declared.
No examples provided.
find_stops_near Find stop places near a coordinate ~99
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.
| Name | Type | Req | Description |
|---|---|---|---|
| latitude | number | yes | Latitude in decimal degrees (WGS84) |
| longitude | number | yes | Longitude in decimal degrees (WGS84) |
| max_results | integer | – | Maximum number of stops to return |
| radius_m | integer | – | Search radius in metres |
No output schema declared.
No examples provided.
get_departures Get next departures from a stop ~96
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.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | How many upcoming departures to return |
| stop_place_id | string | yes | Entur Stop Place ID, e.g. 'NSR:StopPlace:59872'. Get one from resolve_stop_place. |
No output schema declared.
No examples provided.
get_elevation Get elevation at a coordinate ~89
Get the terrain elevation (metres above sea level) at a coordinate from the Norwegian national elevation model (Kartverket DTM). Covers mainland Norway.
| Name | Type | Req | Description |
|---|---|---|---|
| latitude | number | yes | Latitude in decimal degrees (WGS84). Norway spans about 57–72°N. |
| longitude | number | yes | Longitude in decimal degrees (WGS84). Norway spans about 4–31°E. |
No output schema declared.
No examples provided.
get_elevation_profile Get an elevation profile along a path ~99
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.
| Name | Type | Req | Description |
|---|---|---|---|
| path | array | yes | 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 |
No output schema declared.
No examples provided.
get_fare_zones Get fare zones for a stop ~74
Get the fare (tariff) zone(s) a stop place belongs to (Entur). Fare zones set the ticket price for a journey.
| Name | Type | Req | Description |
|---|---|---|---|
| stop_place_id | string | yes | Entur Stop Place ID, e.g. 'NSR:StopPlace:59872'. Get one from resolve_stop_place. |
No output schema declared.
No examples provided.
get_realtime_status Get realtime status for a stop or line ~111
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
get_stop_accessibility Get stop accessibility ~108
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.
| Name | Type | Req | Description |
|---|---|---|---|
| stop_place_id | string | yes | Entur Stop Place ID, e.g. 'NSR:StopPlace:59872'. Get one from resolve_stop_place. |
No output schema declared.
No examples provided.
get_vehicle_positions Get live vehicle positions ~146
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
list_quays List quays (platforms) for a stop ~73
List all quays (platforms/stopping points) at a stop place (Entur), with their public codes, coordinates, and wheelchair access.
| Name | Type | Req | Description |
|---|---|---|---|
| stop_place_id | string | yes | Entur Stop Place ID, e.g. 'NSR:StopPlace:59872'. Get one from resolve_stop_place. |
No output schema declared.
No examples provided.
lookup_admin_unit Look up municipality and county ~112
Find which municipality (kommune) and county (fylke) a location falls in, with official codes (Kartverket). Give either a coordinate or a free-text address.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
lookup_property Look up property (matrikkel) info ~154
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
plan_trip Plan a public transport trip ~289
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
No output schema declared.
No examples provided.
resolve_stop_place Resolve a place to a Stop Place ID ~87
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.
| Name | Type | Req | Description |
|---|---|---|---|
| max_results | integer | – | Maximum number of stops to return |
| query | string | yes | Place or stop name, e.g. 'Oslo S' or 'Bergen busstasjon' |
No output schema declared.
No examples provided.
search_address Search Norwegian addresses ~189
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
search_place_names Search Norwegian place names ~104
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.
| Name | Type | Req | Description |
|---|---|---|---|
| max_results | integer | – | Maximum number of matches to return |
| query | string | yes | Place name to search for, e.g. 'Galdhøpiggen'. Supports the * wildcard. |
No output schema declared.
No examples provided.
transform_coordinates Transform coordinates between systems ~187
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).
| Name | Type | Req | Description |
|---|---|---|---|
| from_epsg | integer | yes | Source EPSG code, e.g. 4326 |
| to_epsg | integer | yes | Target EPSG code, e.g. 25833 |
| x | number | yes | Easting, or longitude for a geographic system (e.g. 4326/4258) |
| y | number | yes | Northing, or latitude for a geographic system |
No output schema declared.
No examples provided.
validate_address Validate and normalize an address ~75
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Address to validate, e.g. 'karl johans gt 1 oslo' |
No output schema declared.
No examples provided.
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 hosted endpoint (https://norway-location-transport-mcp.met-mcp-worker.workers.dev/mcp).
Is the io.github.trondbjoroy/norway-location-transport-mcp server safe to use?
io.github.trondbjoroy/norway-location-transport-mcp scores 73 out of 100 on VerifyMCP. 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.
Does the io.github.trondbjoroy/norway-location-transport-mcp server require authentication?
No. We connected to io.github.trondbjoroy/norway-location-transport-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
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.