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

VerifiedSTDIODesktop only

Overview

AI-generated 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.
Before you install
The service is retired as of May 2026 and the API is gone, so published versions are installable for archival purposes only. Do not expect audits or fix briefs to work, and do not supply an API key expecting functionality.

Installation

In SourceWeft

  1. Open Stobo SEO & AEO Audit in the dashboard and add it to a workspace.
  2. 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_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?

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_site71,000 tk · 6 fetches20,000 tk · 1 call
audit_freshness60,000 tk · 20 fetches3,000 tk · 1 call
generate_llms_txt35,000 tk · 6 fetches3,000 tk · 1 call
extract_tone35,000 tk · 10 fetches5,000 tk · 1 call
Full suite264,500 tk · 56 fetches47,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 ClaudeWhat it doesTool
"Stobo this site: example.com"30 SEO + 7 AEO checks + E-E-A-T + blog detection across your whole siteaudit_site
"Audit this article: example.com/blog/post"7 SEO + 14 AEO checks on a single articleaudit_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 coverageaudit_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.xmlgenerate_sitemap
"Generate freshness code for example.com/blog/post"JSON-LD snippet with datePublished and dateModifiedgenerate_freshness_code
"Check connection"Diagnostic ping. Also tells you if a newer MCP version is available.check_connection

Premium — coming soon

Say to ClaudeWhat it doesTool
"Generate llms.txt for example.com"Crawl your site and return a spec-compliant llms.txtgenerate_llms_txt
"Extract brand voice from example.com/blog"Analyze up to 10 articles and create a persistent voice profileextract_tone
"Rewrite this article: example.com/blog/post"Audit + tone match + full rewrite in one pipelinerewrite_article
"Audit the UX of example.com"50+ UX checks across accessibility, forms, typography, and navigationaudit_ux
"How many credits do I have?"Credit balance and usage breakdownget_credits

Routing

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

Install

bash
pip install stobo-mcp

No install with uvx:

bash
uvx stobo-mcp

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"      }    }  }}

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

bash
pip install --upgrade stobo-mcp

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.

License

MIT

Source: README.md at commit d2e459e

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  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