Remote MCP · Endpoint

City Atlas 城市圖譜 MCP server

No. City Atlas 城市圖譜 answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.cityatlas.tw/mcp

The last check completed an MCP handshake.

Registry name
tw.cityatlas/cityatlas
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
574 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Greater Hsinchu, Taiwan open data on a 125 m grid: crashes, buses, schools, flood. Read-only.
Listing
From the official MCP registry (active).
Recent checks of City Atlas 城市圖譜
CheckedResultHandshake
1 hour agoHandshake completed574 ms
9 days agoHandshake completed204 ms
10 days agoHandshake completed321 ms
11 days agoHandshake completed194 ms
12 days agoHandshake completed186 ms
14 days agoHandshake completed250 ms
14 days agoHandshake completed292 ms
15 days agoHandshake completed66 ms
17 days agoHandshake completed218 ms
19 days agoHandshake completed212 ms
21 days agoHandshake completed199 ms
24 days agoHandshake completed223 ms
26 days agoHandshake completed252 ms
28 days agoHandshake completed316 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 16 responding of 16.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with City Atlas 城市圖譜 and makes no claim about it beyond what these checks measured.