Skip to main content
Glama
deenesjakoruzh
thedaviddias

MCP LLMS.txt Explorer

by thedaviddias
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

MCP LLMS.txt Проводник

значок кузнеца

Сервер Model Context Protocol для исследования веб-сайтов с файлами llms.txt. Этот сервер поможет вам обнаружить и проанализировать веб-сайты, реализующие стандарт llms.txt.

Функции

Ресурсы

  • Проверьте веб-сайты на наличие файлов llms.txt и llms-full.txt

  • Анализ и проверка содержимого файла llms.txt

  • Получите доступ к структурированным данным о соответствующих веб-сайтах

Инструменты

  • check_website - Проверка наличия на сайте файлов llms.txt

    • Принимает URL домена в качестве входных данных

    • Возвращает расположение файлов и статус проверки

  • list_websites - Список известных веб-сайтов с файлами llms.txt

    • Возвращает структурированные данные о соответствующих веб-сайтах

    • Поддерживает фильтрацию по типу файла (llms.txt/llms-full.txt)

Related MCP server: MCP LLMS-TXT Documentation Server

Разработка

Установить зависимости:

pnpm install

Сборка сервера:

pnpm run build

Для разработки с автоматической пересборкой:

pnpm run watch

Установка

Установка через Smithery

Чтобы автоматически установить mcp-llms-txt-explorer для Claude Desktop через Smithery :

npx -y @smithery/cli install @thedaviddias/mcp-llms-txt-explorer --client claude

Установка вручную

Чтобы использовать этот сервер:

# Clone the repository
git clone https://github.com/thedaviddias/mcp-llms-txt-explorer.git
cd mcp-llms-txt-explorer

# Install dependencies
pnpm install

# Build the server
pnpm run build

Конфигурация с Claude Desktop

Для использования с Claude Desktop добавьте конфигурацию сервера:

В MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json В Windows: %APPDATA%/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "llms-txt-explorer": {
      "command": "node",
      "args": ["/path/to/llms-txt-explorer/build/index.js"],
    }
  }
}

Для использования npx вы можете использовать:

{
  "mcpServers": {
    "llms-txt-explorer": {
      "command": "npx",
      "args": ["-y", "@thedaviddias/mcp-llms-txt-explorer"]
    }
  }
}

Отладка

Поскольку серверы MCP взаимодействуют через stdio, отладка может быть сложной. Мы рекомендуем использовать MCP Inspector , который доступен как пакетный скрипт:

pnpm run inspector

Инспектор предоставит URL-адрес для доступа к инструментам отладки в вашем браузере.

Лицензия

Данный проект лицензирован по лицензии MIT — подробности см. в файле LICENSE.

Available Tools

2 tools
check_websiteC

Check if a website has llms.txt files

ParametersJSON Schema
NameRequiredDescriptionDefault
urlYesURL of the website to check

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool checks for 'llms.txt files,' implying a read-only operation, but doesn't specify what 'check' entails (e.g., HTTP request details, error handling, or output format). For a tool with no annotations, this is a significant gap in transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, clear sentence with no wasted words. It's front-loaded with the core purpose and efficiently conveys the tool's function without unnecessary elaboration, making it highly concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., boolean result, file details, or error messages) or any behavioral aspects like rate limits or authentication needs. For a tool with no structured support, the description should provide more context to be fully helpful.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 100% description coverage, with the 'url' parameter fully documented. The description doesn't add any semantic details beyond the schema, such as URL format requirements or examples. Given the high schema coverage, the baseline score of 3 is appropriate, as the schema handles the parameter documentation adequately.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Check if a website has llms.txt files.' It specifies the verb ('check') and resource ('website'), making the action explicit. However, it doesn't differentiate from the sibling tool 'list_websites,' which likely serves a different function (listing vs. checking), so it doesn't reach the highest score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention the sibling tool 'list_websites' or any other context for usage, such as prerequisites or scenarios. This leaves the agent without direction on tool selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

list_websitesB

List known websites with llms.txt files

ParametersJSON Schema
NameRequiredDescriptionDefault
filter_llms_txtNoOnly show websites with llms.txt
filter_llms_full_txtNoOnly show websites with llms-full.txt

TDQS

B3.1/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions that the tool lists websites 'with llms.txt files' but doesn't describe what 'known websites' means, whether this is a read-only operation, what format the output takes, or any limitations (like pagination or rate limits). The description is minimal and lacks important behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise - a single sentence that directly states the tool's purpose. There's zero waste or unnecessary elaboration. It's appropriately sized for a simple listing tool with well-documented parameters.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple listing tool with 100% schema coverage but no annotations and no output schema, the description is adequate but has clear gaps. It explains what the tool does but doesn't provide context about what constitutes 'known websites' or what the output format will be. The description meets minimum viability but could be more complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents both parameters (filter_llms_txt and filter_llms_full_txt) with clear descriptions. The description doesn't add any parameter semantics beyond what's in the schema - it doesn't explain how these filters work together or their default behavior. Baseline 3 is appropriate when schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'List known websites with llms.txt files' specifies both the action (list) and resource (websites with llms.txt files). However, it doesn't explicitly differentiate from the sibling tool 'check_website', which likely serves a different purpose (possibly checking individual websites rather than listing them).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. There's no mention of the sibling tool 'check_website' or any context about when listing websites is appropriate versus checking individual ones. The description simply states what the tool does without usage context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 2 tool updates
    • First observedcheck_website
    • First observedlist_websites
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.1/5.0

Scored across 2 tools

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count2/5

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.

Completeness2/5

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.

Maintenance

ActivityInactive
ResponsivenessUnresponsive

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches