MCP LLMS.txt Explorer
Related Servers
Alternatives to MCP LLMS.txt Explorer
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables checking whether a website has a usable llms.txt file and scoring it from 0 to 100.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to create, validate, and audit llms.txt files for websites, including checking against Google Lighthouse's Agentic Browsing requirements, via Streamable HTTP with no API key needed.5 npm2MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to extract, validate, and discover documentation from websites using llms.txt and install.md standards.14 npm34-
- AlicenseNot gradedqualityCmaintenanceEnables websites to expose a first-class interface for AI agents by providing read-only MCP tools like search_site and generating llms.txt discovery files.05MIT
- AlicenseBqualityFmaintenanceA server that analyzes website performance using Playwright and Lighthouse, allowing LLMs to perform web performance analysis through the Model Context Protocol.25MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables users to fetch and audit documentation from user-defined llms.txt index files. It provides tools to list documentation sources and retrieve content from specific URLs with built-in domain access controls for secure context retrieval.MIT
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: check_website verifies the presence of llms.txt files on a specific website, while list_websites retrieves a list of known websites that already have such files. There is no overlap in functionality, making it easy for an agent to select the appropriate tool based on the task.
Both tools follow a consistent verb_noun pattern (check_website and list_websites), using snake_case and clear action verbs. This uniformity makes the tool set predictable and easy to understand, with no deviations in naming conventions.
With only two tools, the server feels under-scoped for exploring llms.txt files. While the tools cover basic checking and listing, there are likely missing operations such as fetching file contents, updating lists, or analyzing data, which limits the server's utility for comprehensive exploration.
The tool set is severely incomplete for an 'Explorer' server. It lacks essential operations like retrieving the actual llms.txt content, validating file structure, searching within files, or managing the list of websites. This creates significant gaps that will hinder agents from performing meaningful exploration tasks.