Faceabot Transit Norway (Vy, Entur)
Server Details
Norwegian trains, buses and ferries: live trips and departures (Entur). Free, no key.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 3 tools
Each tool targets a clearly distinct task: no_connections plans journeys between two places, no_find_station looks up stations by name, and no_station_departures lists departures from a single stop. There is no meaningful overlap, so an agent can easily select the right tool.
All names use snake_case with a consistent 'no_' country prefix, which is predictable. However, the suffixes mix noun and verb_noun patterns (connections, find_station, station_departures), a minor deviation from a uniform convention.
Three tools cover the core transit query workflows (station lookup, departures, point-to-point journeys) without redundancy. It is on the minimal side for a public transport domain but still well-scoped and not thin enough to be problematic.
The surface covers station search, real-time departures, and full journey planning, which are the main use cases. Minor gaps exist, such as service alerts, real-time vehicle positions, or ticket information, but agents can work around them for typical queries.
Available Tools
3 toolsno_connectionsNorwegian public transport journeys (trains, buses, ferries)ARead-onlyIdempotentInspect
Journeys between two places in Norway by train, bus, tram, metro or boat (Vy, SJ Nord, Go-Ahead, Ruter, Skyss…): times, platforms, transfers, live delays, cancellations. Use when: someone travels by public transport in Norway (e.g. Oslo to Bergen). Example: {"from":"Oslo S","to":"Bergen stasjon"}
Inputs: to (required), from (required), date, time, +2 more.
no_find_stationFind a Norwegian station or stopARead-onlyIdempotentInspect
Finds Norwegian stations and stops matching a word, with their ids. Use when: a place name is ambiguous or misspelled. Example: {"query":"Bergen"}
Inputs: query (required).
no_station_departuresNext departures from a Norwegian station or stopARead-onlyIdempotentInspect
Next departures from one Norwegian station or stop (train, bus, tram, metro, boat): time, line, destination, platform, live delay, cancellations. Use when: someone is at (or going to) a stop in Norway. Example: {"station":"Oslo S"}
Inputs: station (required), results.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Norwegian transport (Entur) and geodata (Kartverket): trips, departures, addresses, elevation.
Entur MCP — Norway public transport, nationwide, all modes (developer.entur.org)
Finnish trains (VR, Helsinki commuter): live direct trains and departures. Free, no key.
Swiss trains and public transport: live connections and departures. Official data, free, no key.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceProvides access to Norway's nationwide public transport data (all modes) via the Entur API, enabling queries about routes, stops, and departures through natural language.156 npmMIT
- AlicenseAqualityCmaintenanceEnables AI agents to search for stops and stations across all Norwegian public transport and to fetch real-time departure data — planned versus expected times, delays, platform, operator, and disruption messages — with no API key required. Covers bus, tram, metro, train, and ferry nationwide through Entur's open APIs, with filtering by line, destination, and future departure time.2MIT
- AlicenseAqualityCmaintenanceEnables AI agents to access Norwegian public transport and geospatial data, including trip planning, stop departures, address search, elevation, and administrative boundaries, via the Entur and Kartverket APIs.2147 npmMIT
- AlicenseAqualityDmaintenanceProvides Estonian public transport timetables, trip planning, stop search, and real-time vehicle tracking.81MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.