Skip to main content
Glama
hugorodgerbrown

traintracker

by hugorodgerbrown
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to traintracker

No user-submitted related servers found.

    Related Servers

    • SNCF API MCP Server

      Kryzo
      F
      license
      Not graded
      quality
      D
      maintenance
      A modular Python wrapper for the SNCF API that integrates with Claude Desktop, enabling intelligent journey planning and train information retrieval across France's railway network.
      19
      -

    • railinfo-mcp

      AquibFaiyaz
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables real-time Indian Railways information retrieval, including live train running status, station schedules, and upcoming arrivals/departures.
      -

    • uk-rail-mcp

      RealGUppercut
      F
      license
      Not graded
      quality
      C
      maintenance
      Provides live UK rail data including station search, departures, arrivals, service details, and pre-filled Trainline booking links.
      -

    • Where's My DB?

      dewalt-1
      A
      license
      Not graded
      quality
      D
      maintenance
      A Claude skill + MCP server that tells you how Deutsche Bahn delays will affect your trip — not just whether your train is late.
      MIT

    • mcp-irail

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides real-time Belgian rail (SNCB/NMBS) data via the iRail API, enabling AI agents to query train schedules and live information.
      3 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 9 tools

    Disambiguation4/5

    Each tool targets a distinct station/service/platform resource, and the descriptions clearly separate live departures, platform departures, and a train's platform. The main risk is the departure_platform/platform_departures name pair, which could be confused, but the descriptions disambiguate them well.

    Naming Consistency3/5

    Names are consistently snake_case and readable, but they mix noun-style resources (timetable, service_details, data_status) with verb-style actions (plan_journey, find_station). The departure_platform/platform_departures swapped-word pair also breaks a clear naming pattern.

    Tool Count5/5

    Nine tools is well-scoped for a UK rail information server. Each tool covers a meaningful query type without bloat, and the set feels appropriately sized for both departure boards and journey planning.

    Completeness5/5

    The read-only rail domain is well covered: station lookup, live arrivals/departures, platform data, future timetable, per-service details, and journey planning are all present. The data_status tool also gives agents a way to diagnose missing or stale data sources, avoiding dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources