Skip to main content
Glama
tyleryancey

stl-transit

by tyleryancey
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to stl-transit

No user-submitted related servers found.

    Related Servers

    • gtfs-scorecard

      ChelseaKR
      A
      license
      B
      quality
      Not graded
      maintenance
      A read-only MCP server that answers questions about GTFS transit feed quality from the published gtfsscorecard.org scorecards: letter grades, the fixes that matter most, and score history. It runs locally over stdio with no API key and no write tools.
      9
      1
      Apache 2.0

    • 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
      8 npm
      MIT

    • db-mcp

      Amor216
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that exposes the Deutsche Bahn public transport API to any MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.). Five tools cover station search, departures, journey planning, trip details, and nearby stations.
      6
      1
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.7/5.0

    Scored across 45 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: static GTFS inspection, realtime decoding, oracle fixtures, web capture, diffing, and support reconstruction are cleanly separated even where they touch similar data. Potentially adjacent tools like stl_gtfs_departures, stl_rt_stop_arrivals, and stl_support_repro are explicitly differentiated by schedule-only vs realtime-merged vs device-reproduction intent.

    Naming Consistency5/5

    Names follow a highly consistent stl_<domain>_<topic> snake_case pattern, with domain prefixes like gtfs, rt, oracle, web, diff, assert, bundle, report, and support. Plural/singular distinctions and verb choices are uniform and predictable across the set.

    Tool Count2/5

    45 tools is far beyond the 3-15 well-scoped range and well above the 25+ 'too many' threshold. The breadth is justified by the domain's complexity, but the raw count still makes the surface heavy and harder for an agent to scan efficiently.

    Completeness5/5

    The tool surface covers the full lifecycle: fetching static and realtime feeds, inspecting GTFS schema and data, querying departures and calendars, decoding realtime protobuf, generating/verifying oracle fixtures, diffing snapshots, capturing web pages, bundling fares/holidays, running assumptions, and producing reports and support reconstructions. No obvious dead-end workflow remains.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources