Remote MCP · Endpoint

app.netlify.japan-data-mcp/japan-data-mcp MCP server

No. app.netlify.japan-data-mcp/japan-data-mcp answered an MCP handshake 11 hours ago.

UpLast checked 11 hours ago

Server URL

https://japan-data-mcp.netlify.app/mcp

The last check completed an MCP handshake.

Registry name
app.netlify.japan-data-mcp/japan-data-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
148 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Japanese law, corporation & statistics data as MCP, normalized to English with source attribution.
Listing
From the official MCP registry (active).
Recent checks of app.netlify.japan-data-mcp/japan-data-mcp
CheckedResultHandshake
11 hours agoHandshake completed148 ms
2 days agoHandshake completed149 ms
4 days agoHandshake completed152 ms
6 days agoHandshake completed157 ms
7 days agoHandshake completed233 ms
8 days agoHandshake completed186 ms
9 days agoHandshake completed248 ms
12 days agoHandshake completed123 ms
14 days agoHandshake completed166 ms
15 days agoHandshake completed366 ms
16 days agoHandshake completed187 ms
18 days agoHandshake completed203 ms
19 days agoHandshake completed256 ms
19 days agoHandshake completed238 ms
20 days agoHandshake completed174 ms
21 days agoHandshake completed331 ms
23 days agoHandshake completed173 ms

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

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 app.netlify.japan-data-mcp/japan-data-mcp and makes no claim about it beyond what these checks measured.