
mcp-seo-audit
io.github.atomno-mcpPublished by GitHub account atomno-mcpv0.4.7Updated Oct 24, 2026
Technical SEO site audit MCP: health score, issues, robots, sitemap, JSON-LD.
The publisher's own server: audit.domains - Domain Valuation
Overview
Runs real technical SEO and GEO audits of a site, returning a deterministic health score, categorized issues, and fix advice.
- What you can do
- Provides eight tools: audit_site returns a 0-100 health score, letter grade, and issues grouped by category; audit_diff compares a site against its previous snapshot; list_checks and explain_issue describe the engine's checks and how to fix them; validate_robots and check_sitemap inspect robots.txt and sitemap.xml; build_jsonld and build_meta generate schema.org JSON-LD and head meta tags. It performs actual HTTP requests, probing TLS, redirects, TTFB, AI-crawler access, and llms.txt rather than inferring from model knowledge.
- When to use it
- Useful when an assistant needs measured, reproducible SEO findings for a page or site instead of guesses, for tracking changes between audits, or for generating and validating structured data and meta tags.
- Requirements
- Runs locally over stdio, typically launched with uvx from the PyPI package atomno-mcp-seo-audit, so a Python/uv runtime and network access are needed. No key is required for the free tier; deeper checks, GEO sub-score, deep-crawl, and audit_diff need DETAILWEB_API_KEY from a PRO+ plan or higher. Optional variables: DETAILWEB_API_BASE, DETAILWEB_TIMEOUT, DETAILWEB_LANG.
Installation
In SourceWeft
- Open mcp-seo-audit in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
atomno-mcp-seo-audit
[PyPI] [Python] [License: MIT] [MCP]
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) — API
keys unlock the deeper engine on the PRO+ plan and up (see Free vs PRO+).
Why pair it with an LLM?
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.
What you get
audit_site(url, depth=1, lang="ru")— one call returns:- health score
0–100(higher is better) and a letter gradeA–F; - issues grouped by category (security, SEO & indexing, performance, GEO, …),
each with status
pass / warn / fail; - a short human-readable summary.
- health score
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 feature — needs a key on the PRO+ plan or higher.list_checks(lang="ru")— the full catalogue of engine checks grouped by category, with afree/PRObadge 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 acheck_idfromaudit_siteorlist_checks. Title and category are localized; detailed advice is currently in Russian (theadvice_langfield reports this).validate_robots(content, lang="ru")— paste arobots.txtand get back syntax issues, whether aSitemap: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 description (120–160 chars) lengths.
Free vs PRO+
Which plan unlocks the API/MCP? Programmatic access (this server,
audit_diff, deep-crawl, GEO sub-score) is enabled on PRO+ (pro_plus), Business and Enterprise. The entry-level PRO plan and the Free tier are web-dashboard only — an API key issued on them authenticates but still returns the free result. If you need programmatic access, pick PRO+ or higher.
The audit engine itself stays on the server — this package is a thin client (HTTP calls + formatting only).
Install
Or add to your MCP client config (mcp.json):
Configuration
All via environment variables:
The free tier needs no key and no signup — just run the command above.
Programmatic access (40+ deeper checks, GEO sub-score, deep-crawl, audit_diff)
requires a key from the PRO+ plan or higher — the entry-level PRO plan is
web-dashboard only and its key returns the free result. It is currently
provisioned on request: email [email protected] or reach out via
audit.detailweb.ru. Once your account is active you
create keys yourself in Dashboard → Account → API keys (dwa_…, shown once)
and put the key in DETAILWEB_API_KEY.
Example
"Audit https://example.com"
The agent calls audit_site("https://example.com") and gets back the health
score, grade and the list of issues to fix.
License
MIT © atomno-mcp. The open-source client talks to a proprietary hosted backend.
🇷🇺 На русском
MCP-сервер технического SEO-аудита на движке detail.web. Запускайте аудит прямо из ИИ-агента (Cursor, Claude Desktop и любой MCP-клиент): health-score, проблемы по 8 категориям и GEO-суб-балл (видимость в ИИ-поиске — ChatGPT, Perplexity, AI Overviews).
Зачем в связке с нейросетью. Языковая модель сама по себе судит о сайте по
обучающим данным и в лучшем случае по одной отрисованной странице — она не
прочитает напрямую срок SSL-сертификата, не измерит время ответа, не распарсит
sitemap.xml и не проверит, заблокирован ли GPTBot в robots.txt. Этот сервер
выполняет такие проверки по-настоящему: HTTP-запросы, заголовки, редиректы,
микроразметка — и даёт детерминированный score (тот же сайт → то же число),
пригодный для отчёта клиенту. Это прибор, а нейросеть — аналитик, который читает
показания. Лучше всего работает связка.
Инструменты: audit_site (аудит + score + GEO), audit_diff (что
изменилось с прошлой проверки — stateful, тариф PRO+ и выше), list_checks (каталог
проверок free/PRO), explain_issue (почему важно + как исправить),
validate_robots, check_sitemap, build_jsonld, build_meta.
Установка:
В конфиге MCP-клиента (mcp.json):
Бесплатный тариф (базовые проверки, одна страница) работает сразу, без ключа
и регистрации. Программный доступ (40+ глубоких проверок, GEO-суб-балл,
deep-crawl до 20 страниц, audit_diff) работает с ключом тарифа PRO+
(pro_plus) и выше — Business, Enterprise. Начальный тариф PRO
(1290 ₽) и Free — только веб-кабинет: ключ на них проходит авторизацию, но
результат остаётся бесплатным. Тариф пока выдаём по запросу: напишите на
[email protected] или через audit.detailweb.ru.
После активации аккаунта ключ (dwa_…) создаётся в кабинете → Аккаунт →
API-ключи (показывается один раз) и подставляется в DETAILWEB_API_KEY в
env. Полное описание инструментов и настроек — в английской версии выше.
Source: README.md at commit 751e636
Tools
0Version history
1- v0.4.7LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Other Audit integrations
audit.domains - Domain Valuation
domains.auditOfficial publisher
Deterministic domain-name valuation: fair-value intervals, comparable recorded sales, availability checks, and a verified for-sale listing market.
Revenue Agent — OpenAPI Audit & Change Detection
news.prhOfficial publisher
A remote MCP endpoint that audits OpenAPI specifications and detects API changes, charging $0.10 USDC per analysis via x402 on Base.

SEO Audit & Broken Link Checker
Published by GitHub account prometheus-maker
An Apify-hosted MCP server that audits a website's pages for SEO metadata and finds broken links and images, returning per-page scores.

FinePrint AI Legal Risk & Contract Audit MCP Server
Published by GitHub account RitualDev-Lab
Local in-memory scanner that grades legal contracts, NDAs and leases for risk and drafts redline amendments for coding agents.

Mcp Supply Audit
Published by GitHub account kimmawla
Audits MCP servers as supply-chain artifacts — registry entries, PyPI/npm packages, client configs and tool definitions — using read-only static checks.