Skip to main content
Glama
fredrsat

ruter-connector

by fredrsat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to ruter-connector

No user-submitted related servers found.

    Related Servers

    • mcp-entur

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides access to Norway's nationwide public transport data (all modes) via the Entur API, enabling queries about routes, stops, and departures through natural language.
      403 npm
      MIT

    • trafikkmeldinger-mcp

      smlhus1
      A
      license
      A
      quality
      B
      maintenance
      Enables querying Norwegian traffic messages (roadworks, closures, detours) from Statens vegvesen, filtered by route and time window. Supports both current and future travel times, with tools for route-based and general searches.
      3
      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
      259 PyPI
      MIT

    • rozklad-mcp

      ContentWriterco
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to search Polish public transport timetables — trains, PKS/regional buses, and optionally urban transit in ~20 cities — by planning journeys with transfers, checking departures with platforms, and tracking live delays, cancellations and full trip details, all from open GTFS data without an API key. Station lookup tolerates typos and missing Polish diacritics, and endpoints can be a stop, a whole city, or coordinates.
      6
      418 npm
      34
      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.9/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools serve clearly distinct purposes: one searches for stops by name, the other retrieves departures for a given stop. There is no overlap or ambiguity in their intended use.

    Naming Consistency3/5

    The names follow mixed conventions: 'finn_stoppested' is a verb+noun phrase, while 'avganger' is a noun. This inconsistency makes the pattern less predictable, though both are descriptive.

    Tool Count3/5

    Two tools is borderline thin for a transit connector. While they cover a basic workflow (find stop, get departures), the server name suggests a broader API surface that is not represented.

    Completeness3/5

    The core workflow of finding a stop and checking departures is covered, but notable gaps exist such as journey planning, line information, and location-based stop lookup, which are typical for a Ruter connector.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources