Skip to main content
Glama
Sign In
db-timetables-mcp

db-timetables-mcp

by kukshaus
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to db-timetables-mcp

No user-submitted related servers found.

    Related Servers

    • Tessa Travel MCP

      hannes813
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only public-transport station lookup, journey routing with realtime annotations and generated Deutsche Bahn search links, plus current IRIS departure boards by EVA.
      MIT

    • DB Timetable MCP Server

      zzuisa
      A
      license
      A
      quality
      D
      maintenance
      Provides access to Deutsche Bahn's timetable data through MCP, enabling real-time train schedules, station search, and change tracking for German railway stations.
      4
      102 npm
      MIT

    • transit-mcp

      zahraabouzeid
      A
      license
      Not graded
      quality
      B
      maintenance
      Lets an AI assistant plan public transport journeys across Germany and other countries, with legs, platforms, delays and alerts, plus stop departures, full trip details, place search, and live DB station boards. Tickets and prices are not included.
      AGPL 3.0

    • irail-mcp

      HansF
      A
      license
      A
      quality
      C
      maintenance
      Provides Belgian railway travel information via the iRail API, including station search, live departures/arrivals, route planning, and network disturbances.
      5
      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.5/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: one resolves station names to identifiers, one returns outbound departures, one returns inbound arrivals. There is no plausible way an agent would misselect among them.

    Naming Consistency3/5

    find_station follows a verb_noun pattern while departures and arrivals are bare plural nouns, so the convention is mixed. The names are still unambiguous and readable, but there is no single predictable pattern an agent can rely on.

    Tool Count4/5

    Three tools is on the thin side, but for a narrow live-board service each tool earns its place, and the station lookup is a necessary prerequisite for the two board tools. It is slightly minimal rather than bloated.

    Completeness3/5

    Station lookup plus live departure and arrival boards cover the core lookup flow, but the surface has notable gaps for a 'timetables' domain: no journey/connection planning, no scheduled timetable for a specific train, and no way to query a board by station ID without re-searching. Agents needing trip planning will hit a dead end.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources