Skip to main content
Glama
vbhjckfd
by vbhjckfd

Related Servers

Alternatives to mcp-lad-lviv-ua

  • F
    license
    Not graded
    quality
    D
    maintenance
    A server that provides seamless access to the GTFOBins database through Claude Desktop, allowing users to query exploitation techniques, search for specific binaries, and explore privilege escalation methods directly from Claude conversations.
    -
  • F
    license
    Not graded
    quality
    D
    maintenance
    Provides real-time transit data for OC Transpo in Ottawa, including live vehicle positions and trip updates via GTFS-RT feeds. It enables AI agents to monitor arrival delays, schedule changes, and transit telemetry through the Model Context Protocol.
    2
    -

Related Servers

  • A
    license
    Not graded
    quality
    B
    maintenance
    Live intercity bus-trip search across Ukraine and Europe — real-time prices, seats, carriers, cheapest-day-of-month calendar, and trip details with passenger discounts. Read-only, no API key; also available as a hosted remote endpoint at https://mcp.soloway.com.ua/mcp.
    MIT
  • A
    license
    C
    quality
    C
    maintenance
    MCP server for the UK Bus Open Data Service, enabling timetable queries, stop search, route discovery, journey planning, and real-time bus tracking.
    16
    23 PyPI
    MIT
  • A
    license
    Not graded
    quality
    D
    maintenance
    Read-only MCP server that queries Russian Railways (ticket.rzd.ru) for train schedules, car types, prices, and seat availability. It provides official RZD links for manual booking but does not log in, book, or pay.
    31 npm
    2
    MIT
  • A
    license
    A
    quality
    B
    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

TDQS

A4.9/5.0

Scored across 5 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: route static vs realtime, stop geometry vs realtime, and stop discovery. Descriptions explicitly disambiguate when to use each, leaving no ambiguity.

Naming Consistency5/5

All tool names follow the consistent pattern 'get_[resource]_[modifier]' in snake_case, e.g., get_route_realtime, get_stop_geometry. The naming is predictable and easy to understand.

Tool Count5/5

5 tools is well-scoped for a transit information server, covering all essential operations: route static and realtime data, stop static geometry and realtime arrivals, and stop discovery. No excess or deficiency.

Completeness5/5

The tool surface is complete for the domain: users can discover stops, get realtime arrivals, static route info, route shapes, and live vehicle positions. There are no obvious gaps such as missing CRUD operations or dead ends.

Maintenance

ActivityActive
ResponsivenessNo issues