Skip to content

Agent Ready Website Audit MCP server

ai.workpods/agent-ready-mcpworkpods.aistreamable-httpv1.0.1Scanned

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

13 tools: 12 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 12 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 12
  • Can send data out · 9
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

12 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Agent Ready Website Audit MCP server can do

The Agent Ready Website Audit MCP server is published by workpods.ai, a domain the MCP Registry verified. It has 13 tools. It can create or change data (12 tools: seo_audit_page, check_robots_sitemap_llms_txt, check_ai_crawler_access, check_agent_readiness and 8 more), but cannot delete data. 1 tool only reads.

12 tools bring in text other people can write (seo_audit_page, check_robots_sitemap_llms_txt, check_ai_crawler_access and 9 more); 9 tools can send data out of your system (seo_audit_page, check_robots_sitemap_llms_txt, check_ai_crawler_access and 6 more).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 21, 2026, version 1.0.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

13 tools

Changes things 12Claude Code: ask
  • check_agent_readinessChecks 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 …Reads text others writeCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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), result (the details below), resultId and reportUrl (null). The check saves nothing. When the person asks for a link to open or share later, pass resultId to share_report within an hour. 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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
    • title: Check AI agent readiness
  • check_ai_crawler_accessChecks 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-Ta…Reads text others writeCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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), result (the details below), resultId and reportUrl (null). The check saves nothing. When the person asks for a link to open or share later, pass resultId to share_report within an hour. 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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
    • title: Check AI crawler access
  • check_local_seo_detailsLocal 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, c…Reads text others writeCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a destination (input.phone): what the tool writes goes there.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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), result (the details below), resultId and reportUrl (null). The check saves nothing. When the person asks for a link to open or share later, pass resultId to share_report within an hour. 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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
    • title: Check local SEO details
  • check_robots_sitemap_llms_txtChecks 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, Goog…Reads text others writeCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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), result (the details below), resultId and reportUrl (null). The check saves nothing. When the person asks for a link to open or share later, pass resultId to share_report within an hour. 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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
    • title: Check robots.txt, sitemaps and llms.txt
  • compare_with_competitor_pageRuns 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.Reads text others writeCan send data out1 finding

    Why it is in this group

    • The name "compare_with_competitor_page" says "compare": a word for reading.
    • The description's first verb is "run": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.

    Findings

    • Warn

      The server marks "compare_with_competitor_page" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":true}; The name "compare_with_competitor_page" says "compare": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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), result (the details below), resultId and reportUrl (null). The check saves nothing. When the person asks for a link to open or share later, pass resultId to share_report within an hour. 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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
    • title: Compare with a competitor's page
  • draft_llms_txtDrafts 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 …Reads text others writeCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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) and result (the details below); resultId and reportUrl are null, as drafts are not saved. 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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
    • title: Draft an llms.txt file
  • draft_robots_txt_for_ai_crawlersDrafts 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…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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) and result (the details below); resultId and reportUrl are null, as drafts are not saved. Errors come back as one plain sentence.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
    • title: Draft robots.txt rules for AI crawlers
  • draft_schema_markupDrafts 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 …Reads text others writeCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a destination (input.phone): what the tool writes goes there.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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) and result (the details below); resultId and reportUrl are null, as drafts are not saved. 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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
    • title: Draft schema markup (JSON-LD)
  • request_full_auditFiles 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 …Reads text others writeNo findings

    Why it is in this group

    • The name "request_full_audit" says "request": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: true
    • title: Request a full WorkPods audit
  • seo_audit_pageSEO 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.Reads text others writeCan send data outNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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), result (the details below), resultId and reportUrl (null). The check saves nothing. When the person asks for a link to open or share later, pass resultId to share_report within an hour. 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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
    • title: SEO audit of one page
  • share_reportSaves the result of a check as a report page the person can open and share, kept 30 days, and returns its link.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "save": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Saves the result of a check as a report page the person can open and share, kept 30 days, and returns its link. Use it only when the person asks for a link to the results or a report to share. Pass the resultId that seo_audit_page, check_robots_sitemap_llms_txt, check_ai_crawler_access, check_agent_readiness, compare_with_competitor_page or check_local_seo_details returned; it stays valid for one hour after the check, and the same resultId always gives the same link. result has tool and url (the check and page the report covers) and reportUrl is the report page. An unknown or expired resultId is an error: run the check again, then share it. Recorded: the tool and the app name.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: true
    • title: Save a shareable report
  • start_site_crawlStarts 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, no…Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "start_site_crawl" says "start": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe name "start_site_crawl" says "crawl": it reads web pages, which anyone can write.
    • untrusted-inputThe description's first sentence says "crawl": it reads web pages, which anyone can write.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: true
    • title: Start a site-wide SEO crawl
Only reads 1Show 1 read-only tool
  • get_site_crawlReads a crawl started by start_site_crawl.Reads text others writeNo findings

    Why it is in this group

    • The name "get_site_crawl" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe name "get_site_crawl" says "crawl": it reads web pages, which anyone can write.
    • untrusted-inputThe description's first sentence says "crawl": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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), result (the details below) and reportUrl (a report page of the finished crawl the person can open and share, kept 30 days; null until the crawl is done). Errors come back as one plain sentence.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
    • title: Get the site crawl results

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 21, 2026, 19:21 UTC, unchanged since Nov 14, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
12
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 12 tools that change things (12 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.workpods.ai/mcp: tools/list returned 13 tools to an anonymous client, including seo_audit_page (write), check_robots_sitemap_llms_txt (write), check_ai_crawler_access (write), check_agent_readiness (write), compare_with_competitor_page (write) and 7 more

    What this check looks for

Posture changes

  1. Nov 14, 2026
    • Tools that change things, listed without credentials: 11 to 12

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "compare_with_competitor_page" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":true}; The name "compare_with_competitor_page" says "compare": a word for reading.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 added, 11 changed.+1 added~11 changedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 11 -> 12.View diff
    • Tools that change things, listed without credentials: 11 to 12
  3. Tools7 added, 7 removed, 4 changed.+7 added−7 removed~4 changedView diff

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http agent-ready https://mcp.workpods.ai/mcp
claude mcp add --transport http agent-ready https://mcp.workpods.ai/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__agent-ready__get_site_crawl"
    ],
    "ask": [
      "mcp__agent-ready__seo_audit_page",
      "mcp__agent-ready__check_robots_sitemap_llms_txt",
      "mcp__agent-ready__check_ai_crawler_access",
      "mcp__agent-ready__check_agent_readiness",
      "mcp__agent-ready__compare_with_competitor_page",
      "mcp__agent-ready__check_local_seo_details",
      "mcp__agent-ready__draft_llms_txt",
      "mcp__agent-ready__draft_robots_txt_for_ai_crawlers",
      "mcp__agent-ready__draft_schema_markup",
      "mcp__agent-ready__share_report",
      "mcp__agent-ready__start_site_crawl",
      "mcp__agent-ready__request_full_audit"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as agent-ready. Review it before you use it.

Capability tags behind 12 rules
  • mcp__agent-ready__seo_audit_page untrusted-input, outbound
  • mcp__agent-ready__check_robots_sitemap_llms_txt untrusted-input, outbound
  • mcp__agent-ready__check_ai_crawler_access untrusted-input, outbound
  • mcp__agent-ready__check_agent_readiness untrusted-input, outbound
  • mcp__agent-ready__compare_with_competitor_page untrusted-input, outbound
  • mcp__agent-ready__check_local_seo_details untrusted-input, outbound
  • mcp__agent-ready__draft_llms_txt untrusted-input, outbound
  • mcp__agent-ready__draft_schema_markup untrusted-input, outbound
  • mcp__agent-ready__share_report untrusted-input
  • mcp__agent-ready__start_site_crawl untrusted-input, outbound
  • mcp__agent-ready__get_site_crawl untrusted-input
  • mcp__agent-ready__request_full_audit untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/ai.workpods/agent-ready-mcp/verify?hash=8f0cc10421864a11f0693523738e2a36beb13328f4717b5b46e93fb5b7aa516f" | jq -e '.changed == false'

Pinned hash 8f0cc1042186, from Nov 21, 2026, 05:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/ai.workpods/agent-ready-mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for ai.workpods/agent-ready-mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/ai.workpods/agent-ready-mcp.svg)](https://radar.anlyon.com/servers/ai.workpods/agent-ready-mcp)

Source: MCP Registry. Synced Nov 7, 2026, 01:17 UTC.

Agent Ready Website Audit MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Agent Ready Website Audit MCP server safe?

No scan can promise that. What its definitions show: 13 tools, 12 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Agent Ready Website Audit MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Agent Ready Website Audit MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Agent Ready Website Audit MCP server have?

13 tools: 12 write, 1 read. seo_audit_page, check_robots_sitemap_llms_txt, check_ai_crawler_access, check_agent_readiness, compare_with_competitor_page, check_local_seo_details, draft_llms_txt, draft_robots_txt_for_ai_crawlers and 5 more.

Does the Agent Ready Website Audit MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Agent Ready Website Audit MCP server send data to outside services?

9 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): seo_audit_page, check_robots_sitemap_llms_txt, check_ai_crawler_access, check_agent_readiness, compare_with_competitor_page, check_local_seo_details and 3 more.

Has the Agent Ready Website Audit MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 21, 2026. Every change is on this page and in its Atom feed.