Wake site readiness
Server Details
How an AI agent sees a public website: robots, llms.txt, sitemap, agent card, scored. No key needed.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-06-18
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 3 tools
The three tools map to entirely separate jobs: informational overview, read-only site probe, and account creation. An agent can pick the right one from the name alone with no overlap.
All tools share a uniform wake_ prefix and snake_case, with clear action-oriented suffixes (about, check_site, signup). The pattern is predictable and readable.
Three tools is thin but defensible for a narrow onboarding surface (explain, audit, sign up); each earns its place. It could use at least one more tool to read results, but nothing here is redundant.
The surface covers discovery, an unauthenticated audit, and signup, but the signup description promises you can 'read the desk over MCP' and there is no tool to fetch desk data, scores history, or manage the account. An agent hitting the promised pay-off hits a dead end.
Available Tools
3 toolswake_aboutWhat Wake isBRead-onlyInspect
One paragraph on Wake (agent experience optimization and agent engine optimization for a website), with links to docs, API, MCP and signup.
Inputs: no named parameters.
wake_check_siteCheck a site's agent readinessARead-onlyInspect
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.
Inputs: host.
wake_signupOpen a Wake desk for a websiteARead-onlyInspect
Create the account and the desk for a website you own and get an API key back, so you can install the tracker and read the desk over MCP. Needs site, email and terms_accepted: true (terms: /wake/docs/terms.md, privacy: /wake/docs/privacy.md). One desk per host; rate-limited.
Inputs: site, email, terms_accepted.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
How an AI agent sees a public website: robots, llms.txt, sitemap, agent card, scored fixes. Host in.
Scan any public website and see how ready it is for AI agents and AI search, explained plainly.
Scores any public website on how usable it is by AI agents, with per-check evidence.
Is this website visible to AI agents? Robots, llms.txt, sitemap, extraction, then placement.
Related MCP Servers
- AlicenseAqualityCmaintenanceEnables AI agents to check whether a public website is crawlable, understandable, and ready for AI search workflows through local-only audits of robots.txt, sitemaps, metadata, and llms.txt.373 npm2MIT
- AlicenseAqualityDmaintenanceAudits AI-bot visibility: robots.txt per-bot for 22 AI user-agents (GPTBot/ClaudeBot/PerplexityBot/etc), Cloudflare flags, JSON-LD, sitemap, llms.txt, SPA shell, plus cross-model brand mentions via Perplexity + OpenRouter. 0-100 score. SSRF-guarded, spend-capped.41MIT
- AlicenseAqualityCmaintenanceEnables AI agents to audit and improve a site's visibility in AI search by checking robots.txt against 17 major AI crawlers, detecting llms.txt, and returning a 0-100 visibility score with per-crawler verdicts; it also lists known AI crawlers and their purposes.2MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to scan any website for agent-readiness and generate the necessary artifacts (llms.txt, WebMCP scaffold, structured data) to make it agent-ready.5 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.