site-autopsy vs Inclusify Accessibility
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. Inclusify Accessibility is an MCP server published by inclusifyapp.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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
| Marketplace |  Inclusify Accessibility | |
|---|---|---|
| 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: 1.0.2 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
| Fact | site-autopsyno longer listed · | Inclusify Accessibility |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 2 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (app.inclusifyapp.com/api/mcp/customer) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence | MIT | MIT |
| Repository (differs) | github.com/airzona/site-autopsy | github.com/magebitcom/inclusify-plugin |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 30 h ago |
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.
-
AI visibility + site audits: see if ChatGPT, Perplexity, Claude & Gemini recommend a website.
-
Measured performance, Core Web Vitals, accessibility, SEO, best-practices, and agentic browsing skills for any web stack.
-
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…
-
audit ai.webmatik/audit
AI website growth audits: SEO, performance, AI readiness (GEO), conversion, a11y, security.
-
AI website audit: security, SEO, performance, UX and accessibility checks with actionable fixes.
-
MCP server: audit any website for SEO, accessibility, and AI-searchability, then auto-fix it.
What each says it does
site-autopsy
Brutal AI website audit. Lighthouse + axe + niche-aware design critique.
Inclusify Accessibility
Accessibility and WCAG data for your own websites: fix lists, live checks, and fix validation.
How to run each
site-autopsy
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Inclusify Accessibility As a remote MCP server
claude mcp add --transport http inclusify https://app.inclusifyapp.com/api/mcp/customerCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Inclusify Accessibility has a remote endpoint we check. How we check endpoints
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: site-autopsy · What it can do: Inclusify Accessibility · 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.