Remote MCP · Endpoint

搜尋引擎與 AI 爬蟲工具箱 MCP server

No. 搜尋引擎與 AI 爬蟲工具箱 answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://seo.penguindriver.com/mcp

The last check completed an MCP handshake.

Registry name
com.penguindriver/seo
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
80 ms
Tools exposed
14 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
搜尋引擎與 AI 爬蟲工具箱：搜尋指令、爬蟲驗證、收錄與 AEO 健檢。台灣繁體中文 MCP 工具。
Website
https://seo.penguindriver.com/
Listing
From the official MCP registry (active).
Recent checks of 搜尋引擎與 AI 爬蟲工具箱
CheckedResultHandshake
7 hours agoHandshake completed80 ms
2 days agoHandshake completed50 ms
4 days agoHandshake completed103 ms
6 days agoHandshake completed55 ms
8 days agoHandshake completed81 ms
10 days agoHandshake completed76 ms
12 days agoHandshake completed60 ms
13 days agoHandshake completed84 ms
14 days agoHandshake completed76 ms
15 days agoHandshake completed64 ms
18 days agoHandshake completed161 ms
20 days agoHandshake completed69 ms
21 days agoHandshake completed76 ms
23 days agoHandshake completed52 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 搜尋引擎與 AI 爬蟲工具箱 and makes no claim about it beyond what these checks measured.