A pasteable skeleton generated from the repository name. Check the project README for the exact package and arguments.
Star count
21 ★ · arthurpanhku/DragonMCP · read from the GitHub search API · (checked 2026-10-16 20:00:20)
Source
collected from the punkpeye/awesome-mcp-servers list · type: MCP server
Harvest history
first seen 2026-10-09 · last seen 2026-10-16 · seen 32× · listed by 7 sources
Score
score 703 · 21 ★ · 7 sources · mcp
FAQ (answers come from our records)
How do I install it?
We did not find an install command for this repository (our install coverage is only about 4%). Check its README or releases page.
Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository arthurpanhku/DragonMCP;first catalogued 2026-10-09;last seen 2026-10-16。There is no official certification or quality rating here — we record sources and dates only.
**Hong Kong & cross-border open data for AI Agents** English | 简体中文 Live MTR arrivals, HK Observatory weather, and Mainland China routing — over the Model Context Protocol. Quickstart • Tools • Limitations • Roadmap --- 🌟 What is DragonMCP? An MCP server that gives AI agents **real, verifiable public data** for Hong Kong and the Mainland China border region. **Every tool in this server calls a live API. There are no mocks.** If an upstream source is down, the tool says so — it never invents a plausible-looking answer. You can verify this yourself at any time with the built-in system_run_selftest tool, which pings every upstream and reports what is actually reachable. Why this niche: Hong Kong's public data is genuinely open (data.gov.hk, no keys, no rate-limit paperwork) but scattered across agencies with inconsistent formats. And cross-border trips — where a single journey spans MTR, the Mainland rail network, and two different weather authorities — are exactly the case no single agency has any incentive to serve. --- 🔥 Live example **MTR real-time arrivals** — no API key required: **Hong Kong Observatory** — no API key required, includes active warnings: --- 🛠️ Tools | Tool | Source | API key | What it does | | :--- | :--- | :--- | :--- | | search_mtr_schedule | MTR via data.gov.hk | — | Journey planning **with transfers** + real-time arrivals; all 10 lines, all 98 stations | | hk_weather_current | HK Observatory | — | Current conditions + active warnings | | hk_typhoon_signal | HK Observatory | — | Structured typhoon, rainstorm, and other active warning status | | search_transit_route | MTR / Amap | CN only | Unified HK/CN routing; picks the right provider | | system_run_selftest | all of the above | — | Live reachability check of every upstream | | amap_search_poi | Amap (Gaode) | ✅ | POI search in Mainland China | | amap_walking_direction | Amap (Gaode) | ✅ | Walking route | | amap_driving_direction | Amap (Gaode) | ✅ | Driving route | | amap_transit_direction | Amap (Gaode) | ✅ | Public transit route | | amap_bicycling_direction | Amap (Gaode) | ✅ | Cycling route | **MTR coverage** — all 10 lines, station names accepted in English or Chinese: Island (港岛线) · Tsuen Wan (荃湾线) · Kwun Tong (观塘线) · Tseung Kwan O (将军澳线) · **East Rail (东铁线, runs to Lo Wu 罗湖 and Lok Ma Chau 落马洲)** · Tuen Ma (屯马线) · South Island (南港岛线) · Tung Chung (东涌线) · Airport Express (机场快线) · Disneyland Resort (迪士尼线) --- ⚠️ Limitations Stated up front, because a tool that hides its limits is a tool that lies to your agent: - **Routes minimise transfers, not travel time.** No inter-station running times are published, so we optimise for the thing we can actually measure. Occasionally a two-transfer route is faster than the one-transfer route returned. - **Real-time arrivals cover the boarding leg only.** Without running times we cannot say when you will reach a transfer station, so quoting arrivals for later legs would be invention. - **Two stations have no real-time feed.** The upstream API serves no arrivals for Tin Hau or Prince Edward. Routing through them works; arrivals at them are reported as unavailable rather than faked.