Remote MCP · Endpoint

ALGO BIZ: Japan towns, jobs and industries MCP server

No. ALGO BIZ: Japan towns, jobs and industries answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://yy-algo.com/mcp/

The last check completed an MCP handshake.

Registry name
com.yy-algo/japan-data
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
571 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Japanese statistics: 1,889 towns, job-openings ratios, 62 industries and a town x industry sheet.
Listing
From the official MCP registry (active).
Recent checks of ALGO BIZ: Japan towns, jobs and industries
CheckedResultHandshake
7 hours agoHandshake completed571 ms
4 days agoHandshake completed727 ms
14 days agoHandshake completed944 ms
15 days agoHandshake completed717 ms
15 days agoHandshake completed913 ms
17 days agoHandshake completed798 ms
18 days agoHandshake completed626 ms
19 days agoHandshake completed752 ms
20 days agoHandshake completed525 ms
21 days agoHandshake completed1.70 s
23 days agoHandshake completed556 ms
26 days agoHandshake completed550 ms

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

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 ALGO BIZ: Japan towns, jobs and industries and makes no claim about it beyond what these checks measured.