Remote MCP · Endpoint

遊戲發售日與預告片資料庫 MCP server

No. 遊戲發售日與預告片資料庫 answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://tw-game-release.panda198271.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.workers.panda198271.tw-game-release/game-release
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
364 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
全球 PC、主機、手機遊戲發售日、延期紀錄與官方預告片(繁體中文)。
Listing
From the official MCP registry (active).
Recent checks of 遊戲發售日與預告片資料庫
CheckedResultHandshake
1 hour agoHandshake completed364 ms
2 days agoHandshake completed309 ms
4 days agoHandshake completed295 ms
6 days agoHandshake completed408 ms
8 days agoHandshake completed310 ms
10 days agoHandshake completed42 ms
11 days agoHandshake completed292 ms
13 days agoHandshake completed321 ms
14 days agoHandshake completed325 ms
15 days agoHandshake completed332 ms
18 days agoHandshake completed67 ms
19 days agoHandshake completed55 ms
21 days agoHandshake completed91 ms
22 days agoHandshake completed81 ms
23 days agoHandshake completed50 ms

The last 15 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 15.

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.