Faceabot Rail Finland (VR)
Server Details
Finnish trains (VR, Helsinki commuter): live direct trains and departures. 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 distinct scope: finding stations, departures from a single station, and connections between two stations. There is mild overlap between fi_station_departures and fi_train_connections (both return times, tracks, delays, cancellations), but the one-station vs two-station distinction keeps them separable.
All names share a consistent 'fi_' prefix and snake_case formatting, which is good. However, the verb pattern is inconsistent: fi_find_station is verb_noun while fi_station_departures and fi_train_connections are noun phrases, breaking a uniform convention.
Three tools is on the lean side but reasonable for a focused Finnish rail lookup server. Each tool earns its place with a clear use case, though the surface is thin enough that it borders on minimal.
The set covers the main rail workflows: station lookup, station departures, and point-to-point connections. A notable gap is the explicit 'direct trains only' limitation (no transfer/multi-leg itineraries) and the lack of train-number/detail lookups, which could hinder some agent requests.
Available Tools
3 toolsfi_find_stationFind a Finnish stationARead-onlyIdempotentInspect
Finds Finnish passenger stations matching a word (Finnish or Swedish name), with their short codes. Use when: a station name is ambiguous or misspelled. Example: {"query":"Helsinki"}
Inputs: query (required).
fi_station_departuresNext trains from a Finnish stationARead-onlyIdempotentInspect
Next train departures from one Finnish station: time, train, destination, track, live delay, cancellations. Use when: someone is at (or going to) a station in Finland. Example: {"station":"Helsinki"}
Inputs: station (required), results.
fi_train_connectionsDirect Finnish trains between two stations (VR)ARead-onlyIdempotentInspect
Direct trains between two Finnish stations (VR long-distance and Helsinki commuter trains): departure and arrival times, tracks, live delays, cancellations. Direct trains only (no transfers). Use when: someone travels by train in Finland (e.g. Helsinki to Tampere). Example: {"from":"Helsinki","to":"Tampere"}
Inputs: to (required), from (required), date, time, +2 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Irish trains and DART: live direct trains in the next 90 minutes, departures. Free, no key.
Norwegian trains, buses and ferries: live trips and departures (Entur). Free, no key.
Swiss trains and public transport: live connections and departures. Official data, free, no key.
Belgian trains for AI agents: live journeys, departures, delays, disruptions. Free, no key.
Related MCP Servers
- AlicenseAqualityDmaintenanceProvides Estonian public transport timetables, trip planning, stop search, and real-time vehicle tracking.81MIT

mcp-db-railofficial
AlicenseNot gradedqualityBmaintenanceEnables keyless access to German and European rail and public transport data, including station search, live departures and arrivals, and multi-leg journey planning with real-time updates.116 npmMIT- AlicenseNot gradedqualityCmaintenanceProvides live vessel positions from Fintraffic's AIS receivers in Finnish and Baltic waters, with tools to query vessels near a point, count vessels in an area, and get details by MMSI. No authentication required.296 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables querying live departure and arrival boards, delays, platforms, cancellations, crowding, stop-by-stop progress, and journey planning with up to one change for Lombardy's regional rail network, using public open data without an API key.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.