Home / MCP registry index / dev.workers.panda198271.tw-search-seo/search-seo

搜尋引擎與 AI 爬蟲工具箱

dev.workers.panda198271.tw-search-seo/search-seo in the official MCP registry. Endpoint https://tw-search-seo.panda198271.workers.dev/mcp.

The registry describes it as: 檢查網站爬蟲設定、驗證爬蟲 IP、IndexNow 提交與 YouTube SEO 檢查。

We read its 14 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Tools it advertises

build_search_urls search_operators generate_robots_txt test_robots_txt check_site_crawlers ai_crawler_list verify_crawler_ip serp_preview generate_meta_tags youtube_seo_check indexnow_submit search_engine_market_share search_submit_guide geo_citation_audit

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/dev-workers-panda198271-tw-search-seo-search-seo/badge.svg)](https://lazaretto.dev/mcp-registry/dev-workers-panda198271-tw-search-seo-search-seo)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.