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.