Skip to main content
Glama
vladirocox

STPT MCP

by vladirocox
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to STPT MCP

No user-submitted related servers found.

    Related Servers

    • mcp-tfl

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides keyless, real-time access to London transport data, letting agents check line service status, search stops and stations, fetch live predicted arrivals, plan journeys across modes and postcodes, see Santander cycle-hire dock availability, and list current disruptions. It can be used as a hosted remote MCP endpoint, a local stdio server, or plain HTTP calls.
      6 npm
      MIT

    • chelaile-mcp

      PeanutSplash
      A
      license
      A
      quality
      C
      maintenance
      MCP server for Chelaile realtime public transit data in China, including bus and metro arrivals, vehicle positions, nearby stops, timetables, and route planning. It runs locally over stdio with no login or account configuration required.
      15
      1,477 npm
      24
      MIT

    • Bay Area Transit MCP

      srivastsh
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables querying real-time BART and SF Muni transit data, including departures, trip planning, fares, advisories, routes, alerts, vehicle positions, and schedules, from any MCP-compatible client.
      1
      MIT

    • RedTransporteMCP

      iiroak
      A
      license
      A
      quality
      C
      maintenance
      Private MCP server adapter for RedTransporteAPI, providing read-only access to Santiago de Chile public transit data including stops, routes, real-time iBus/RED predictions, and RAPTOR journey planning, secured with deny-by-default bearer token authentication over stdio or streamable HTTP.
      15
      1
      GPL 3.0
    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 7 tools

    Disambiguation5/5

    Each tool targets a distinct transit object or concern: stop search, stop detail, route listing, arrivals, service status, alerts, and vehicle positions. Boundaries are clear even where arrivals and vehicle positions both relate to live transit data.

    Naming Consistency5/5

    All tool names use a consistent snake_case verb_noun convention: search_stops, get_stop, list_routes, get_arrivals, get_service_status, get_alerts, get_vehicles. No ambiguous or inconsistent naming styles appear.

    Tool Count5/5

    Seven tools is well-scoped for a transit MCP server, covering discovery, detail, arrivals, alerts, vehicles, and health without bloat. Each tool has a clear role.

    Completeness4/5

    The surface covers core transit workflows: finding stops, viewing routes and stop details, checking arrivals, alerts, and vehicle positions. Minor gaps exist, such as explicit route-detail or trip-planning operations, but core use cases are supported.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources