Skip to main content
Glama
Sign In
idfm-mcp

idfm-mcp

by Drathod-24
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to idfm-mcp

No user-submitted related servers found.

    Related Servers

    • IDFM Transit MCP

      MaximeGrn
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables assistants to search stations and places, plan journeys, check next departures, monitor disruptions, and assess journey status across Île-de-France public transport using official IDFM PRIM APIs. It supports métro, RER, Transilien, tram, and bus modes without hardcoded stations or routes.
      MIT

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

    • Live Transit MCP Server

      loama
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to query live public transport status, alerts, line maps and vehicle positions across worldwide networks through tools such as search, network_status, line_status, disruptions, airport and vehicles_near.
      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.3/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool maps to a clearly distinct transit task: station lookup, real-time departures, journey planning, and disruption status. There is little risk of misselection, and descriptions reinforce the boundaries between tools.

    Naming Consistency3/5

    Two tools follow a verb_noun pattern (search_stop, plan_journey), but next_departures is an adjective_noun phrase and traffic_disruptions is a noun_noun phrase. The names are readable and individually clear, but the set does not follow one predictable convention.

    Tool Count5/5

    Four tools is well-scoped for a focused Île-de-France transit query server. Each tool serves a distinct core user need, and there are no redundant or filler tools.

    Completeness4/5

    The server covers the main transit workflows: finding stops, checking next departures, planning journeys, and viewing disruptions. Minor gaps remain, such as line-level details, fare information, or accessibility-specific queries, but agents can handle core tasks without dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources