Search / in.railroute/journey-planner
RailRoute journey planner
R0· no sign-inPlan intercity journeys in India by train, flight or both, with a fare for every travel class.
v1.3.0 · active · website · descriptor JSON · versions
Search / in.railroute/journey-planner
R0· no sign-inPlan intercity journeys in India by train, flight or both, with a fare for every travel class.
v1.3.0 · active · website · descriptor JSON · versions
{
"mcpServers": {
"journey-planner": {
"type": "http",
"url": "https://www.railroute.in/api/mcp"
}
}
}claude mcp add --transport http journey-planner https://www.railroute.in/api/mcp[mcp_servers.journey-planner]
url = "https://www.railroute.in/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"journey-planner": {
"type": "remote",
"url": "https://www.railroute.in/api/mcp",
"enabled": true
}
}
}{
"mcpServers": {
"journey-planner": {
"type": "http",
"url": "https://www.railroute.in/api/mcp"
}
},
"deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=journey-planner&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vd3d3LnJhaWxyb3V0ZS5pbi9hcGkvbWNwIn0%3D"
}{
"servers": {
"journey-planner": {
"type": "http",
"url": "https://www.railroute.in/api/mcp"
}
}
}{
"mcpServers": {
"journey-planner": {
"httpUrl": "https://www.railroute.in/api/mcp"
}
}
}extensions:
"journey-planner":
enabled: true
name: "journey-planner"
type: streamable_http
uri: "https://www.railroute.in/api/mcp"
timeout: 300
protocol.modernnewest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28protocol.statelessonly applies to 2026-07-28 serversprotocol.transportstreamable HTTPprotocol.list_ttlonly applies to 2026-07-28 serversauth.prm, auth.as_metadata, auth.cimdno remote uses OAuthauth.secret_in_urlno templated URLtools.descriptionsevery tool has a descriptiontools.description_length1 tools have descriptions over 1,024 characters, which crowds the contexttools.schemasevery tool has an object input schematools.annotations8 of 8 tools declare readOnlyHint or destructiveHinttools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: plan_journey (destructiveHint); check_train_options (destructiveHint); journey_calendar (destructiveHint); …tools.token_costabout 2,138 tokens to load every tooltools.api_dumptools are not a one-to-one API dumpstability.changesno tool changes in 30 daysstability.rug_pullno tool changed its meaning under the same namedeps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI packageNo tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.
Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.
+dns-namespace +website +reachable +uptime-100% ~updated-46d-ago -no-repository
Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.
| remote | auth | reachable | uptime 30d | p50 | protocol | last ok |
|---|---|---|---|---|---|---|
https://www.railroute.in/api/mcp streamable-http | none | yes | 100% | 570 ms | 2025-11-25 | 2026-10-19 |
check_train_optionsread-only | 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. |
find_placeread-only | 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. |
journey_calendarread-only | 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. |
nearby_stationsread-only | 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. |
next_confirmed_dateread-only | 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. |
plan_journeyread-only | 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. |
station_departuresread-only | 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. |
train_scheduleread-only | 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. |
Schemas: list_tools.
{
"name": "in.railroute/journey-planner",
"title": "RailRoute journey planner",
"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
"remotes": [
{
"url": "https://www.railroute.in/api/mcp",
"type": "streamable-http"
}
],
"version": "1.3.0",
"websiteUrl": "https://www.railroute.in/mcp",
"description": "Plan intercity journeys in India by train, flight or both, with a fare for every travel class."
}