Skip to main content
Glama
ContentWriterco

rozklad-mcp

by ContentWriterco
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to rozklad-mcp

No user-submitted related servers found.

    Related Servers

    • ruter-connector

      fredrsat
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to search for stops and stations across all Norwegian public transport and to fetch real-time departure data — planned versus expected times, delays, platform, operator, and disruption messages — with no API key required. Covers bus, tram, metro, train, and ferry nationwide through Entur's open APIs, with filtering by line, destination, and future departure time.
      2
      MIT
    • transcapi-mcp by tcdataconsultants

      transcapi-mcpofficial

      tcdataconsultants
      A
      license
      A
      quality
      B
      maintenance
      Connects AI assistants to live public transport data across Great Britain, enabling searches for stops and stations, real-time bus and rail departures, live vehicle positions, service disruptions, and door-to-door journey planning. All tools are read-only and require an API key.
      10
      122 PyPI
      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.
      15 npm
      MIT

    • Moscow Transport MCP

      zavorateam
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to access real-time public transport data for Moscow and the Moscow region, aggregating and reconciling information from multiple sources. Provides tools for finding stops, live arrival boards, vehicle tracking, route details, and ETA calculations.
      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 6 tools

    Disambiguation5/5

    Each tool targets a clearly distinct purpose: journey planning, departure boards, trip details, stop search by name, stop search by coordinates, and data source metadata. The boundaries are well defined, and descriptions clarify how tools relate (e.g., ref from plan_journey/departures). No tool overlaps significantly with another.

    Naming Consistency4/5

    All names use snake_case consistently, which aids readability. However, the set mixes verb-led names (plan_journey, find_stops) with noun-led names (data_sources, departures, trip_details, nearby_stops), a minor deviation from a single pattern.

    Tool Count5/5

    Six tools are well-scoped for a journey-planning server covering routing, stop lookup, real-time boards, trip details, and metadata. Each tool has a clear, non-redundant role without obvious padding or missing essentials.

    Completeness4/5

    The surface covers core operations: find stops, plan journeys, get departures/arrivals, inspect trip details, and discover data sources. Minor gaps exist, such as no dedicated tool for service alerts/disruptions or line-level schedule queries, but agents can work around these using available tools.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources