Remote MCP · Endpoint

コエカツ アンケート集計データ MCP server

No. コエカツ アンケート集計データ answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.datasetsearch.jp/

The last check completed an MCP handshake.

Registry name
jp.datasetsearch/koekatsu
Transport
Streamable HTTP
Protocol negotiated
2025-11-25
Handshake latency
660 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
コエカツの公開アンケート集計を検索・取得できる読み取り専用サーバー。登録不要。引用用の時点固定URLと出典つき。
Listing
From the official MCP registry (active).
Recent checks of コエカツ アンケート集計データ
CheckedResultHandshake
1 hour agoHandshake completed660 ms
2 days agoHandshake completed681 ms
4 days agoHandshake completed609 ms
5 days agoHandshake completed662 ms
7 days agoHandshake completed1.08 s
8 days agoHandshake completed629 ms
9 days agoHandshake completed621 ms
12 days agoHandshake completed561 ms
13 days agoHandshake completed605 ms
15 days agoHandshake completed710 ms
17 days agoHandshake completed567 ms
18 days agoHandshake completed560 ms
19 days agoHandshake completed582 ms
20 days agoHandshake completed670 ms
21 days agoHandshake completed628 ms
21 days agoHandshake completed618 ms
23 days agoHandshake completed659 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 コエカツ アンケート集計データ and makes no claim about it beyond what these checks measured.