Remote MCP · Endpoint

ベストカレンダー 暦データ MCP server

No. ベストカレンダー 暦データ answered an MCP handshake 20 minutes ago.

UpLast checked 20 minutes ago

Server URL

https://bestcalendar.jp/mcp

The last check completed an MCP handshake.

Registry name
jp.bestcalendar/koyomi
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
381 ms
Tools exposed
16 tools
Uptime, last 30 days
91.7% from 12 checks
Described by its publisher as
Japanese calendar data (rokuyo, lucky days, solar terms, holidays, moon, sunrise), 1926-2080.
Listing
From the official MCP registry (active).
Recent checks of ベストカレンダー 暦データ
CheckedResultHandshake
20 minutes agoHandshake completed381 ms
3 days agoFailed - the request timed out—
14 days agoHandshake completed451 ms
14 days agoHandshake completed1.79 s
15 days agoHandshake completed329 ms
16 days agoHandshake completed332 ms
18 days agoHandshake completed368 ms
18 days agoHandshake completed345 ms
19 days agoHandshake completed2.50 s
21 days agoHandshake completed1.18 s
22 days agoHandshake completed327 ms
25 days agoHandshake completed324 ms

The last 12 checks. Full history is kept for 30 days; the all-time counter stands at 11 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 ベストカレンダー 暦データ and makes no claim about it beyond what these checks measured.