Skip to main content
Glama
rsiva2294

madurai-transit-mcp

by rsiva2294
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to madurai-transit-mcp

No user-submitted related servers found.

    Related Servers

    • 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
      21 npm
      4
      ISC

    • oasa-mcp

      fabianhogger
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to query live arrivals, vehicle positions, routes, stops, and timetables across the Athens public transport network, with stop lookups by name or coordinate in Greek or Latin script. Results cover OASA buses, trolleys, metro, and tram, falling back to cached reference data when the upstream API is unreachable.
      MIT

    • transit-mcp

      aminamos
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to access real-time and scheduled public transit data, including routes, stops, departures, and service alerts, across multiple US metropolitan areas.
      5
      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

    A4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: finding routes between stops, retrieving details for a specific bus number, searching stops, and calculating fares. No overlapping functionality, so an agent can easily select the right tool.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (search_bus_routes, get_bus_details, search_bus_stops, calculate_fare). This creates a predictable and uniform naming convention.

    Tool Count5/5

    With only 4 tools, the server is well-scoped for its narrow domain of Madurai bus transit. Each tool serves a necessary function, and the count is within the ideal 3-15 range.

    Completeness4/5

    The tool surface covers the core transit workflows: route search, bus details, stop lookup, and fare calculation. Missing features like schedule or real-time tracking are not implied by the domain scope, so only minor gaps exist.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources