Stobo SEO & AEO Audit

io.github.stobo-app由 GitHub 帳號 stobo-app 發布v0.4.3更新於 Oct 25, 2026

AI-powered SEO and AEO audit for websites

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

已驗證STDIO僅桌面

服務詳細資訊

識別碼: io.github.stobo-app/seo-audit
傳輸: STDIO
執行環境: Desktop only
信任: Verified
發布於: Sep 16, 2026

安全提示

MCP 服務會接收對話中的工具呼叫請求，並可能執行外部操作。啟用前請先了解該服務能做什麼，並只授予它所需的權限。

註冊中心已驗證此條目所屬的 GitHub 帳號 stobo-app。這並不表明該帳號就是產品方。

SourceWeft 的檢查只涵蓋條目是否完整、端點是否回應；不審查伺服器的程式碼，也不審查其工具的行為。

在 README 中新增徽章

向讀者展示該 MCP 服務已收錄於 SourceWeft，徽章連結到本頁。

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.stobo-app%2Fseo-audit.svg)](https://sourceweft.com/mcp/io.github.stobo-app%2Fseo-audit?utm_source=readme&utm_medium=badge)

概覽

AI 產生的概覽

一個已停用的 SEO/AEO 稽核 MCP 伺服器，供 Claude Desktop 使用，現在僅提供一個回報服務停運的狀態工具。

可以做什麼: 回報服務狀態：只有一個 stobo_status 工具，用來說明 Stobo 稽核服務已停用、其 API 已無法使用，除此之外不提供其他功能。
適用情境: 僅適用於存檔或查閱用途，例如想確認該服務的停運狀態。它無法用於網站稽核，因為稽核工具已不存在，後端 API 也已關閉。
執行需求: 透過 uvx 或 pip 從 stobo-mcp 的 PyPI 套件以本機程序方式執行，並在 Claude Desktop 中設定。STOBO_API_KEY 環境變數為選用，STOBO_BASE_URL 預設指向已無法使用的 Stobo API。

安裝前請注意

該服務已於 2026 年 5 月停用，API 已下線，已發佈版本僅供存檔安裝。不要預期稽核或修正簡報能正常運作，也不要為了期待功能而提供 API 金鑰。

安裝

在 SourceWeft 中

開啟儀表板中的 Stobo SEO & AEO Audit，將其新增到工作區。
為需要使用其工具的對話啟用該服務。

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

其他 MCP 客戶端

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

README

Stobo MCP Server

⚠️ Retired (May 2026). The Stobo SEO/AEO audit service has been shut down and its API is no longer available. This MCP server no longer performs audits — it exposes a single stobo_status tool that reports the retirement and nothing else. Published versions remain installable for archival purposes only. Thank you to everyone who used it.

Audit any site for SEO, AEO, and E-E-A-T from Claude Desktop. Get a structured fix brief your developer can drop straight into Claude Code, Cursor, or VS Code and start shipping.

You: stobo this site: example.com
Claude: I just received a complete audit for example.com. SEO, AEO, EEAT,per-page breakdowns, 30+ checks with scores and details.
Want me to generate a fix brief you can download and drop intoClaude Code, Cursor, or hand off to your developer?

You: stobo this site: example.com
Claude: I just received a complete audit for example.com. SEO, AEO, EEAT,per-page breakdowns, 30+ checks with scores and details.
Want me to generate a fix brief you can download and drop intoClaude Code, Cursor, or hand off to your developer?

Why not just use web_fetch?

Fetching every page manually costs ~386,000 tokens across 16+ calls. It still misses Core Web Vitals, TTFB, and Flesch-Kincaid. Those metrics require server-side computation. Stobo runs everything in one call.

	Manual (web_fetch)	Stobo MCP
`audit_site`	71,000 tk · 6 fetches	20,000 tk · 1 call
`audit_freshness`	60,000 tk · 20 fetches	3,000 tk · 1 call
`generate_llms_txt`	35,000 tk · 6 fetches	3,000 tk · 1 call
`extract_tone`	35,000 tk · 10 fetches	5,000 tk · 1 call
Full suite	264,500 tk · 56 fetches	47,000 tk · 9 calls

82% fewer tokens. And you get metrics Claude cannot compute from raw HTML alone.

What happens after an audit

Claude receives 30+ scored checks across SEO, AEO, and E-E-A-T. It then offers a fix brief: structured markdown with every failing check, prioritized by impact, with specific fix instructions. Paste it into Claude Code, Cursor, or VS Code and start shipping.

Claude also offers generators for quick wins. Failing robots.txt? Claude generates one. Same for llms.txt, sitemap, and freshness code. The audit-to-fix loop runs in a single conversation.

Tools

Free — no API key required

Say to Claude	What it does	Tool
"Stobo this site: example.com"	30 SEO + 7 AEO checks + E-E-A-T + blog detection across your whole site	`audit_site`
"Audit this article: example.com/blog/post"	7 SEO + 14 AEO checks on a single article	`audit_article`
"Generate a fix brief"	Structured markdown fix brief from a completed audit. Numbered tasks, priority order, fix instructions. IDE-ready.	`generate_fix_brief`
"Check freshness across example.com/sitemap.xml"	Scan your sitemap for datePublished and dateModified coverage	`audit_freshness`
"Generate a robots.txt for example.com"	AI-crawler-friendly robots.txt. All 21 major bots covered.	`generate_robots_txt`
"Generate a sitemap for example.com"	BFS-crawl up to 200 URLs and return a sitemap.xml	`generate_sitemap`
"Generate freshness code for example.com/blog/post"	JSON-LD snippet with datePublished and dateModified	`generate_freshness_code`
"Check connection"	Diagnostic ping. Also tells you if a newer MCP version is available.	`check_connection`

Premium — coming soon

Say to Claude	What it does	Tool
"Generate llms.txt for example.com"	Crawl your site and return a spec-compliant llms.txt	`generate_llms_txt`
"Extract brand voice from example.com/blog"	Analyze up to 10 articles and create a persistent voice profile	`extract_tone`
"Rewrite this article: example.com/blog/post"	Audit + tone match + full rewrite in one pipeline	`rewrite_article`
"Audit the UX of example.com"	50+ UX checks across accessibility, forms, typography, and navigation	`audit_ux`
"How many credits do I have?"	Credit balance and usage breakdown	`get_credits`

Routing

Domain or homepage → audit_site
Blog post or article URL → audit_article
After any audit → Claude offers generate_fix_brief automatically

Install

No install with uvx:

Setup

Add to your Claude Desktop config.

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

Windows: %APPDATA%\Claude\claude_desktop_config.json

json

{  "mcpServers": {    "stobo": {      "command": "stobo-mcp",      "env": {        "STOBO_API_KEY": "your-api-key",        "STOBO_BASE_URL": "https://api.trystobo.com"      }    }  }}

{  "mcpServers": {    "stobo": {      "command": "stobo-mcp",      "env": {        "STOBO_API_KEY": "your-api-key",        "STOBO_BASE_URL": "https://api.trystobo.com"      }    }  }}

STOBO_API_KEY is optional. Every audit and fix brief tool works without one. API key support for premium tools is coming soon.

Full setup guide at docs.trystobo.com.

Upgrades

Run check_connection. Claude tells you if a newer version is available.

What's new in v0.5.0

generate_fix_brief: structured fix brief from any completed audit. Free, instant, no LLM.
Claude now offers a fix brief automatically after every audit_site or audit_article run.
check_connection reports when a newer version is available.
Version strings are now consistent across server, client, and package.