mcpbeat Sign in

Agent Ready Website Audit MCP Server

answering

Agent Ready Website Audit is answering right now. Last checked 7 min ago. It exposes 12 tools.

SEO and AI search audit for any website: technical SEO, schema, AI crawler access and llms.txt.

Uptime history 23 hours of history
23 hours agonow
100.0%
Uptime 24h
85 of 85 checks
12
Tools
read from the server
840 ms
Response time
average over 24h
open, no key
Access
streamable-http

Nothing serious here today

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

Three servers free · no card

Connect this server

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

run in your terminal
claude mcp add agent-ready-mcp --transport http https://mcp.workpods.ai/mcp
Settings → Connectors → Add custom connector, then paste this address
https://mcp.workpods.ai/mcp
~/.codex/config.toml
[mcp_servers.agent-ready-mcp]
url = "https://mcp.workpods.ai/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "agent-ready-mcp": {
      "url": "https://mcp.workpods.ai/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "agent-ready-mcp": {
      "type": "http",
      "url": "https://mcp.workpods.ai/mcp"
    }
  }
}

Available tools 12

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

draft
draft_llms_txt
Drafts a starter llms.txt (llmstxt.org) for a site from its home page and sitemap: an H1 with the site name, its description as the summary, and links to its main pages grouped by section, titled from the pages where they were fetched. Use it when the site has no llms.txt or a broken one. result has llmsTxt (the file text), saveAs (where it goes), links, sitemapUrls and existingLlmsTxt (the outcome of the current one). The person should edit it before publishing. Returns JSON: summary (one sentence), reportUrl (a shareable report page for the person, kept 30 days; null for tools that keep none) and result (the details below). Errors come back as one plain sentence. Recorded: the checked domain and path (never the query string), the tool, which checks failed and the app name; never an IP address or page text.
draft_robots_txt_for_ai_crawlers
Drafts robots.txt groups for the AI crawlers Agent Ready tracks, and a Content-Signal line, from what the site owner wants: crawlers that index for AI search, crawlers that fetch a page because a user asked, and crawlers that collect training data, each allowed or blocked, with per-crawler overrides. It fetches nothing. Use it after check_robots_sitemap_llms_txt or check_ai_crawler_access shows crawlers blocked or allowed against the owner's wishes. result has robotsTxt (the lines to merge), contentSignal, decisions (each crawler with its role and choice) and unknownOverrides (tokens not recognised). Returns JSON: summary (one sentence), reportUrl (a shareable report page for the person, kept 30 days; null for tools that keep none) and result (the details below). Errors come back as one plain sentence.
draft_schema_markup
Drafts schema markup (schema.org JSON-LD structured data) for a page: Organization, WebSite, FAQPage (questions read from headings that end in a question mark, with the text under them) or LocalBusiness. Values the person gives win over values read from the page. Use it when seo_audit_page reports missing or incomplete structured data. result has jsonLd, scriptTag (ready to paste into the <head>), filledFrom (each field: input or page), missing (fields to fill in) and existingTypes (schema types the page already declares). Returns JSON: summary (one sentence), reportUrl (a shareable report page for the person, kept 30 days; null for tools that keep none) and result (the details below). Errors come back as one plain sentence. Recorded: the checked domain and path (never the query string), the tool, which checks failed and the app name; never an IP address or page text.
agent
check_agent_readiness
Checks whether AI agents can use a page and its site: labelled forms and buttons, declared WebMCP tools, a Markdown version (content negotiation or a Link header), the agent files and MCP server cards under /.well-known, and whether the domain has an MCP server listed in the official MCP Registry. Use it when the person asks whether agents can complete tasks on the site or find its MCP server. result has checks (the agent checks with status and summary), webMcpTools, markdownVersion, agentFiles and mcpRegistry (listings by name, website or endpoint; null when the registry could not be read, an empty list when nothing is listed). Registry lookups are cached 6 hours. These are deterministic checks of public pages fetched by Agent Ready Website Audit, with no AI model and no account. They do not cover rankings, keyword volumes, backlinks or how AI answers mention the brand. Returns JSON: summary (one sentence), reportUrl (a shareable report page for the person, kept 30 days; null for tools that keep none) and result (the details below). Errors come back as one plain sentence. Recorded: the checked domain and path (never the query string), the tool, which checks failed and the app name; never an IP address or page text.
compare
compare_with_competitor_page
Runs the seo_audit_page checks on the person's page and a competitor's page that targets the same search or task, and lists the checks where they differ. Use it when the person asks why a competitor ranks or shows up in AI answers and they do not. result has mine and theirs (status, scores, problem count, word count, headings, schema types) and differences (check id with each side's status and summary). These are deterministic checks of public pages fetched by Agent Ready Website Audit, with no AI model and no account. They do not cover rankings, keyword volumes, backlinks or how AI answers mention the brand. Returns JSON: summary (one sentence), reportUrl (a shareable report page for the person, kept 30 days; null for tools that keep none) and result (the details below). Errors come back as one plain sentence. Recorded: the checked domain and path (never the query string), the tool, which checks failed and the app name; never an IP address or page text.
crawler
check_ai_crawler_access
Checks whether AI crawlers such as GPTBot, ClaudeBot and PerplexityBot may read one page, from robots.txt, the robots meta tags (including ones naming the crawler), the X-Robots-Tag header and the HTTP status. Use it when the person asks whether ChatGPT, Claude, Perplexity or Google can see a page, or whether blocked crawlers explain why the site is missing from AI answers. result.bots lists each crawler with verdict: readable, readable_not_for_index (it may fetch the page but is asked not to index it), blocked_by_robots_txt or page_unavailable, plus robotsTxtAllows and the pageDirectives found. Firewalls that block crawlers by user agent or IP are not visible from here. These are deterministic checks of public pages fetched by Agent Ready Website Audit, with no AI model and no account. They do not cover rankings, keyword volumes, backlinks or how AI answers mention the brand. Returns JSON: summary (one sentence), reportUrl (a shareable report page for the person, kept 30 days; null for tools that keep none) and result (the details below). Errors come back as one plain sentence. Recorded: the checked domain and path (never the query string), the tool, which checks failed and the app name; never an IP address or page text.
local
check_local_seo_details
Local SEO check of a business's website: whether the page states the business name, address and phone the person gives (NAP consistency), and whether it has LocalBusiness schema, click-to-call links and an embedded Google map. Use it for local SEO questions about a shop, clinic, restaurant or office's website. result has name, address and phone, each with status match, mismatch, not_found or profile_missing (no value given) and what the site states, localSchema (types and missing fields; null when there is none), telLinks and embeddedMap. It does not read the Google Business Profile itself. These are deterministic checks of public pages fetched by Agent Ready Website Audit, with no AI model and no account. They do not cover rankings, keyword volumes, backlinks or how AI answers mention the brand. Returns JSON: summary (one sentence), reportUrl (a shareable report page for the person, kept 30 days; null for tools that keep none) and result (the details below). Errors come back as one plain sentence. Recorded: the checked domain and path (never the query string), the tool, which checks failed and the app name; never an IP address or page text.
request
request_full_audit
Files a request for a full WorkPods audit of a site: how AI answers (ChatGPT, Gemini, Perplexity, Google AI Overviews) mention the brand and its competitors, search rankings and a prioritised fix list, done by WorkPods with paid data. Use it only when the person asks for it and gives their own work email. There is no charge. A WorkPods operator reviews the request and emails the report to that address within 3 working days. result has requested, domain and next (what to tell the person). The email goes to WorkPods and is not stored by this service.
robots
check_robots_sitemap_llms_txt
Checks a site's robots.txt, sitemaps and llms.txt: robots.txt with the verdict for each AI crawler (GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-User, PerplexityBot, Google-Extended and more), Content-Signal lines, the sitemaps, llms.txt, the agent files under /.well-known (AI catalog, MCP server cards, A2A agent card) and whether the home page has a Markdown version. Use it to see whether AI crawlers may read the site, whether its sitemap and llms.txt are in place, and what it offers agents. Only the origin of the URL is used. result has robotsTxt (url, status, contentSignals), aiCrawlers (token, operator, role, allowed), sitemaps (URL count, a sample, files), agentFiles (each with outcome ok, not_found, blocked or failed), markdownVersion and findings. A status of null means the site gave no answer. Cached for 1 hour. These are deterministic checks of public pages fetched by Agent Ready Website Audit, with no AI model and no account. They do not cover rankings, keyword volumes, backlinks or how AI answers mention the brand. Returns JSON: summary (one sentence), reportUrl (a shareable report page for the person, kept 30 days; null for tools that keep none) and result (the details below). Errors come back as one plain sentence. Recorded: the checked domain and path (never the query string), the tool, which checks failed and the app name; never an IP address or page text.
seo
seo_audit_page
SEO audit of one web page, covering technical SEO and AI search readiness: how search engines, AI answer engines (ChatGPT, Perplexity, Google AI Overviews) and AI agents read it. It checks indexing (status, robots, canonical), title and meta description, headings and copy, schema markup (JSON-LD), links, image alt text and AI readiness. Use it when the person asks for an SEO or website audit of a page, how a page does in search or AI answers, or what to fix first. result has url (where the page landed), status, scores (passed and judged checks per layer: seo, geo, axo), problems (each with check id, status fail or partial, severity, a one-line summary and evidence), passed and notApplicable (check ids). Results are cached for 15 minutes. These are deterministic checks of public pages fetched by Agent Ready Website Audit, with no AI model and no account. They do not cover rankings, keyword volumes, backlinks or how AI answers mention the brand. Returns JSON: summary (one sentence), reportUrl (a shareable report page for the person, kept 30 days; null for tools that keep none) and result (the details below). Errors come back as one plain sentence. Recorded: the checked domain and path (never the query string), the tool, which checks failed and the app name; never an IP address or page text.
site
get_site_crawl
Reads a crawl started by start_site_crawl. While it runs, result has status (queued or running) and pagesDone; call again in 20 to 30 seconds. Once done, result has the site-wide findings and the crawled pages with their problems, 10 pages per call: pass nextCursor back as cursor for the next 10; nextCursor is null on the last page. A failed crawl has status failed and error. An unknown or expired job id is an error. Returns JSON: summary (one sentence), reportUrl (a shareable report page for the person, kept 30 days; null for tools that keep none) and result (the details below). Errors come back as one plain sentence.
start
start_site_crawl
Starts a site-wide SEO crawl of up to 50 pages, in the background, for the problems one page cannot show: broken links, duplicate titles and descriptions, orphan and deep pages, noindex and sitemap mismatches and soft 404s. Use it when the person wants the whole site checked. It returns at once with jobId; call get_site_crawl with it every 20 to 30 seconds until status is done. Crawls honour robots.txt and pause between pages, so 50 pages take a few minutes. Results are kept 24 hours. These are deterministic checks of public pages fetched by Agent Ready Website Audit, with no AI model and no account. They do not cover rankings, keyword volumes, backlinks or how AI answers mention the brand. Recorded: the checked domain and path (never the query string), the tool, which checks failed and the app name; never an IP address or page text.

Endpoints

URLTransportStateLatencyChecked
https://mcp.workpods.ai/mcp streamable-http answering 804 ms 7 min ago

Alternatives to Agent Ready Website Audit

same job, measured the same way
Geolint
by iliasabk

ESLint for AI search: audits AI-crawler access, llms.txt, schema and citability.

95 installs/wk local only
Errandkit SEO & AI Search Readiness Audit
by errandkit

Audit pages for SEO and AI search: scores, fixes, AI crawler access, llms.txt. Pay per use.

answering
SEO Records
by seorecords

SEO check of any website and AI crawler access test (access pass), and the full Audit.

5 tools answering
GEO Inspector
by bigsupe55

Inspect a site's AI-search readiness: AI crawler access, llms.txt, schema markup, meta directives

52 installs/wk local only
AEO Auditor — AI Search & Agent Readiness Engine
by aeoauditing

Live AEO, GEO, JSON-LD Schema, robots.txt AI crawler, and Agent Readiness diagnostic auditor.

3 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
Momentic
by momenticmarketing

Free SEO, GEO, and AEO audits: analyze any page or domain, AI-crawler access, agent readiness.

12 tools answering
Alice
by tranx

Audit any site's AI visibility from your assistant: crawler access, rendering, and schema.

2 tools answering

Agent Ready Website Audit — questions

Answers built from our own checks of this server.

What can Agent Ready Website Audit do?
It exposes 12 tools, read directly from the server on our last check. Among them: check_agent_readiness, check_ai_crawler_access, check_local_seo_details, check_robots_sitemap_llms_txt, compare_with_competitor_page, draft_llms_txt and 6 more. 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 Agent Ready Website Audit working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 85 of 85 checks got a reply (100.0%), average response time 840 ms. The bar chart above shows every period we have measured.
How do I connect Agent Ready Website Audit?
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 Agent Ready Website Audit need an API key?
No. Agent Ready Website Audit completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 12 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Agent Ready Website Audit?
It answers our handshake in 840 ms on average, which is faster than 8% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.