mcp-seo-audit

io.github.atomno-mcp由 GitHub 帳號 atomno-mcp 發布v0.4.7更新於 Oct 24, 2026

Technical SEO site audit MCP: health score, issues, robots, sitemap, JSON-LD.

發布方自己的服務:audit.domains - Domain Valuation

概覽

AI 產生的概覽

對網站執行真實的技術 SEO 與 GEO 稽核,回傳確定性的健康分數、分類問題與修正建議。

可以做什麼
提供八個工具:audit_site 回傳 0-100 健康分數、字母等級與依類別分组的問題;audit_diff 與上一次快照比較;list_checks 與 explain_issue 說明引擎的檢查項目及修正方式;validate_robots 與 check_sitemap 檢查 robots.txt 與 sitemap.xml;build_jsonld 與 build_meta 產生 schema.org JSON-LD 與 head 中繼標籤。它會發出真實 HTTP 請求,探測 TLS、重新導向、TTFB、AI 爬蟲存取與 llms.txt,而非依賴模型知識推測。
適用情境
適合需要可量測、可重現的 SEO 結論而非猜測的情境,也適合追蹤兩次稽核之間的變化,或產生並驗證結構化資料與中繼標籤。
執行需求
透過 stdio 在使用者本機執行,通常以 uvx 啟動 PyPI 套件 atomno-mcp-seo-audit,因此需要 Python/uv 執行環境與網路存取。免費層不需要金鑰;更深入的檢查、GEO 子分數、深度爬取與 audit_diff 需要來自 PRO+ 或更高方案的 DETAILWEB_API_KEY。選用變數:DETAILWEB_API_BASE、DETAILWEB_TIMEOUT、DETAILWEB_LANG。
安裝前請注意
選用的 DETAILWEB_API_KEY 是機密,應透過環境變數提供,不要外流。稽核會把目標 URL 傳送到 detail.web 後端,網站地圖檢查會抓取遠端 URL。免費層僅涵蓋核心檢查與單一頁面;入門級 PRO 方案的金鑰仍只回傳免費結果。詳細修正建議目前為俄文。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 mcp-seo-audit,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

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 grade A–F;
    • issues grouped by category (security, SEO & indexing, performance, GEO, …), each with status pass / warn / fail;
    • a short human-readable summary.
  • 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 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 description (120–160 chars) lengths.

Free vs PRO+

Free (no key)PRO+ and up (API key)
Checkscore technical basics40+ deeper checks (E-E-A-T, Schema.org, Goldmine title)
GEO4 GEO signalsGEO readiness sub-score + deep GEO checks
Crawlsingle pagedeep-crawl up to 20 pages (depth=2/3)

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

bash
uvx atomno-mcp-seo-audit

Or add to your MCP client config (mcp.json):

json
{  "mcpServers": {    "seo-audit": {      "command": "uvx",      "args": ["atomno-mcp-seo-audit"]    }  }}

Configuration

All via environment variables:

VariableDefaultPurpose
DETAILWEB_API_BASEhttps://api.detailweb.ruBackend base URL
DETAILWEB_API_KEY—API key (dwa_...) from a PRO+ plan or higher. Without it (or on Free/PRO) → free tier
DETAILWEB_TIMEOUT60HTTP timeout (seconds)
DETAILWEB_LANGruDefault issue-title language (ru / en)

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.

Установка:

bash
uvx atomno-mcp-seo-audit

В конфиге MCP-клиента (mcp.json):

json
{  "mcpServers": {    "seo-audit": {      "command": "uvx",      "args": ["atomno-mcp-seo-audit"],      "env": { "DETAILWEB_LANG": "ru" }    }  }}

Бесплатный тариф (базовые проверки, одна страница) работает сразу, без ключа и регистрации. Программный доступ (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. Полное описание инструментов и настроек — в английской версии выше.

來源:README.md,提交 751e636

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

1
  1. v0.4.7最新Sep 16, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

其他 Audit 整合