ai.workpods/agent-ready-mcp · v1.0.1 · search-and-web
Agent Ready Website Audit is healthy: it completed an MCP handshake in 1781 ms and exposes 12 tools.
SEO and AI search audit for any website: technical SEO, schema, AI crawler access and llms.txt.
Endpoint: https://mcp.workpods.ai/mcp (streamable-http)
No repository listed · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 12 |
| Latency | 1781 ms |
| Last checked (UTC) | 2026-11-07T03:30:44.429Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-11-07T03:30:44.429Z | Healthy | 1781 |
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), l |
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 |
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, |
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. U |
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 |
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 |
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 |
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 |
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 m |
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 |
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; ne |
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 |