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 · TW-SEARCH-SEO.PANDA198271.WORKERS.DEV

檢查網站爬蟲設定、驗證爬蟲 IP、IndexNow 提交與 YouTube SEO 檢查。

+7 this week 81 Trust /100

Last scanned (13 hours ago)

Scores higher than 79% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Marketing and SEO

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 Security74
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 19 Nov 26 +7
    • Authorization: unverified → partial ▲ security
    • Tool “ai_crawler_list” changed its title: AI 與搜尋引擎爬蟲 User-Agent 名單 cosmetic
    • Tool “build_search_urls” changed its title: build_search_urls cosmetic
    • Tool “check_site_crawlers” changed its title: 檢查網站的 robots.txt、Sitemap、llms.txt cosmetic
    • Tool “generate_meta_tags” changed its title: generate_meta_tags cosmetic
    • Tool “generate_robots_txt” changed its title: 產生 robots.txt cosmetic
    • Tool “geo_citation_audit” changed its title: AEO/GEO 引用準備度健檢 cosmetic
    • Tool “indexnow_submit” changed its title: indexnow_submit cosmetic
    • Tool “search_engine_market_share” changed its title: 台灣與全球搜尋引擎市佔率 cosmetic
    • Tool “search_operators” changed its title: 搜尋指令 cosmetic
    • Tool “search_submit_guide” changed its title: search_submit_guide cosmetic
    • Tool “serp_preview” changed its title: 預覽 Google 搜尋結果標題與描述 cosmetic
    • Tool “test_robots_txt” changed its title: 依 RFC 9309 測試某個 User-Agent 能否抓取某路徑 cosmetic
    • Tool “verify_crawler_ip” changed its title: verify_crawler_ip cosmetic
    • Tool “youtube_seo_check” changed its title: 檢查 YouTube 章節時間碼 cosmetic
  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 7 Nov 26 0
    • Stability: 0.97 → pass security
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 5 Nov 26 0
    • Stability: 0.97 → pass security
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 21 Nov 2026 · Probed https://tw-search-seo.panda198271.workers.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=panda198271.workers.dev CN=YE1,O=Let's Encrypt,C=US 20 Nov 2026 18 Feb 2027 ECDSA 256 ECDSA-SHA384 698567de15a9ee5b0673e90061a4c5fb25e
SANs: *.panda198271.workers.dev, panda198271.workers.dev
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of tw-search-seo.panda198271.workers.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
workers.dev. No DS 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://tw-search-seo.panda198271.workers.dev/mcp Verified 200
http (plaintext) http://tw-search-seo.panda198271.workers.dev/mcp HTTPS enforced 302 https://penguindriver.com/connect
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.

Install

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

搜尋引擎與 AI 爬蟲工具箱 is a hosted endpoint at https://tw-search-seo.panda198271.workers.dev/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 · tw-search-seo.panda198271.workers.dev

# add to Claude Code
claude mcp add --transport http dev-workers-panda198271-tw-search-seo-search-seo 'https://tw-search-seo.panda198271.workers.dev/mcp'
Common questions

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

搜尋引擎與 AI 爬蟲工具箱 is an MCP server listed in the public MCP registry as dev.workers.panda198271.tw-search-seo/search-seo. 檢查網站爬蟲設定、驗證爬蟲 IP、IndexNow 提交與 YouTube SEO 檢查。 This page covers its hosted endpoint (https://tw-search-seo.panda198271.workers.dev/mcp).

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

搜尋引擎與 AI 爬蟲工具箱 scores 81 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 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the 搜尋引擎與 AI 爬蟲工具箱 MCP server?

VerifyMCP ran 13 checks on 搜尋引擎與 AI 爬蟲工具箱, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.