Skip to main content
Glama
yasg1988

transport12 MCP Server

by yasg1988
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to transport12 MCP Server

No user-submitted related servers found.

    Related Servers

    • mcp-hsl

      devusvulgaris
      A
      license
      A
      quality
      B
      maintenance
      An MCP server exposing Greater Helsinki public transport data from Digitransit, enabling LLM hosts to answer live transit queries, plan journeys, and fetch stop departures via natural language.
      3
      6 npm
      MIT

    • mcp-stm-montevideo

      chaba11
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server exposing Montevideo public transportation data (STM) as tools for AI assistants, enabling natural language queries about routes, stops, arrivals, and trip planning.
      3 npm
      1
      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.
      -

    • BVG MCP Server

      uniquename
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for interacting with the Berlin Public Transport (BVG) API to search for locations and plan journeys. It provides real-time access to departures, arrivals, trip details, and vehicle tracking within Berlin's transit network.
      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

    B3.2/5.0

    Scored across 17 tools

    Disambiguation3/5

    Most tools have clear resource-specific boundaries, but health and get_service_status overlap in purpose, and get_bus_station_races versus get_bus_station_calendar may confuse agents about which returns actual races versus availability. search_everything also partially duplicates the individual search tools, though its aggregate intent is clear.

    Naming Consistency4/5

    The tool set follows a consistent snake_case verb_noun pattern with get_, search_, and find_ prefixes, making the API largely predictable. The lone 'health' tool breaks the pattern slightly, but it is still easily understood as a status check.

    Tool Count4/5

    With 17 tools, the server is at the upper edge of a reasonable size, but the breadth of the domain—stops, routes, vehicles, bus stations, and tickets—justifies the count. No tool feels redundant enough to remove outright, though the three health/summary tools could arguably be consolidated.

    Completeness4/5

    The server covers the core read-only workflows for a transit API: searching stops/routes, retrieving arrivals and vehicle forecasts, and exploring bus station races and ticket URLs. Minor gaps exist such as lack of a stop detail endpoint, route schedule/timetable data, or direct bus station lookup by ID, but agents can work around these with the provided surface.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources