Skip to main content
Glama
capraCoder

db-fahrplan

by capraCoder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to db-fahrplan

No user-submitted related servers found.

    Related Servers

    • 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
      80 npm
      MIT

    • DB Timetable MCP Server

      jorekai
      A
      license
      A
      quality
      D
      maintenance
      Provides access to Deutsche Bahn train timetables, station information, and schedule changes through Model Context Protocol tools and resources.
      4
      80 npm
      17
      MIT

    • db-fahrplan-mcp

      eric134422
      A
      license
      A
      quality
      B
      maintenance
      An (unofficial) MCP server for the Deutsche Bahn Timetables API — station search, planned departures, and real-time changes (delays, platform changes, cancellations) as tools for Claude and other MCP clients.
      4
      2
      MIT

    • hafasmcp

      mchristoffers
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server for real-time German public transport data (HAFAS/VBN network). Enables querying departures, arrivals, journeys, and nearby stops using natural language.
      -

    • mcp-swisstransport

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables querying Swiss public transport data (stations, departures, connections) from the Transport Open Data API via natural language through an MCP gateway.
      1 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.8/5.0

    Scored across 9 tools

    Disambiguation4/5

    Each tool targets a distinct task: station search, journey planning, fare offers, best-price search, departures, arrivals, trip details, nearby stations, and train formation. The only mild overlap is between db_journey_offers and db_best_price (both fare-related), but their specific purposes and usage cues keep them distinguishable.

    Naming Consistency4/5

    All tools consistently use the `db_` prefix and clear domain vocabulary. Minor inconsistency: `db_search_station` is verb-based while most others are noun phrases (`db_journeys`, `db_departures`), but the overall pattern is still predictable and readable.

    Tool Count5/5

    Nine tools is well-scoped for a rail travel information server. Each tool covers a distinct user need without unnecessary duplication or overwhelming breadth.

    Completeness5/5

    The tool set covers the full journey information workflow: station discovery by name or GPS, journey planning, fare comparison, live departures/arrivals, per-trip stop details, and train formation. There are no obvious dead ends or significant missing operations for the stated domain.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources