Planning and disruption tools sitting together is the combination that matters on the day: get_travel_advice returns routes with real-time status and crowding, and get_disruptions says whether the line is being worked on at all. get_current_time_in_rfc3339 exists because the other tools want RFC3339 timestamps in the Europe/Amsterdam timezone, which removes the one thing an agent reliably gets wrong when planning a journey for later today.
An eight-tool client for Dutch railway travel information, covering journey planning, live station boards, disruptions, station facts and domestic pricing.
- Route options between two stations with transfers, platform information, duration, status and crowding, planned for now or for a given dateTime, optionally optimised for arrival
- Live departures and arrivals for a station with platform numbers, delays, origins or destinations and travel notes, bounded by maxJourneys and available in a chosen lang
- Current and planned disruptions including maintenance work, alternative transport, effect on travel time and the advice attached, filtered by type or to active ones only
- Fares for domestic journeys by travelClass and travelType, with adults, children and isJointJourney changing the answer
- OV-fiets availability at a station, station lookup by query, and get_current_time_in_rfc3339 for the timestamp the other tools expect
NS_API_KEY for the Dutch railway API, and station names or codes for the journey tools — a uicCode where a station has one. Pricing covers domestic journeys. MIT licensed.
One command plus a key — npx -y ns-mcp-server, then supply credentials