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
      C
      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.
      6
      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

    • mcp-tfl-journey

      alisonborba
      A
      license
      B
      quality
      D
      maintenance
      Provides real-time Transport for London journey data, including routes, alerts, and disruptions, allowing AI assistants to search journeys and get station information.
      1
      24
      4
      ISC

    • mcp-irail

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides real-time Belgian rail (SNCB/NMBS) data via the iRail API, enabling AI agents to query train schedules and live information.
      5
      MIT
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.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

    ActivityMaintained
    ResponsivenessNo issues

    Resources