Skip to main content
Glama
DomainTang

12306-mcp

by DomainTang
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to 12306-mcp

No user-submitted related servers found.

    Related Servers

    • 12306-MCP-Python

      DomainTang
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to query public China Railway 12306 information via MCP, including station lookup, ticket availability, transfer planning, and train route details. It does not support login, booking, or payment.
      MIT

    • 12306-MCP

      xiaobenyang-com
      A
      license
      B
      quality
      D
      maintenance
      12306 ticket purchase search server based on Model Context Protocol (MCP). It provides a simple API interface, allowing large models to search for 12306 ticket purchasing information through the interface.
      8
      1
      Apache 2.0

    • train-mcp-server

      CallwaterSword
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables querying train and high-speed rail schedules, durations, and seat availability between Chinese stations using 12306 data, with automatic fallback to simulated data when the API is rate-limited.
      -

    • 12306 Train MCP

      boy-373
      A
      license
      Not graded
      quality
      B
      maintenance
      Query China railway train schedules, ticket availability and station info via 12306 official API. Streamable HTTP endpoint.
      MIT

    • tripnow-mcp

      huoliAgi
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables real-time flight and train ticket queries, dynamic trip tracking, and knowledge-based Q&A about rail and aviation policies.
      -
    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.4/5.0

    Scored across 8 tools

    Disambiguation2/5

    The station lookup tools heavily overlap: get-stations-code-in-city and get-station-code-of-citys both map a city to station codes, differing only by 'all stations' vs 'representative station'. get-station-code-by-names and get-station-by-telecode add further lookup variants, making it easy for an agent to select the wrong one.

    Naming Consistency3/5

    All tools use a get- prefix, which provides some consistency, but the station-related names are not parallel: get-stations-code-in-city, get-station-code-of-citys, get-station-code-by-names, and get-station-by-telecode follow inconsistent patterns. The 'citys' typo further reduces naming quality.

    Tool Count4/5

    Eight tools is a reasonable size for a train travel assistant. However, four of those tools are dedicated to station-code lookup, which inflates the count and makes the surface feel slightly heavier than necessary.

    Completeness4/5

    Core workflows are covered: getting the current date, resolving station codes, querying direct tickets, querying transfer tickets, and retrieving train route stops. Minor gaps exist such as no explicit ticket price or train status tool, but agents can likely complete common travel queries.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources