| FMRS | 66 / 100 · C | 77 / 100 · B | 75 / 100 · B |
|---|
| Reliability | 11 / 20 | 12 / 20 | 13 / 20 |
|---|
| Security and permissions | 13 / 20 | 16 / 20 | 12 / 20 |
|---|
| Maintenance | 13 / 20 | 16 / 20 | 16 / 20 |
|---|
| Documentation | 15 / 20 | 18 / 20 | 17 / 20 |
|---|
| Setup experience | 14 / 20 | 15 / 20 | 17 / 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
| - Scenarios needing clean, structured web context fed to an AI assistant
- Users already on the Firecrawl platform who want to call its scraping capability directly via MCP
|
|---|
| 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)
| - Simple static-page scraping where you don't want to depend on a third-party API and incur call costs
- Sites that explicitly disallow automated access (robots.txt)
|
|---|
| 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
| - Requires a Firecrawl API key to call; cost and quota are governed by the Firecrawl account
- firecrawl_agent/firecrawl_interact perform automated browser interaction, which may trigger login or form-submission flows on the target site
|
|---|
| 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
| - Bulk crawl/map tools can generate significant request volume against a target site — respect the site's rate limits and terms of service
- firecrawl_agent's interactive action chain is longer — define task boundaries clearly before running it to avoid accidentally triggering actions on a sensitive site
|
|---|
| Supported clients | Claude Desktop, Cursor | Claude Desktop, Cursor, Codex, Google Antigravity | Claude Desktop, VS Code, Cursor, Windsurf, Zed, Amp |
|---|
| Tools | 7 | 26 | 11 |
|---|