protogrid

Search / in.railroute/journey-planner

RailRoute journey planner

R0· no sign-in

Plan intercity journeys in India by train, flight or both, with a fare for every travel class.

v1.3.0 · active · website · descriptor JSON · versions

An agent can connect right now, no human step.Remote endpoint, no authentication, reachable on the last probe.
Quality82good
Trust80of 100
Uptime, 30 days100%
Latency p50570 ms

Connect

8 clients · secrets stay placeholders
{
  "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

Quality 82 / 100good

protocol75 · weight 25
  • warn
    protocol.modernnewest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
  • n/a
    protocol.statelessonly applies to 2026-07-28 servers
  • pass
    protocol.transportstreamable HTTP
  • n/a
    protocol.list_ttlonly applies to 2026-07-28 servers
authorizationn/a · weight 15
  • n/a
    auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
  • n/a
    auth.secret_in_urlno templated URL
tool hygiene79 · weight 30
  • pass
    tools.descriptionsevery tool has a description
  • warn
    tools.description_length1 tools have descriptions over 1,024 characters, which crowds the context
  • pass
    tools.schemasevery tool has an object input schema
  • pass
    tools.annotations8 of 8 tools declare readOnlyHint or destructiveHint
  • fail
    tools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: plan_journey (destructiveHint); check_train_options (destructiveHint); journey_calendar (destructiveHint); …
  • pass
    tools.token_costabout 2,138 tokens to load every tool
  • pass
    tools.api_dumptools are not a one-to-one API dump
stability100 · weight 15
  • pass
    stability.changesno tool changes in 30 days
  • pass
    stability.rug_pullno tool changed its meaning under the same name
dependenciesn/a · weight 15
  • n/a
    deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

8 tools, about 2,138 tokens to load them all · tool set 66105cd9c05f · checked 2026-10-19 10:52 UTC

Tool changes

No 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.

Trust 80 / 100

no-repository
provenance55
liveness100
freshness85
hygiene80

+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.

Endpoints

remoteauthreachableuptime 30dp50protocollast ok
https://www.railroute.in/api/mcp streamable-httpnoneyes100%570 ms2025-11-252026-10-19

Tools (8)

check_train_optionsread-onlyLive 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-onlyTurn 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-onlyDay-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-onlyOther 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-onlySearch 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-onlyEvery 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-onlyEvery 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-onlyEvery 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.

Similar MCP servers

Official server.json
{
  "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."
}