Technical SEO site audit MCP: health score, issues, robots, sitemap, JSON-LD.
MCPpedia last refreshed this data
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-atomno-mcp-mcp-seo-audit": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Technical SEO site audit MCP: health score, issues, robots, sitemap, JSON-LD.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationBe the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in marketing
DataForSEO API modelcontextprotocol server
MCP server for Mindbox CDP API — customer profiles, orders, segments. 3 tools.
MCP server for Yandex.Direct API — campaigns, ads, statistics, keywords. Bearer token auth.
一键同步文章到多个内容平台,支持今日头条、WordPress、知乎、简书、掘金、CSDN、typecho各大平台,一次发布,多平台同步发布。解放个人生产力
MCP Security Weekly
Get CVE alerts and security updates for io.github.atomno-mcp/mcp-seo-audit and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
MCP (Model Context Protocol) server for technical SEO & GEO audits, powered by
the detail.web engine — real measurements, not LLM
guesses. Run it from Cursor, Claude Desktop or any MCP client. 8 tools:
audit_site (deterministic 0–100 health score + letter grade, 78 checks across
8 categories, plus a GEO sub-score — visibility in ChatGPT / Perplexity /
Google AI Overviews), audit_diff (compare vs the previous snapshot),
robots.txt & sitemap.xml validators, JSON-LD & meta/OpenGraph builders, and
per-check fix explainers. Probes TLS, redirects, TTFB, AI-crawler access (GPTBot)
and llms.txt. Free tier + PRO (deep-crawl, GEO, 40+ deeper checks).
A language model on its own infers a site from training data and, at best, one
rendered page — it can't directly read your TLS certificate's expiry, measure
response time, parse sitemap.xml, or check whether GPTBot is blocked in
robots.txt. This server runs those checks for real: actual HTTP requests,
security headers, redirect chains, structured-data validation — and returns a
deterministic score (same site → same number), reproducible enough to put in
a client report. Think of it as the instrument and the LLM as the analyst that
interprets the readout — the two work best together.
audit_site(url, depth=1, lang="ru") — one call returns:
0–100 (higher is better) and a letter grade A–F;pass / warn / fail;audit_diff(url, lang="ru") — re-audits a site and compares it to the
previous run: health/score delta and which checks got worse or better. The
first call stores a baseline. This is something a one-off LLM question can't
do — track a site over time. Stateful PRO feature (needs an API key).list_checks(lang="ru") — the full catalogue of engine checks grouped by
category, with a free / PRO badge on each — so you (and the agent) can see
exactly what the free tier covers and what PRO unlocks.explain_issue(check_id, lang="ru") — a deep-dive on a single check:
why it matters and how to fix it. Pass a check_id from audit_site or
list_checks. Title and category are localized; detailed advice is currently
in Russian (the advice_lang field reports this).validate_robots(content, lang="ru") — paste a robots.txt and get back
syntax issues, whether a Sitemap: directive is present, whether CSS/JS is
blocked from render bots, and which AI crawlers (GPTBot, ClaudeBot, …) are
explicitly blocked. No fetch — validates the text you provide.check_sitemap(url, lang="ru") — fetches a sitemap by URL and reports its
format (urlset / sitemapindex), URL count and common problems (404,
non-XML content type, http:// links, missing <lastmod>, the 50k-per-file
limit). The fetch is SSRF-guarded on the server.build_jsonld(type, fields, lang="ru") — generates a ready-to-paste
schema.org JSON-LD <script> (Organization, LocalBusiness, Article, Product,
FAQPage, BreadcrumbList, WebSite) and tells you which required/recommended
fields are missing. It never invents data — only what you pass in.build_meta(fields, lang="ru") — generates <head> meta tags (title,
description, canonical, Open Graph, Twitter Card) and validates the title
(50–60 chars) and des