Remote MCP · Endpoint

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

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

UpLast checked 8 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
687 ms
Tools exposed
14 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
搜尋引擎與 AI 爬蟲工具箱:搜尋指令、爬蟲驗證、收錄與 AEO 健檢。台灣繁體中文 MCP 工具。
Listing
From the official MCP registry (active).
Recent checks of 搜尋引擎與 AI 爬蟲工具箱
CheckedResultHandshake
8 hours agoHandshake completed687 ms
10 days agoHandshake completed85 ms
11 days agoHandshake completed131 ms
11 days agoHandshake completed76 ms
13 days agoHandshake completed54 ms
15 days agoHandshake completed61 ms
15 days agoHandshake completed65 ms
16 days agoHandshake completed155 ms
17 days agoHandshake completed54 ms
19 days agoHandshake completed112 ms
22 days agoHandshake completed81 ms
24 days agoHandshake completed58 ms
26 days agoHandshake completed80 ms
29 days agoHandshake completed50 ms

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

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 搜尋引擎與 AI 爬蟲工具箱 and makes no claim about it beyond what these checks measured.