NS Dutch Railways API: live departures, station search, journey planning, disruptions, fares.
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
get_departuresLive NS departures from a station: times, platforms, train types, disruptions. Station codes like UT (Utrecht), ASD (Amsterdam).Live NS departures from a station: times, platforms, train types, disruptions. Station codes like UT (Utrecht), ASD (Amsterdam).
No input schema was published for this tool.
search_stationsFind NS stations by name or code: UIC codes, coordinates, synonyms.Find NS stations by name or code: UIC codes, coordinates, synonyms.
No input schema was published for this tool.
plan_journeyNS door-to-door journey advice: transfers, platforms, fares, disruptions between stations.NS door-to-door journey advice: transfers, platforms, fares, disruptions between stations.
No input schema was published for this tool.
get_disruptionsCurrent NS disruptions and engineering works with affected routes and alternative advice.Current NS disruptions and engineering works with affected routes and alternative advice.
No input schema was published for this tool.
get_faresNS fares between two stations: single, return, discount options.NS fares between two stations: single, return, discount options.
No input schema was published for this tool.
station_network_censusCount the railway stations OpenStreetMap knows inside a bounding box, via the keyless Overpass API: how many are named, how many carry coordinates, the operator and network tags that dominate, and which station names appear.Count the railway stations OpenStreetMap knows inside a bounding box, via the keyless Overpass API: how many are named, how many carry coordinates, the operator and network tags that dominate, and which station names appear.
No input schema was published for this tool.
station_wikidata_profileLook a station up on Wikidata for what the rail API does not carry: the item and its description, coordinates, the date it opened, its platform count and how much data the item actually holds.Look a station up on Wikidata for what the rail API does not carry: the item and its description, coordinates, the date it opened, its platform count and how much data the item actually holds.
No input schema was published for this tool.
7 of 7 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
NS Dutch Railways API: live departures, station search, journey planning, disruptions, fares.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
The crawl stopped at the depth-4 limit. Anything below that level was never resolved.
The crawl stopped at the 60-package limit. The rest of the tree was never resolved.
36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)
54 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.
+42 more not listed. The counts by reason above cover all of them.
Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.