Your Travel Radar

Dated, sourced facts on European night train stations and lines, and measured punctuality.

Should I use this

Quality & Safety

A
Description quality
96%
Schema completeness
68%
Naming quality
91%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Findings (1)

  • LOWTool 'list_lines' description lacks action verbin list_lines

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~499Tokens (tool definitions)
~278 BTypical response size
Minimal attention impact (0.39% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "night-trains": {
      "url": "https://yourtravelradar.com/mcp"
    }
  }
}

Remote endpoints

https://yourtravelradar.com/mcpstreamable-http

What it can do

Tool inventory

Tools (7)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢search_stations(query, country)

Find night train stations by name and/or ISO country code. Returns id, name, country, coordinates and the night train lines calling there.

Input Schema

{
  "type": "object",
  "properties": {
    "query": {
      "type": "string"
    },
    "country": {
      "type": "string",
      "description": "ISO 3166-1 alpha-2, e.g. SE"
    }
  }
}
🟢get_station(id)

All published facts for one station (lockers, toilets, showers, waiting room at night, step-free access...), each with source and observation date, plus facts not known yet.

Input Schema

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "description": "Station id or slug from search_stations"
    }
  },
  "required": [
    "id"
  ]
}
🟢list_lines

All European night train lines: id, name, operator, booking URL.

Input Schema

{
  "type": "object",
  "properties": {}
}
🟢get_line(id)

All published facts for one night train line (power sockets, bikes, pets, food on board, booking window...) with source and date, and its stations in order.

Input Schema

{
  "type": "object",
  "properties": {
    "id": {
      "type": "string"
    }
  },
  "required": [
    "id"
  ]
}
⚪facts_by_key(key)

One fact across all stations or lines, e.g. key "shower" for every station with a known shower. Use fact_keys for the list.

Input Schema

{
  "type": "object",
  "properties": {
    "key": {
      "type": "string"
    }
  },
  "required": [
    "key"
  ]
}
⚪punctuality(line, train, country, days)

How late night trains really arrive, per train, counted every night by us from Fintraffic and Trafikverket open data: on-time share (within 5 minutes at the last stop), median and 90th percentile delay, cancellations. Filter by line id, train number or country (FI, SE).

Input Schema

{
  "type": "object",
  "properties": {
    "line": {
      "type": "string"
    },
    "train": {
      "type": "string"
    },
    "country": {
      "type": "string"
    },
    "days": {
      "type": "integer",
      "description": "7 to 365, default 365"
    }
  }
}
⚪fact_keys

Every fact key with its type, allowed values and label.

Input Schema

{
  "type": "object",
  "properties": {}
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded7 tools