Skip to main content
Glama
freestylefly

12306-MCP

by freestylefly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to 12306-MCP

No user-submitted related servers found.

    Related Servers

    • 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

    • 12306 MCP Server

      drfccv
      A
      license
      A
      quality
      B
      maintenance
      A high-performance FastAPI backend for train ticket queries in China, supporting real-time ticket availability, station information, transfers, and train schedules through the Model Context Protocol for AI assistants and automation.
      7
      394
      MIT

    • 12306-mcp

      DomainTang
      A
      license
      B
      quality
      C
      maintenance
      Enables searching 12306 railway ticket information, filtering trains, querying passing stations, and searching transfer routes through MCP.
      8
      7,295 npm
      MIT

    • JSON Query MCP

      mgraczyk
      F
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server for querying large JSON files using JSONPath expressions, enabling LLMs to efficiently search and extract information from large JSON data.
      3
      11
      -
    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

    A3.9/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap. Tools target specific functions like date retrieval, station code lookup (by telecode, names, cities, or stations in a city), ticket queries (direct and interline), and train route details, making misselection unlikely.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with 'get-' prefix (e.g., get-current-date, get-tickets). The naming is uniform and predictable, enhancing readability and usability.

    Tool Count5/5

    With 8 tools, the server is well-scoped for querying 12306 train data. Each tool serves a specific role in the workflow, from station code resolution to ticket and route queries, without being overly sparse or bloated.

    Completeness4/5

    The toolset covers core functionalities like date handling, station code retrieval, ticket queries, and route details, supporting key user workflows. A minor gap is the lack of booking or purchase tools, but this is reasonable for a query-focused server.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources