
Stobo SEO & AEO Audit
io.github.stobo-appPublished by GitHub account stobo-appv0.4.3Updated Oct 25, 2026
AI-powered SEO and AEO audit for websites
The publisher's own server: audit.domains - Domain Valuation
Overview
A retired SEO/AEO audit MCP server for Claude Desktop that now only exposes a status tool reporting the service's shutdown.
- What you can do
- Report service status: a single stobo_status tool reports that the Stobo audit service has been retired and its API is no longer available, and nothing else.
- When to use it
- Only for archival or reference purposes, for example if you want to confirm the service's retirement status. It is not useful for auditing websites, since the audit tools no longer exist and the backend API is shut down.
- Requirements
- Runs as a local process via uvx or pip from the stobo-mcp PyPI package, configured in Claude Desktop. The STOBO_API_KEY environment variable is optional and STOBO_BASE_URL defaults to the Stobo API, which is no longer available.
Installation
In SourceWeft
- Open Stobo SEO & AEO 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
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_statustool 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.
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.
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
Premium — coming soon
Routing
- Domain or homepage →
audit_site - Blog post or article URL →
audit_article - After any audit → Claude offers
generate_fix_briefautomatically
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
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_siteoraudit_articlerun. check_connectionreports when a newer version is available.- Version strings are now consistent across server, client, and package.
License
MIT
Source: README.md at commit d2e459e
Tools
0Version history
1- v0.4.3LatestSep 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.

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.

Arquestra Audit
Published by GitHub account pablo-ramossanchez
Audit a data file before publishing: one light per figure. Your data never reaches the server.