Remote MCP · Endpoint

Gachi Data API — Japan Station & Accessibility Data MCP server

No. Gachi Data API — Japan Station & Accessibility Data answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://api.gachi-tokusuru.com/mcp

The last check completed an MCP handshake.

Registry name
com.gachi-tokusuru/japan-data-api
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
89 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Deep, obscure Japanese station, accessibility & hazard data for AI agents. English-first.
Listing
From the official MCP registry (active).
Recent checks of Gachi Data API — Japan Station & Accessibility Data
CheckedResultHandshake
2 hours agoHandshake completed89 ms
1 day agoHandshake completed132 ms
3 days agoHandshake completed60 ms
3 days agoHandshake completed66 ms
4 days agoHandshake completed67 ms
5 days agoHandshake completed181 ms
7 days agoHandshake completed115 ms
10 days agoHandshake completed82 ms
12 days agoHandshake completed65 ms
15 days agoHandshake completed77 ms
17 days agoHandshake completed123 ms
19 days agoHandshake completed81 ms
21 days agoHandshake completed69 ms
23 days agoHandshake completed80 ms
25 days agoHandshake completed58 ms
26 days agoHandshake completed76 ms
28 days agoHandshake completed163 ms
29 days agoHandshake completed134 ms

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

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 Gachi Data API — Japan Station & Accessibility Data and makes no claim about it beyond what these checks measured.