M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← 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 queriesFirecrawl MCP ServerFirecrawl's official MCP server for web search, scraping, and structured extraction for AI agents
FMRS66 / 100 · C75 / 100 · B
Reliability11 / 2013 / 20
Security and permissions13 / 2012 / 20
Maintenance13 / 2016 / 20
Documentation15 / 2017 / 20
Setup experience14 / 2017 / 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
  • 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
  • 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 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
  • 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 clientsClaude Desktop, CursorClaude Desktop, VS Code, Cursor, Windsurf, Zed, Amp
Tools711