Skip to main content
Glama
aaronbiscotti

prt-mcp

by aaronbiscotti
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to prt-mcp

No user-submitted related servers found.

    Related Servers

    • stl-transit

      tyleryancey
      F
      license
      A
      quality
      C
      maintenance
      MCP server for St. Louis transit developer tooling, providing 45 tools for GTFS and GTFS-Realtime inspection, feed surveillance, schedule and arrival queries, assertions, drift detection, and golden-fixture generation for the Light Phone 3 Kotlin transit app, all backed by public unauthenticated sources.
      45
      -

    • transport12 MCP Server

      yasg1988
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that integrates with the transport12 API to provide tools for searching stops, routes, arrivals, and vehicle forecasts, enabling natural language interaction with public transport data.
      4 npm
      MIT

    • 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
      6 npm
      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

    B3.2/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct TrueTime data endpoint: routes, directions, stops, vehicles, predictions, patterns, and service bulletins. The nouns alone make the intended data type unambiguous, so an agent can reliably select the correct tool.

    Naming Consistency5/5

    Every tool follows the same prt_get_<plural_noun> snake_case pattern with a shared prt prefix. There are no deviations in verb style, casing, or structure, making the set highly predictable.

    Tool Count5/5

    Seven read-only tools map cleanly to the seven TrueTime API endpoints. The count is well-scoped for a transit data wrapper, with no redundant or filler tools.

    Completeness5/5

    The surface covers the full TrueTime read-only endpoint set: routes, directions, stops, vehicles, predictions, patterns, and service bulletins. All standard transit-data queries are reachable with no obvious dead ends for the stated purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources