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.

llms.txt 檢查工具

REMOTE · LLMS-CHECK.PANDA198271.WORKERS.DEV

檢查網站 llms.txt 與 AI 爬蟲 robots.txt 設定,並自動產生 llms.txt。

+6 this week 82 Trust /100

Last scanned (13 hours ago)

Scores higher than 81% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Search and Retrieval

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 Usability71
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 256 tokens (~64/item across 4 items; 4 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 Coverage75
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 25% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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 +6
    • Authorization: unverified → partial ▲ security
    • Tool “check_ai_crawler_access” changed its title: 讀取網站 robots.txt cosmetic
    • Tool “check_llms_txt” changed its title: 檢查一個網站對 AI 的友善程度 cosmetic
    • Tool “generate_llms_txt” changed its title: 讀取網站首頁與 sitemap cosmetic
    • Tool “validate_llms_txt” changed its title: 驗證一段 llms.txt 內容是否符合格式 cosmetic
  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 9 Nov 26 +1
    • Stability: 0.97 → pass security
  • 8 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 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 +1
    • Stability: 0.97 → pass security
  • 4 Nov 26 −1
    • Stability: pass → 0.97 functional
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://llms-check.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 llms-check.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://llms-check.panda198271.workers.dev/mcp Verified 200
http (plaintext) http://llms-check.panda198271.workers.dev/mcp HTTPS enforced 302 https://penguindriver.com/connect
MCP tools · 4 exposed · ~226 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
check_ai_crawler_access ~66

讀取網站 robots.txt,回報 GPTBot、ChatGPT-User、ClaudeBot、Claude-User、PerplexityBot 等 13 種 AI 爬蟲是被允許還是封鎖。

NameTypeReqDescription
urlstringyes–

No output schema declared.

No examples provided.

check_llms_txt ~84

檢查一個網站對 AI 的友善程度:llms.txt 是否存在與格式問題、llms-full.txt、Markdown 頁面、robots.txt 對各 AI 爬蟲的設定、sitemap,回傳 0–100 分與改善建議。

NameTypeReqDescription
urlstringyes網站網址或網域

No output schema declared.

No examples provided.

generate_llms_txt ~34

讀取網站首頁與 sitemap,自動產生 llms.txt 草稿。

NameTypeReqDescription
urlstringyes–

No output schema declared.

No examples provided.

validate_llms_txt ~42

驗證一段 llms.txt 內容是否符合格式(H1、摘要、分區、連結)。

NameTypeReqDescription
contentstringyes–

No output schema declared.

No examples provided.

Install

How do I install the llms.txt 檢查工具 MCP server?

llms.txt 檢查工具 is a hosted endpoint at https://llms-check.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 · llms-check.panda198271.workers.dev

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

What is the llms.txt 檢查工具 MCP server?

llms.txt 檢查工具 is an MCP server listed in the public MCP registry as dev.workers.panda198271.llms-check/llms-check. 檢查網站 llms.txt 與 AI 爬蟲 robots.txt 設定,並自動產生 llms.txt。 This page covers its hosted endpoint (https://llms-check.panda198271.workers.dev/mcp).

Is the llms.txt 檢查工具 MCP server safe to use?

llms.txt 檢查工具 scores 82 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 llms.txt 檢查工具 MCP server expose?

llms.txt 檢查工具 exposes 4 tools: check_llms_txt, check_ai_crawler_access, generate_llms_txt, validate_llms_txt. Their descriptions and schemas cost roughly 226 tokens of context every time the server is loaded.

Does the llms.txt 檢查工具 MCP server require authentication?

No. We connected to llms.txt 檢查工具 without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the llms.txt 檢查工具 MCP server still maintained?

llms.txt 檢查工具 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 llms.txt 檢查工具 MCP server?

VerifyMCP ran 13 checks on llms.txt 檢查工具, 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.