Remote MCP · Endpoint

クビアカのいま (Aromia bungii in Japan) MCP server

No. クビアカのいま (Aromia bungii in Japan) answered an MCP handshake 42 minutes ago.

UpLast checked 42 minutes ago

Server URL

https://kubiaka-now.com/mcp

The last check completed an MCP handshake.

Registry name
com.kubiaka-now/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
228 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Red-necked longhorn beetle (Aromia bungii) in Japan: damage status, new detections, rewards by city.
Listing
From the official MCP registry (active).
Recent checks of クビアカのいま (Aromia bungii in Japan)
CheckedResultHandshake
42 minutes agoHandshake completed228 ms
3 days agoHandshake completed178 ms
13 days agoHandshake completed195 ms
13 days agoHandshake completed197 ms
15 days agoHandshake completed225 ms
15 days agoHandshake completed244 ms
17 days agoHandshake completed72 ms
18 days agoHandshake completed193 ms
18 days agoHandshake completed131 ms
20 days agoHandshake completed154 ms
22 days agoHandshake completed184 ms
25 days agoHandshake completed152 ms
27 days agoHandshake completed138 ms

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

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 クビアカのいま (Aromia bungii in Japan) and makes no claim about it beyond what these checks measured.