in.railroute/journey-planner

Est-ce que in.railroute/journey-planner est sûr ?

Au dernier audit MCP Hub, le serveur MCP « in.railroute/journey-planner » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 8 outils

• check_train_options≈ 332 tokens

  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.

  Paramètres, retour & exemple (6)

  Paramètres

  • to · string · requis
    Station code the traveller alights at
  • date · string · requis
  • from · string · requis
    Station code the traveller boards at
  • quota · string · optionnel · GN | TQ | PT | LD | SS
  • include_rac · boolean · optionnel
    RAC is a ticket that carries a right to board, so it counts as bookable by default.
  • train_number · string · requis

  Exemple d'appel

  {"name": "check_train_options", "arguments": {"to": "texte", "date": "texte", "from": "texte", "train_number": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• find_place≈ 212 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • limit · integer · optionnel
  • query · string · requis
    A city, station name or station code

  Exemple d'appel

  {"name": "find_place", "arguments": {"query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• journey_calendar≈ 244 tokens

  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.

  Paramètres, retour & exemple (4)

  Paramètres

  • to · string · requis
    Destination station code
  • days · integer · optionnel
  • from · string · requis
    Origin station code
  • start_date · string · requis
    First day of the span

  Exemple d'appel

  {"name": "journey_calendar", "arguments": {"to": "texte", "from": "texte", "start_date": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• nearby_stations≈ 200 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

  • limit · integer · optionnel
  • radius_km · integer · optionnel
  • station_code · string · requis

  Exemple d'appel

  {"name": "nearby_stations", "arguments": {"station_code": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• next_confirmed_date≈ 282 tokens

  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.

  Paramètres, retour & exemple (4)

  Paramètres

  • to · string · requis
    Destination station code
  • date · string · requis
    The date to search forward FROM
  • from · string · requis
    Origin station code
  • quota · string · optionnel · GN | TQ | PT | LD | SS

  Exemple d'appel

  {"name": "next_confirmed_date", "arguments": {"to": "texte", "date": "texte", "from": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• plan_journey≈ 829 tokens

  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.

  Paramètres, retour & exemple (10)

  Paramètres

  • to · string · requis
    Place id from find_place
  • date · string · requis
    Travel date in IST. Today is allowed; the past is refused.
  • from · string · requis
    Place id from find_place
  • limit · integer · optionnel
    How many of EACH kind to return. Raise it only if the traveller asks to see more.
  • modes · string · optionnel · any | trains_only | flights_only
    Restrict the answer. Default 'any' ranks trains, flights and government buses together — leave it out unless the traveller has actually named a mode. 'trains_only' and 'flights_only' both drop the buses.
  • quota · string · optionnel · GN | TQ | PT | LD | SS
  • arrive_by · boolean · optionnel
    When true, `date` is the day they must ARRIVE, and journeys may depart the day before.
  • train_class · string · optionnel · 2S | SL | CC | 3E | 3A | 2A | 1A | EC
    Price every train in this class: 2S Second Sitting, SL Sleeper, CC AC Chair Car, 3E AC 3 Economy, 3A AC 3 Tier, 2A AC 2 Tier, 1A First AC, EC Executive Chair Car. Omit to price each train in every class we know it carries.
  • ask_preferences · boolean · optionnel
    Whether to ask the traveller for a travel class when they have not named one. Set false for automated or bulk use.
  • include_connections · string · optionnel · auto | always | never
    Journeys with one change of train. 'auto' searches for them when direct trains are thin, which is when they matter; 'always' searches regardless and costs a few more seconds.

  Exemple d'appel

  {"name": "plan_journey", "arguments": {"to": "texte", "date": "texte", "from": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• station_departures≈ 214 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

  • after · string · optionnel
    Only departures at or after this IST clock time, HH:MM
  • limit · integer · optionnel
  • station_code · string · requis
    Station code, e.g. CNB

  Exemple d'appel

  {"name": "station_departures", "arguments": {"station_code": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• train_schedule≈ 126 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • train_number · string · requis

  Exemple d'appel

  {"name": "train_schedule", "arguments": {"train_number": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://www.railroute.in/api/mcp