mcpbeat

llms.txt Checker - AI Readiness Audit MCP Server

io.github.apifymcpfactory-droid/llms-txt-checker
answering

llms.txt Checker - AI Readiness Audit is answering right now. Last checked 12 min ago. Last commit 20 Jul 2026.

Checks llms.txt, AI crawler access in robots.txt, and sitemap - with a 0-100 AI readiness score.

Uptime history 42 hours of history
42 hours agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
422 ms
Response time
average over 24h
0
Stars
last commit 20 Jul 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

run in your terminal
claude mcp add llms-txt-checker --transport http https://mcp.apify.com?tools=apifmcpfactory/llms-txt-checker
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "llms-txt-checker": {
      "url": "https://mcp.apify.com?tools=apifmcpfactory/llms-txt-checker"
    }
  }
}
~/.codex/config.toml
[mcp_servers.llms-txt-checker]
url = "https://mcp.apify.com?tools=apifmcpfactory/llms-txt-checker"
.cursor/mcp.json
{
  "mcpServers": {
    "llms-txt-checker": {
      "url": "https://mcp.apify.com?tools=apifmcpfactory/llms-txt-checker"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "llms-txt-checker": {
      "url": "https://mcp.apify.com?tools=apifmcpfactory/llms-txt-checker"
    }
  }
}

This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.

Endpoints

URLTransportStateLatencyChecked
https://mcp.apify.com?tools=apifmcpfactory/llms-txt-checker streamable-http needs key 402 ms 12 min ago

llms.txt Checker - AI Readiness Audit — questions

Answers built from our own checks of this server.

Why is there no tool list for llms.txt Checker - AI Readiness Audit?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is llms.txt Checker - AI Readiness Audit working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 422 ms. The bar chart above shows every period we have measured.
How do I connect llms.txt Checker - AI Readiness Audit?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own key or an OAuth login: it refuses anonymous clients.
Does llms.txt Checker - AI Readiness Audit need an API key?
Yes. Every time we knock, llms.txt Checker - AI Readiness Audit answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is llms.txt Checker - AI Readiness Audit?
It answers our handshake in 422 ms on average, which is faster than 30% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is llms.txt Checker - AI Readiness Audit open source?
Yes — 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.