Remote MCP · Endpoint

Hokyo MCP Server MCP server

No. Hokyo MCP Server answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://bustup-monitor.com/mcp

The last check completed an MCP handshake.

Registry name
com.bustup-monitor/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
357 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
豊胸モニター募集サイトのMCPサーバー。クリニック検索・術式情報・悩み相談・世代別記事を提供します。
Listing
From the official MCP registry (active).
Recent checks of Hokyo MCP Server
CheckedResultHandshake
1 hour agoHandshake completed357 ms
2 days agoHandshake completed362 ms
4 days agoHandshake completed88 ms
5 days agoHandshake completed44 ms
7 days agoHandshake completed291 ms
8 days agoHandshake completed439 ms
9 days agoHandshake completed296 ms
12 days agoHandshake completed323 ms
13 days agoHandshake completed223 ms
15 days agoHandshake completed517 ms
16 days agoHandshake completed48 ms
17 days agoHandshake completed144 ms
18 days agoHandshake completed153 ms
19 days agoHandshake completed178 ms
20 days agoHandshake completed39 ms
21 days agoHandshake completed253 ms
22 days agoHandshake completed40 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 Hokyo MCP Server and makes no claim about it beyond what these checks measured.