Remote MCP · Endpoint

Kata (型) MCP server

No. Kata (型) answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.hakuto-0209.com/kata

The last check completed an MCP handshake.

Registry name
com.hakuto-0209/kata
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
68 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
実在の日本のLP/HPを参考に返す。業種や雰囲気からURLと実測配色を数件。無料・鍵不要。
Listing
From the official MCP registry (active).
Recent checks of Kata (型)
CheckedResultHandshake
1 hour agoHandshake completed68 ms
2 days agoHandshake completed46 ms
4 days agoHandshake completed62 ms
5 days agoHandshake completed73 ms
7 days agoHandshake completed73 ms
8 days agoHandshake completed68 ms
9 days agoHandshake completed50 ms
12 days agoHandshake completed68 ms
13 days agoHandshake completed49 ms
15 days agoHandshake completed57 ms
16 days agoHandshake completed47 ms
17 days agoHandshake completed51 ms
18 days agoHandshake completed60 ms
19 days agoHandshake completed71 ms
20 days agoHandshake completed65 ms
21 days agoHandshake completed56 ms
22 days agoHandshake completed67 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 Kata (型) and makes no claim about it beyond what these checks measured.