Remote MCP · Endpoint

KIKARET MCP server

No. KIKARET answered an MCP handshake 8 hours ago.

UpLast checked 8 hours ago

Server URL

https://mcp.kikaret.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.kikaret/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
205 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Structured Japanese childcare facility data with source-backed facts for AI.
Listing
From the official MCP registry (active).
Recent checks of KIKARET
CheckedResultHandshake
8 hours agoHandshake completed205 ms
2 days agoHandshake completed86 ms
4 days agoHandshake completed179 ms
5 days agoHandshake completed44 ms
7 days agoHandshake completed196 ms
8 days agoHandshake completed351 ms
9 days agoHandshake completed152 ms
12 days agoHandshake completed164 ms
13 days agoHandshake completed146 ms
15 days agoHandshake completed221 ms
16 days agoHandshake completed31 ms
17 days agoHandshake completed152 ms
18 days agoHandshake completed154 ms
19 days agoHandshake completed224 ms
20 days agoHandshake completed90 ms
21 days agoHandshake completed144 ms
23 days agoHandshake completed160 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 KIKARET and makes no claim about it beyond what these checks measured.