Skip to main content
Glama
eze-godoy

ns-bridge

by eze-godoy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to ns-bridge

No user-submitted related servers found.

    Related Servers

    • mcp-ns-railways

      McCullonas
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server for querying Dutch railway data via the NS API, with planned tools for station search, departures, trip planning, and disruptions.
      -

    • MCP Trenitalia

      Fanfulla
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for real-time Italian railway data, enabling natural language queries about train schedules, delays, departures, arrivals, and live tracking via the Viaggiatreno API.
      6
      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
      MIT

    • SBB Open Data MCP Server

      malkreide
      A
      license
      A
      quality
      A
      maintenance
      An MCP server for Swiss Federal Railways (SBB) open data, enabling AI models to query real-time disruptions, passenger frequencies, station details, and more without an API key.
      10
      22 PyPI
      2
      MIT

    • db-fahrplan-mcp

      eric134422
      A
      license
      A
      quality
      B
      maintenance
      An (unofficial) MCP server for the Deutsche Bahn Timetables API — station search, planned departures, and real-time changes (delays, platform changes, cancellations) as tools for Claude and other MCP clients.
      4
      2
      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/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: get_departures retrieves departure board information for a single station, search_stations finds station codes, and search_trips plans routes between stations. The descriptions clearly differentiate their functions, making misselection unlikely.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with snake_case naming: get_departures, search_stations, and search_trips. The verbs 'get' and 'search' are appropriately chosen for their respective operations, creating a predictable and readable naming convention throughout.

    Tool Count3/5

    With only 3 tools, the server feels somewhat thin for a train travel domain. While the tools cover core functionalities (departure info, station search, trip planning), additional operations like booking tickets, checking disruptions, or managing favorites would enhance coverage. The count is borderline minimal but functional.

    Completeness4/5

    The tool surface covers essential train travel workflows: finding stations, checking departures, and planning trips with pricing. Minor gaps exist, such as no ticket booking, real-time disruption alerts, or saved trip management, but agents can work effectively with the provided tools for basic planning and information retrieval.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources