Ext Ops Panel
Open dashboard
Comparison

site-autopsy vs CrazySEO

site-autopsy is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑17.

site-autopsy is a plugin bundle for AI coding tools published by AgileRocket. No marketplace we read lists it any more. CrazySEO is an MCP server published by bolidee. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacesite-autopsyCrazySEO
Community marketplace airzona/site-autopsy Removed on 2026-10-17
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 2
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.2
Downloads/month (npm): 439
Downloads/week (npm): 59
Forks (GitHub): 0
Stars (GitHub): 4
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

site-autopsy vs CrazySEO
Factsite-autopsyno longer listed · CrazySEO
Marketplaces that list it (differs)01
Stars (GitHub) (differs)24
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (crazyseo)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published3, secrets among them: 3
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITAGPL-3.0-or-later
Repository (differs)github.com/airzona/site-autopsygithub.com/bolidee/crazyseo
Changes in the last 7 days22
First seen (differs)2026-10-142026-10-11

Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.

What to use instead of site-autopsy

Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.

  • Website Auditor

    AI visibility + site audits: see if ChatGPT, Perplexity, Claude & Gemini recommend a website.

    by SpikeyCoder · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • web-quality-skills

    Measured performance, Core Web Vitals, accessibility, SEO, best-practices, and agentic browsing skills for any web stack.

    by Addy Osmani · Plugin bundle

    Listed on: Community GitHub marketplaces · Describes nearly the same job

  • claude-seo-and-geo-site-audit

    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…

    by rjspence3 · Plugin bundle

    Listed on: Claude Code: claude-plugins-community · Describes nearly the same job

  • audit ai.webmatik/audit

    AI website growth audits: SEO, performance, AI readiness (GEO), conversion, a11y, security.

    by webmatik.ai · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • PageLens AI

    AI website audit: security, SEO, performance, UX and accessibility checks with actionable fixes.

    by PageLens-AI · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

  • site-spec

    MCP server: audit any website for SEO, accessibility, and AI-searchability, then auto-fix it.

    by ariaxhan · MCP server

    Listed on: Official MCP Registry · Describes nearly the same job

Its card, with similar plugins by marketplace

What each says it does

site-autopsy

In its own words, on Community GitHub marketplaces:

Brutal AI website audit. Lighthouse + axe + niche-aware design critique.

CrazySEO

In its own words, on Official MCP Registry:

Audit whether ChatGPT, Gemini and Perplexity recommend a site. Readiness checks need no keys.

How to run each

site-autopsy

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

CrazySEO As a local MCP server: npm package

Claude Code
claude mcp add --env "GOOGLE_API_KEY=<YOUR_GOOGLE_API_KEY>" --env "OPENAI_API_KEY=<YOUR_OPENAI_API_KEY>" --env "PERPLEXITY_API_KEY=<YOUR_PERPLEXITY_API_KEY>" --transport stdio crazyseo -- npx -y crazyseo

Requires: GOOGLE_API_KEY (secret), OPENAI_API_KEY (secret), PERPLEXITY_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 site-autopsy publish no settings it asks for, so we do not compare settings.

What it can do: site-autopsy · What it can do: CrazySEO · 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. 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