Summary
Checking the file rather than assuming it is there.
llms.txt is easy to publish and easy to get subtly wrong. This answers both questions an implementer has — does this domain have one, and does it parse — and the list of known compliant sites supplies working examples to measure yours against.
What it is
A server for the llms.txt standard. Give it a domain and it checks for llms.txt and llms-full.txt, reporting where the files are and whether they validate; it also lists known compliant websites as structured data, filterable by which of the two files they publish.
What you get
- A domain checked for llms.txt and llms-full.txt, with file locations and validation status (check_website)
- Known websites publishing llms.txt returned as structured data (list_websites)
- That list filtered by file type — llms.txt or llms-full.txt
- llms.txt contents parsed and validated rather than merely fetched
- Compliant sites also exposed as resources
Requirements
Node, run through npx or a pnpm build of the repository; Smithery installs it in one command. No account and no key.
Setup effort
One command — npx -y @thedaviddias/mcp-llms-txt-explorer