RailRoute journey planner MCP server
in.railroute/journey-plannerrailroute.instreamable-httpv1.3.0Scanned
Plan intercity journeys in India by train, flight or both, with a fare for every travel class.
8 tools: 3 do something that can't be undone, 3 change things and 2 only read.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 3
- 4 findings
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here do something that can't be undone. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the RailRoute journey planner MCP server can do
The RailRoute journey planner MCP server is published by railroute.in, a domain the MCP Registry verified. It has 8 tools. It can do things that cannot be undone, such as sending, paying or publishing (plan_journey, check_train_options and journey_calendar) and create or change data (3 tools: train_schedule, station_departures and nearby_stations), but cannot delete data. 2 tools only read.
2 tools bring in text other people can write (check_train_options and next_confirmed_date); 3 tools can send data out of your system (plan_journey, check_train_options and journey_calendar).
The fixed checks matched 4 findings (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 15, 2026, version 1.3.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
8 tools
Can't be undone 3Claude Code: ask
check_train_optionsLive seat availability per class for one train on one date, plus every other way to book it when the through ticket will not confirm: a split at an intermediate station, boarding e…Reads text others writeCan send data out1 finding
Why it is in this group
- The input addresses people (input.to): what it sends cannot be taken back.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Findings
- Warn
The server marks "check_train_options" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"idempotentHint":false,"openWorldHint":true}; The input addresses people (input.to): what it sends cannot be taken back.
Description, as the server wrote it Live seat availability per class for one train on one date, plus every other way to book it when the through ticket will not confirm: a split at an intermediate station, boarding earlier, alighting later. This is the tool that rescues a waitlisted train. It spends a metered upstream call, so ask it about trains the traveller is actually considering rather than sweeping a list.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: false
- openWorldHint: true
journey_calendarDay-by-day service over a span of dates for a station pair: which days have a direct train and which have none, plus the weekly pattern.Can send data out1 finding
Why it is in this group
- The input addresses people (input.to): what it sends cannot be taken back.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Findings
- Warn
The server marks "journey_calendar" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The input addresses people (input.to): what it sends cannot be taken back.
Description, as the server wrote it Day-by-day service over a span of dates for a station pair: which days have a direct train and which have none, plus the weekly pattern. Use this when somebody is flexible about when they travel, or asks 'does it run on Sundays'. Timetable only — it says nothing about seats.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
plan_journeyEvery practical way to get from one place to another: direct trains with their fares per class, journeys with one change of train, flights, mixed train-and-flight itineraries, and …Can send data out1 finding
Why it is in this group
- The input addresses people (input.to): what it sends cannot be taken back.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Findings
- Warn
The server marks "plan_journey" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The input addresses people (input.to): what it sends cannot be taken back.
Description, as the server wrote it Every practical way to get from one place to another: direct trains with their fares per class, journeys with one change of train, flights, mixed train-and-flight itineraries, and GOVERNMENT BUSES from the state road transport corporations, priced from their own reservation systems. This is the whole answer in one call. Place ids come from find_place. Use it for bus questions too. On a large share of the corridors these corporations serve there is no through train at all — Mysuru to Mangaluru runs twenty-five buses a day and not one direct train — so a journey this tool answers with a bus is often the only through service that exists, not a second-best. Pass `train_class` when the traveller has named one ("3A", "sleeper") and every train is priced in it; leave it out and each train is priced in every class we have evidence it carries. Pass `modes: "trains_only"` when they have said train — do not ask them to choose otherwise, because the point of this planner is that they do not have to. Pass `arrive_by: true` when they named a time they must BE somewhere rather than a time they want to leave.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
Changes things 3Claude Code: ask
nearby_stationsOther railway stations within a radius of one station, nearest first.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Other railway stations within a radius of one station, nearest first. Useful when a place has no service of its own and the traveller needs to know what is reachable — the planner already does this internally, so reach for it only when somebody asks the question directly.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
station_departuresEvery train scheduled to call at a station, in departure order — the enquiry board, not a journey plan.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Every train scheduled to call at a station, in departure order — the enquiry board, not a journey plan. Use plan_journey when somebody wants to get somewhere; use this when they are asking what leaves from here. Scheduled times only.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
train_scheduleEvery stop of one train with its scheduled arrival and departure, in order.1 finding
Why it is in this group
- The name "train_schedule" says "schedule": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "train_schedule" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The name "train_schedule" says "schedule": a word for a change.
Description, as the server wrote it Every stop of one train with its scheduled arrival and departure, in order. Scheduled times only — this says nothing about where the train is today.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
Only reads 2Show 2 read-only tools
find_placeTurn what somebody typed into RailRoute place ids.No findings
Why it is in this group
- The name "find_place" says "find": a word for reading.
Description, as the server wrote it Turn what somebody typed into RailRoute place ids. ALWAYS call this before plan_journey. A place is a city with all of its stations and airports — Mumbai covers CSMT, LTT, Dadar, Bandra Terminus and the airport — so the planner can choose the right terminal rather than making the traveller do it. Typing a station code ("CSMT") finds the city and says which terminal matched.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
next_confirmed_dateSearch forward up to a month for the first date this route can actually be travelled with a confirmed berth — direct trains and one-change journeys together.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "search": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Search forward up to a month for the first date this route can actually be travelled with a confirmed berth — direct trains and one-change journeys together. Use it when a traveller is flexible about WHEN and the date they asked for is waitlisted. EXPENSIVE: it checks seats across dozens of trains and dates, so it is limited to a few calls an hour; for a single date use check_train_options instead.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: false
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out3
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:55 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 6
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://www.railroute.in/.well-known/oauth-protected-resource/api/mcp
- Authorization servers
- https://www.railroute.in/
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 6 tools that change things (3 irreversible, 3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://www.railroute.in/api/mcp: tools/list returned 8 tools to an anonymous client, including plan_journey (irreversible), check_train_options (irreversible), journey_calendar (irreversible), train_schedule (write), station_departures (write) and 1 more
Findings
Matches of fixed checks, with the text they matched.
- Warnplan_journey
The server marks "plan_journey" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The input addresses people (input.to): what it sends cannot be taken back.
The server marks "check_train_options" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"idempotentHint":false,"openWorldHint":true}; The input addresses people (input.to): what it sends cannot be taken back.
- Warntrain_schedule
The server marks "train_schedule" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The name "train_schedule" says "schedule": a word for a change.
- Warnjourney_calendar
The server marks "journey_calendar" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":false}; The input addresses people (input.to): what it sends cannot be taken back.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.3.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http journey-planner https://www.railroute.in/api/mcpclaude mcp add --transport http journey-planner https://www.railroute.in/api/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__journey-planner__find_place",
"mcp__journey-planner__next_confirmed_date"
],
"ask": [
"mcp__journey-planner__plan_journey",
"mcp__journey-planner__check_train_options",
"mcp__journey-planner__train_schedule",
"mcp__journey-planner__station_departures",
"mcp__journey-planner__journey_calendar",
"mcp__journey-planner__nearby_stations"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as journey-planner. Review it before you use it.
Capability tags behind 4 rules
- mcp__journey-planner__plan_journey outbound
- mcp__journey-planner__check_train_options untrusted-input, outbound
- mcp__journey-planner__journey_calendar outbound
- mcp__journey-planner__next_confirmed_date untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/in.railroute/journey-planner/verify?hash=719222d47961f2c18f83d5574528dbde216103633ffc8a7bf52512a1051c2c3e" | jq -e '.changed == false'Pinned hash 719222d47961, from Nov 15, 2026, 12:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/in.railroute/journey-planner/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/in.railroute/journey-planner)Source: MCP Registry. Synced Oct 21, 2026, 18:13 UTC.
RailRoute journey planner MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the RailRoute journey planner MCP server safe?
- No scan can promise that. What its definitions show: 8 tools, 6 of which can change, send or delete something, and 4 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the RailRoute journey planner MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the RailRoute journey planner MCP server do things that cannot be undone?
- Yes. 3 tools can send, pay, publish or merge: plan_journey, check_train_options and journey_calendar.
What tools does the RailRoute journey planner MCP server have?
- 8 tools: 3 irreversible, 3 write, 2 read. plan_journey, check_train_options, journey_calendar, train_schedule, station_departures, nearby_stations, find_place and next_confirmed_date.
Does the RailRoute journey planner MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the RailRoute journey planner MCP server send data to outside services?
- 3 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): plan_journey, check_train_options and journey_calendar.
Has the RailRoute journey planner MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 15, 2026.