← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

Dimension12306 MCP ServerMCP server for real-time 12306 train ticket queriesHevy MCPManage your Hevy workout data from AI assistants via MCP.
FMRS66 / 100 · C77 / 100 · B
Reliability11 / 2012 / 20
Security and permissions13 / 2016 / 20
Maintenance13 / 2016 / 20
Documentation15 / 2018 / 20
Setup experience14 / 2015 / 20
Best for
  • Individuals planning train travel within China
  • Developers who want 12306 query capabilities inside MCP clients such as Claude Desktop or Cursor
  • Teams that need a self-hosted remote HTTP MCP service or Docker deployment
  • Developers studying MCP server implementations
  • Hevy PRO users who want AI assistants to directly access their workout data
  • People who prefer using MCP clients like Claude, Cursor, Codex for fitness tracking
  • Anyone needing summaries and insights from their training data
Not for
  • Scenarios needing official booking, rebooking, refunds or payment (this project is query-only)
  • Commercial use or production systems with availability/SLA requirements
  • Mission-critical workloads that cannot tolerate upstream API changes or volatility
  • Users expecting official 12306 support or endorsement
  • Users without a Hevy PRO subscription (API key required)
  • Users who want to use the server without an API key
  • Those needing delete workflows (Hevy API does not expose delete endpoints)
Required permissions
  • Network access: must be able to reach the official 12306 endpoints
  • Local file reads: loads bundled static resources such as station data
  • HTTP mode port binding: listens on 0.0.0.0:8000 by default
  • Reads a .env file in the project root when used
  • Requires HEVY_API_KEY environment variable for Hevy API authentication
  • Can create, update, and replace workouts, routines, folders, templates, and body measurements via tools
  • Read operations can fetch workouts, routines, folders, templates, history, and user info
Risks and side effects
  • Unofficial third-party project that only aggregates and relays 12306 public endpoints; upstream changes or rate limits can break queries
  • The README explicitly states it is for learning and research only and prohibits commercial use; users bear the consequences of use
  • Binding HTTP to 0.0.0.0 may expose the port to other hosts on the network, and no authentication mechanism is described
  • Frequent upstream calls may trigger rate limiting or affect the user's account
  • Results depend on upstream data and may be delayed or inaccurate, so they should not be the sole basis for decisions
  • API key can be misused if leaked; do not expose in URLs, logs, or screenshots
  • Create operations may produce duplicates on retry; update operations replace existing records
  • The server sends data to the Hevy API and may send telemetry to external services unless disabled
Supported clientsClaude Desktop, CursorClaude Desktop, Cursor, Codex, Antigravity
Tools726