Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

搜尋引擎與 AI 爬蟲工具箱

REMOTE · SEO.PENGUINDRIVER.COM · SCANNED SEP 29

搜尋引擎與 AI 爬蟲工具箱:搜尋指令、爬蟲驗證、收錄與 AEO 健檢。台灣繁體中文 MCP 工具。

56 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security46
Transport & Reachability100
Schema Quality & AI Usability67
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1033 tokens (~73/item across 14 items; 14 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
  • Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the 搜尋引擎與 AI 爬蟲工具箱 MCP server?

搜尋引擎與 AI 爬蟲工具箱 is a hosted endpoint at https://seo.penguindriver.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · seo.penguindriver.com

# add to Claude Code
claude mcp add --transport http com-penguindriver-seo 'https://seo.penguindriver.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-penguindriver-seo": {
      "url": "https://seo.penguindriver.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-penguindriver-seo": {
      "type": "http",
      "url": "https://seo.penguindriver.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-penguindriver-seo]
url = "https://seo.penguindriver.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-penguindriver-seo": {
      "type": "remote",
      "url": "https://seo.penguindriver.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-penguindriver-seo --url 'https://seo.penguindriver.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-penguindriver-seo:
    url: "https://seo.penguindriver.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-penguindriver-seo": {
      "Transport": "http",
      "Url": "https://seo.penguindriver.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-penguindriver-seo -t streamable-http -u 'https://seo.penguindriver.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-penguindriver-seo": {
      "type": "http",
      "url": "https://seo.penguindriver.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 29 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 28 Sept 26 56

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 29 Sept 2026 · Probed https://seo.penguindriver.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=penguindriver.com CN=WE1,O=Google Trust Services,C=US 27 Sept 2026 26 Dec 2026 ECDSA 256 ECDSA-SHA256 8030e46df50d9b5d13ac7356454163be
SANs: penguindriver.com, seo.penguindriver.com, *.seo.penguindriver.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of seo.penguindriver.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
penguindriver.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://seo.penguindriver.com/mcp Verified 200
http (plaintext) http://seo.penguindriver.com/mcp Inconclusive 405
MCP tools · 14 exposed · ~951 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
ai_crawler_list ~49

AI 與搜尋引擎爬蟲 User-Agent 名單:業者、用途、是否遵守 robots.txt、官方 IP 清單。

NameTypeReqDescription
typestring––

No output schema declared.

No examples provided.

build_search_urls ~97

一次產生 Google、Bing、Yahoo 奇摩、百度、YouTube 的進階搜尋網址(關鍵字、完全符合、排除字、限定網站、檔案類型、時間)。

NameTypeReqDescription
exactstring––
excludestring––
filetypestring––
qstringyes–
sitestring––
timestring––

No output schema declared.

No examples provided.

check_site_crawlers ~62

檢查網站的 robots.txt、Sitemap、llms.txt,以及 Googlebot、bingbot、GPTBot、ClaudeBot、PerplexityBot 等是否被封鎖,附改善建議。

NameTypeReqDescription
urlstringyes–

No output schema declared.

No examples provided.

generate_meta_tags ~72

產生 title、description、canonical、Open Graph、Twitter 卡片與 JSON-LD。

NameTypeReqDescription
descriptionstring––
imagestring––
site_namestring––
titlestringyes–
typestring––
urlstring––

No output schema declared.

No examples provided.

generate_robots_txt ~72

產生 robots.txt:allow_all、block_training(封鎖 AI 訓練保留搜尋)、block_all_ai、block_all,可加不抓路徑與 Sitemap。

NameTypeReqDescription
disallowstring––
modestring––
sitemapstring––

No output schema declared.

No examples provided.

geo_citation_audit ~117

AEO/GEO 引用準備度健檢:檢查網頁能否被 ChatGPT、Perplexity、Google AI 摘要等答案引擎引用(爬蟲可讀、開頭直接回答、問句標題、表格、外部與權威來源、更新日期、JSON-LD citation、llms.txt、Markdown 版、Content-Digest),給分數與優先修正清單。

NameTypeReqDescription
urlstringyes–

No output schema declared.

No examples provided.

indexnow_submit ~76

用 IndexNow 通知 Bing、Yandex、Naver 等搜尋引擎網址已更新(需先在網站放金鑰檔,最多 100 個網址)。

NameTypeReqDescription
hoststringyes–
keystringyes–
keyLocationstring––
urlsarrayyes–

No output schema declared.

No examples provided.

search_engine_market_share ~38

台灣與全球搜尋引擎市佔率(Google、Bing、Yahoo、百度等,StatCounter 最新月份)。

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_operators ~57

搜尋指令(site:、filetype:、intitle:、before: 等)在 Google、Bing、Yahoo、百度的支援對照與已失效指令。

NameTypeReqDescription
enginestring––

No output schema declared.

No examples provided.

search_submit_guide ~39

如何讓 Google、Bing、Yahoo、百度、YouTube、AI 搜尋收錄網站:工具、步驟與 API。

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

serp_preview ~55

預覽 Google 搜尋結果標題與描述,估算中文像素寬度與截斷位置。

NameTypeReqDescription
descriptionstring––
titlestringyes–
urlstring––

No output schema declared.

No examples provided.

test_robots_txt ~54

依 RFC 9309 測試某個 User-Agent 能否抓取某路徑。

NameTypeReqDescription
pathstring––
robotsstringyes–
user_agentstringyes–

No output schema declared.

No examples provided.

verify_crawler_ip ~67

驗證 IP 是否真的來自 Googlebot、bingbot、GPTBot、ClaudeBot、PerplexityBot、Applebot、Baiduspider 等(官方 IP 清單+反查 DNS)。

NameTypeReqDescription
botstring––
ipstringyes–

No output schema declared.

No examples provided.

youtube_seo_check ~96

檢查 YouTube 章節時間碼(0:00 起、至少 3 段、每段 10 秒)與標題、說明、標籤、主題標籤數量上限。

NameTypeReqDescription
chaptersstring––
descriptionstring––
durationstring––
tagsstring––
titlestring––

No output schema declared.

No examples provided.

Common questions

What is the 搜尋引擎與 AI 爬蟲工具箱 MCP server?

搜尋引擎與 AI 爬蟲工具箱 is an MCP server listed in the public MCP registry as com.penguindriver/seo. 搜尋引擎與 AI 爬蟲工具箱:搜尋指令、爬蟲驗證、收錄與 AEO 健檢。台灣繁體中文 MCP 工具。 This page covers its hosted endpoint (https://seo.penguindriver.com/mcp).

Is the 搜尋引擎與 AI 爬蟲工具箱 MCP server safe to use?

搜尋引擎與 AI 爬蟲工具箱 scores 56 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the 搜尋引擎與 AI 爬蟲工具箱 MCP server expose?

搜尋引擎與 AI 爬蟲工具箱 exposes 14 tools: build_search_urls, search_operators, generate_robots_txt, test_robots_txt, check_site_crawlers, and 9 more. Their descriptions and schemas cost roughly 951 tokens of context every time the server is loaded.

Does the 搜尋引擎與 AI 爬蟲工具箱 MCP server require authentication?

No. We connected to 搜尋引擎與 AI 爬蟲工具箱 without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the 搜尋引擎與 AI 爬蟲工具箱 MCP server still maintained?

搜尋引擎與 AI 爬蟲工具箱 is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.