Wake site readiness MCP Server

by sadri-dridi Your server? Claim it

answering

Wake site readiness is answering right now. Last checked 1 min ago. It exposes 2 tools.

How an AI agent sees a public website: robots, llms.txt, sitemap, agent card, scored fixes. Host in.

Uptime history 70 hours of history

70 hours agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

362 ms

Response time

average over 24h

open, no key

Access

streamable-http

Nothing serious here today

Today is the operative word: we check Wake site readiness every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add wake-site-readiness --transport http https://agent-observatory-desk-production.up.railway.app/api/wake/v1/public/mcp

Settings → Connectors → Add custom connector, then paste this address

https://agent-observatory-desk-production.up.railway.app/api/wake/v1/public/mcp

~/.codex/config.toml

[mcp_servers.wake-site-readiness]
url = "https://agent-observatory-desk-production.up.railway.app/api/wake/v1/public/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "wake-site-readiness": {
      "url": "https://agent-observatory-desk-production.up.railway.app/api/wake/v1/public/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "wake-site-readiness": {
      "type": "http",
      "url": "https://agent-observatory-desk-production.up.railway.app/api/wake/v1/public/mcp"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

wake

wake_about

One paragraph on Wake (agent experience observability + agent engine optimisation for a website), with links to docs, API, MCP and signup.

wake_check_site

Probe a public hostname the way an AI agent sees it (homepage, robots.txt, llms.txt, sitemap, agent card) and return scores out of 100 with concrete recommendations and publish-ready llms.txt / robots files. Input is a hostname only; the probe keeps structural signals, never page bodies. No account needed.

Endpoints

URL	Transport	State	Latency	Checked
https://agent-observatory-desk-production.up.railway.app/api/wake/v1/public/mcp	streamable-http	answering	333 ms	1 min ago

Alternatives to Wake site readiness

same job, measured the same way

Agent-readiness check

by wondaverse

Checks a website for AI agents: robots.txt, llms.txt, MCP, A2A. Ranked fixes, text to paste.

1 tools answering

llms.txt Readiness

by sadri-dridi

Does a site publish llms.txt, robots permissions and a sitemap agents can use? Bounded check.

31 tools answering

AI Site Scorer

by minglesai

Check website AI-readiness: Schema.org, llms.txt, E-E-A-T, robots.txt. Works in Cursor & Claude.

5 tools answering

llms.txt Checker - AI Readiness Audit

by apifymcpfactory-droid

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

answering

Agent Ready Website Check

by sadri-dridi

Check whether a website is readable by AI agents: robots, llms.txt, sitemap, HTML. Bounded.

31 tools answering

Agent Crawl Readiness

by sadri-dridi

Bounded crawl-readiness check for agent access: robots.txt, sitemap.xml, llms.txt, homepage.

31 tools answering

AgenticWebScore

by agenticwebscore

Scan a public website for AI agent readiness: 60 checks, a score, and the evidence for each.

4 tools answering

Agent Readiness Auditor

by asish-singh

Audits any website for AI agent readiness and safety, scoring prompt injection risk and llms.txt.

94 installs/wk local only

Wake site readiness — questions

Answers built from our own checks of this server.

What can Wake site readiness do?

It exposes 2 tools, read directly from the server on our last check. Among them: wake_about, wake_check_site. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Wake site readiness working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 362 ms. The bar chart above shows every period we have measured.

How do I connect Wake site readiness?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Wake site readiness need an API key?

No. Wake site readiness completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Wake site readiness?

It answers our handshake in 362 ms on average, which is faster than 37% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.