Remote MCP · Endpoint

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

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

UpLast checked 7 hours ago

Server URL

https://game.penguindriver.com/mcp

The last check completed an MCP handshake.

Registry name
com.penguindriver/game
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
367 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
遊戲發售日與預告片資料庫：新作發售日、延期消息與官方預告。台灣繁體中文 MCP 工具。
Website
https://game.penguindriver.com/
Listing
From the official MCP registry (active).
Recent checks of 遊戲發售日與預告片資料庫
CheckedResultHandshake
7 hours agoHandshake completed367 ms
2 days agoHandshake completed757 ms
4 days agoHandshake completed364 ms
6 days agoHandshake completed319 ms
8 days agoHandshake completed286 ms
10 days agoHandshake completed329 ms
12 days agoHandshake completed402 ms
13 days agoHandshake completed382 ms
14 days agoHandshake completed341 ms
15 days agoHandshake completed288 ms
18 days agoHandshake completed98 ms
20 days agoHandshake completed53 ms
21 days agoHandshake completed89 ms
23 days agoHandshake completed45 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with 遊戲發售日與預告片資料庫 and makes no claim about it beyond what these checks measured.