Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.trondbjoroy/norway-location-transport-mcp

REMOTE · NORWAY-LOCATION-TRANSPORT-MCP.MET-MCP-WORKER.WORKERS.DEV · 2 COMPONENTS

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

0 this week 74 Trust /100

Last scanned (18 hours ago)

Scores higher than 60% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Maps and Location

Trust breakdown (7 categories)

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
Transport & Reachability100
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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
What we tested

Checks we ran (11)

  • TLS certificate
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (2)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation 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.
  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 23 Sept 26 0
    • Stability: 0.97 → pass security
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: unverified → 0.03 ▲ functional
Diagnostics

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 Nov 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 20 Oct 2026 18 Jan 2027 ECDSA 256 ECDSA-SHA256 dbb4a8b2dadbb446135565516c9bfb63
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. DS published 60074 8 Verified
workers.dev. No DS 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
MCP tools · 21 exposed · ~2,570 tokens

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 →

Tool Tokens
find_addresses_near ~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?'.

NameTypeReqDescription
latitudenumberyesLatitude in decimal degrees (WGS84). Norway spans about 57–72°N.
longitudenumberyesLongitude in decimal degrees (WGS84). Norway spans about 4–31°E.
max_resultsinteger–Maximum number of addresses to return
radius_minteger–Search radius in metres

No output schema declared.

No examples provided.

find_docking_stations ~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.

NameTypeReqDescription
countinteger–Maximum number of stations to return
latitudenumberyesLatitude in decimal degrees (WGS84)
longitudenumberyesLongitude in decimal degrees (WGS84)
range_minteger–Search radius in metres

No output schema declared.

No examples provided.

find_place_names_near ~112

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

NameTypeReqDescription
latitudenumberyesLatitude in decimal degrees (WGS84). Norway spans about 57–72°N.
longitudenumberyesLongitude in decimal degrees (WGS84). Norway spans about 4–31°E.
max_resultsinteger–Maximum number of features to return
radius_minteger–Search radius in metres

No output schema declared.

No examples provided.

find_shared_vehicles ~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.

NameTypeReqDescription
countinteger–Maximum number of vehicles to return
form_factorsarray–Filter by type. Common values: BICYCLE, SCOOTER, CAR, MOPED, CARGO_BICYCLE, OTHER.
latitudenumberyesLatitude in decimal degrees (WGS84)
longitudenumberyesLongitude in decimal degrees (WGS84)
range_minteger–Search radius in metres

No output schema declared.

No examples provided.

find_stops_near ~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.

NameTypeReqDescription
latitudenumberyesLatitude in decimal degrees (WGS84)
longitudenumberyesLongitude in decimal degrees (WGS84)
max_resultsinteger–Maximum number of stops to return
radius_minteger–Search radius in metres

No output schema declared.

No examples provided.

get_departures ~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.

NameTypeReqDescription
countinteger–How many upcoming departures to return
stop_place_idstringyesEntur Stop Place ID, e.g. 'NSR:StopPlace:59872'. Get one from resolve_stop_place.

No output schema declared.

No examples provided.

get_elevation ~89

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

NameTypeReqDescription
latitudenumberyesLatitude in decimal degrees (WGS84). Norway spans about 57–72°N.
longitudenumberyesLongitude in decimal degrees (WGS84). Norway spans about 4–31°E.

No output schema declared.

No examples provided.

get_elevation_profile ~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.

NameTypeReqDescription
patharrayyesOrdered path vertices (at least 2). The path is sampled evenly between them.
samplesinteger–Number of evenly spaced points to sample along the whole path

No output schema declared.

No examples provided.

get_fare_zones ~74

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

NameTypeReqDescription
stop_place_idstringyesEntur Stop Place ID, e.g. 'NSR:StopPlace:59872'. Get one from resolve_stop_place.

No output schema declared.

No examples provided.

get_realtime_status ~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.

NameTypeReqDescription
line_idstring–Line ID (e.g. 'ATB:Line:2_3', from get_departures) for a line-level summary
stop_place_idstring–Stop Place ID for a stop-level summary

No output schema declared.

No examples provided.

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.

NameTypeReqDescription
stop_place_idstringyesEntur Stop Place ID, e.g. 'NSR:StopPlace:59872'. Get one from resolve_stop_place.

No output schema declared.

No examples provided.

get_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.

NameTypeReqDescription
codespace_idstring–Operator codespace, e.g. 'ATB'. Optional if line_id is given.
line_idstring–Line ID, e.g. 'ATB:Line:2_3'. Optional if codespace_id is given.
max_resultsinteger–Maximum number of vehicles to return

No output schema declared.

No examples provided.

list_quays ~73

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

NameTypeReqDescription
stop_place_idstringyesEntur Stop Place ID, e.g. 'NSR:StopPlace:59872'. Get one from resolve_stop_place.

No output schema declared.

No examples provided.

lookup_admin_unit ~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.

NameTypeReqDescription
addressstring–Free-text address, used if no coordinate is given
latitudenumber–Latitude in decimal degrees (WGS84). Norway spans about 57–72°N.
longitudenumber–Longitude in decimal degrees (WGS84). Norway spans about 4–31°E.

No output schema declared.

No examples provided.

lookup_property ~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.

NameTypeReqDescription
addressstring–Free-text address
latitudenumber–Latitude in decimal degrees (WGS84). Norway spans about 57–72°N.
longitudenumber–Longitude in decimal degrees (WGS84). Norway spans about 4–31°E.
max_resultsinteger–Maximum number of properties to return

No output schema declared.

No examples provided.

plan_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.

NameTypeReqDescription
arrive_byboolean–If true, date_time is the desired arrival time instead of departure time
date_timestring–ISO 8601 time, e.g. '2026-08-24T09:00:00+02:00'. Defaults to now.
from_latitudenumber–Latitude in decimal degrees (WGS84)
from_longitudenumber–Longitude in decimal degrees (WGS84)
from_placestring–Origin Stop Place ID (from resolve_stop_place)
num_trip_patternsinteger–How many alternative trips to return
to_latitudenumber–Latitude in decimal degrees (WGS84)
to_longitudenumber–Longitude in decimal degrees (WGS84)
to_placestring–Destination Stop Place ID
transport_modesarray–Restrict to these transit modes, e.g. ['bus','tram']. Omit for all modes.
walk_speednumber–Walking speed in metres per second (default ~1.3)

No output schema declared.

No examples provided.

resolve_stop_place ~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.

NameTypeReqDescription
max_resultsinteger–Maximum number of stops to return
querystringyesPlace or stop name, e.g. 'Oslo S' or 'Bergen busstasjon'

No output schema declared.

No examples provided.

search_address ~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.

NameTypeReqDescription
max_resultsinteger–Maximum number of matches to return
municipality_numberstring–4-digit municipality code (kommunenummer), e.g. '0301' for Oslo
numberinteger–House number (nummer)
postal_codestring–Postal code (postnummer), e.g. '0155'
querystring–Free-text address, e.g. 'Karl Johans gate 1, Oslo'. Supports the * wildcard.
streetstring–Street name (adressenavn). Supports the * wildcard.

No output schema declared.

No examples provided.

search_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.

NameTypeReqDescription
max_resultsinteger–Maximum number of matches to return
querystringyesPlace name to search for, e.g. 'Galdhøpiggen'. Supports the * wildcard.

No output schema declared.

No examples provided.

transform_coordinates ~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).

NameTypeReqDescription
from_epsgintegeryesSource EPSG code, e.g. 4326
to_epsgintegeryesTarget EPSG code, e.g. 25833
xnumberyesEasting, or longitude for a geographic system (e.g. 4326/4258)
ynumberyesNorthing, or latitude for a geographic system

No output schema declared.

No examples provided.

validate_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.

NameTypeReqDescription
addressstringyesAddress to validate, e.g. 'karl johans gt 1 oslo'

No output schema declared.

No examples provided.

Install

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

# add to Claude Code
claude mcp add --transport http trondbjoroy-norway-location-transport-mcp 'https://norway-location-transport-mcp.met-mcp-worker.workers.dev/mcp'
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 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 74 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 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the io.github.trondbjoroy/norway-location-transport-mcp server?

VerifyMCP ran 11 checks on io.github.trondbjoroy/norway-location-transport-mcp, covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about io.github.trondbjoroy/norway-location-transport-mcp: Authorization and HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.