Remote MCP · Endpoint

二行程經典車資料庫 MCP server

No. 二行程經典車資料庫 answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://twostroke.penguindriver.com/mcp

The last check completed an MCP handshake.

Registry name
com.penguindriver/twostroke
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
58 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
二行程經典車資料庫:經典二行程機車規格、零件與保養。台灣繁體中文 MCP 工具。
Listing
From the official MCP registry (active).
Recent checks of 二行程經典車資料庫
CheckedResultHandshake
1 hour agoHandshake completed58 ms
2 days agoHandshake completed78 ms
4 days agoHandshake completed97 ms
6 days agoHandshake completed247 ms
8 days agoHandshake completed51 ms
10 days agoHandshake completed76 ms
12 days agoHandshake completed63 ms
14 days agoHandshake completed62 ms
15 days agoHandshake completed122 ms
16 days agoHandshake completed57 ms
17 days agoHandshake completed73 ms
20 days agoHandshake completed76 ms
22 days agoHandshake completed32 ms
23 days agoHandshake completed316 ms
25 days agoHandshake completed47 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.