Skip to main content
Glama
groundcobra009

yahoo-transit-mcp

by groundcobra009
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to yahoo-transit-mcp

No user-submitted related servers found.

    Related Servers

    • norikae-mcp

      tysonwu
      A
      license
      A
      quality
      D
      maintenance
      MCP server for searching Japanese train routes using Yahoo! Transit data, enabling station-to-station route planning with optional via stations, time specifications, and fare options.
      1
      13 npm
      29
      MIT

    • transit-mcp

      tori-create-7991
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for Japanese public transit journey planning with interactive map UI, enabling station search, route planning, and departure lookups via natural language.
      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

    • ns-bridge

      eze-godoy
      A
      license
      A
      quality
      C
      maintenance
      An MCP server that enables AI assistants to interact with the Netherlands Railways (NS) API for route planning, pricing, and real-time departure information. It provides tools for searching stations, planning trips with connections, and viewing real-time departure boards.
      3
      1
      MIT

    • MCP Trenitalia

      Fanfulla
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for real-time Italian railway data, enabling natural language queries about train schedules, delays, departures, arrivals, and live tracking via the Viaggiatreno API.
      6
      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

    A4.3/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose: station search, route planning, train status, and timetable lookup. There is no overlap or ambiguity between them.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern: search_station, search_route, get_train_status, get_timetable. The naming is uniform and predictable.

    Tool Count5/5

    With 4 tools, the server is well-scoped for a transit domain, covering the essential user needs without unnecessary bloat or missing core functionality.

    Completeness5/5

    The tool set covers station lookup, route planning with fares and times, real-time status, and timetable retrieval. This forms a complete workflow for transit information, with no obvious gaps.

    Maintenance

    ActivityInactive
    ResponsivenessResponsive

    Resources