Ext Ops Panel
Open dashboard
Comparison

fire-your-seo-agency vs io.github.pijusz/mcp-gsc

fire-your-seo-agency is a plugin bundle for AI coding tools published by leopard627. Marketplaces we read that list it: 1 (Community GitHub marketplaces). io.github.pijusz/mcp-gsc is an MCP server published by pijusz. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-05. 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
Marketplacefire-your-seo-agencyio.github.pijusz/mcp-gsc
Community marketplace leopard627/fire-your-seo-agency Listed
Version: 1.3.0
Forks (GitHub): 222
Stars (GitHub): 994
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.7
Downloads/month (npm): 31 788
Downloads/week (npm): 25 849
Forks (GitHub): 1
Stars (GitHub): 3
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 0.4.1
Downloads/month (npm): 31 788
Downloads/week (npm): 25 849
Forks (GitHub): 1
Stars (GitHub): 3
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

fire-your-seo-agency vs io.github.pijusz/mcp-gsc
Factfire-your-seo-agencyio.github.pijusz/mcp-gsc
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)994 (better)3 (worse)
Forks (GitHub) (differs)222 (better)1 (worse)
Last release (differs)2026-11-03 (better)2026-10-22 (worse)
Where it runs (differs)Installs as a plugin bundleOn your machine (mcp-gsc)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceMITMIT
Repository (differs)github.com/leopard627/fire-your-seo-agencygithub.com/pijusz/mcp-gsc
Changes in the last 7 days (differs)10
First seen (differs)2026-10-262026-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

fire-your-seo-agency

In its own words, on Community GitHub marketplaces:

Fire your SEO agency — audits and implements SEO·AEO·GEO·LLMO·NEO(Naver) itself. Crawler-eye audit, intent landing pages, llms.txt, structured data, Naver AI Briefing, content engine (sub-blog · backlog · publish gate · refresh), measurement loop.

io.github.pijusz/mcp-gsc

In its own words, on Official MCP Registry:

Google Search Console MCP server — query performance, sitemaps, indexing & more

How to run each

fire-your-seo-agency As a Claude Code plugin

Claude Code
/plugin marketplace add leopard627/fire-your-seo-agency
/plugin install fire-your-seo-agency@fire-your-seo-agency

io.github.pijusz/mcp-gsc As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio mcp-gsc -- npx -y mcp-gsc

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

Neither one's marketplaces publish the settings it asks for.

What it can do: fire-your-seo-agency · What it can do: io.github.pijusz/mcp-gsc · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). 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