DealLabs
net.deallabs/city-data · v0.2.2 · MCP 2026-07-28
Read-only city data: places, station exits, last trains. Each answer carries its source and date.
Reachability
reachable
checked 2026-11-21 05:34 UTC
Registry status active
Tools pinned 4
5f0c10a68f72
Tools last changed
unchanged since first capture 2026-11-18
Provenance
Registry namespace net.deallabs
(domain verified by the official registry)
Website
https://deallabs.net/connect
Remote endpoints
https://deallabs.net/mcp (streamable-http)
Observed changes
| When (UTC) | Event | Detail |
|---|---|---|
| 2026-11-18 05:31 | first capture | 4 tools pinned |
Pinned tool definitions (4)
| Tool | Description |
|---|---|
| search_verified_places | Find places and stations by name, kind, category, area, nearness or opening time. Answers only from data-standard v1 records; null values are reported as not_known. It does not return train times: for a station's exits or its last... |
| find_active_popups | Pop-ups running on a day. Returns an empty list with reason_code no_v1_records until the city publishes pop-up records in data-standard v1. |
| get_station_exit | The station record, its exits, its last-train times by line and direction (weekday, Saturday and Sunday; Seoul and Busan publish them; other cities answer last_trains as not_published), and (with "to") the walk from the station to a... |
| plan_local_route | Can these stops fit in this time, in this order? Judges each stop with its posted hours on the date. The tool does not guess how long a visit takes: visit_min is required. |
Get alerted when this changes.
Email the moment net.deallabs/city-data drifts, dies, or revives.
Status badge
[](https://toolpin.dev/servers/net.deallabs/city-data)
Maintain this server? Add the badge to your README. It links your users to this live status page.