Ext Ops Panel
Open dashboard
Comparison

claude-seo-and-geo-site-audit vs io.github.SeoScoreAPI/seoscoreapi-mcp

claude-seo-and-geo-site-audit is a plugin bundle for AI coding tools published by rjspence3. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.SeoScoreAPI/seoscoreapi-mcp is an MCP server published by SeoScoreAPI. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceclaude-seo-and-geo-site-auditio.github.SeoScoreAPI/seoscoreapi-mcp
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.4.1
Downloads/month (npm): 651
Downloads/week (npm): 434
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

claude-seo-and-geo-site-audit vs io.github.SeoScoreAPI/seoscoreapi-mcp
Factclaude-seo-and-geo-site-auditio.github.SeoScoreAPI/seoscoreapi-mcp
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (seoscoreapi-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/rjspence3/claude-site-auditgithub.com/seoscoreapi/seoscoreapi-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

claude-seo-and-geo-site-audit

In its own words, on Claude Code: claude-plugins-community:

Audits public-facing websites across accessibility, SEO, GEO (AI search readiness), and usability -- evaluates 17 checks, assigns a letter grade, and generates a client-ready PDF with prioritized recommendations

io.github.SeoScoreAPI/seoscoreapi-mcp

In its own words, on Official MCP Registry:

SEO audits, AI readability, accessibility, backlinks and score monitoring from SEO Score API.

How to run each

claude-seo-and-geo-site-audit As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install claude-seo-and-geo-site-audit@claude-community

io.github.SeoScoreAPI/seoscoreapi-mcp As a local MCP server: npm package

Claude Code
claude mcp add --env "SEO_SCORE_API_KEY=<YOUR_SEO_SCORE_API_KEY>" --transport stdio seoscoreapi-mcp -- npx -y seoscoreapi-mcp

Requires: SEO_SCORE_API_KEY (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of claude-seo-and-geo-site-audit publish no settings it asks for, so we do not compare settings.

What it can do: claude-seo-and-geo-site-audit · What it can do: io.github.SeoScoreAPI/seoscoreapi-mcp · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built