AccessMend vs Inclusify Accessibility
AccessMend is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.
AccessMend is a plugin bundle for AI coding tools published by Eric. 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-25. 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 alepha188838884/accessmend | Removed on 2026-10-15 Version: 0.2.0 Forks (GitHub): 0 Stars (GitHub): 0 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 | AccessMendno longer listed · | Inclusify Accessibility |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) | 0 | 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 |
| Hooks it runs (differs) | 1 | Not published |
| Parts of the bundle (differs) | 3 | Not a bundle |
| Licence | MIT | MIT |
| Repository (differs) | github.com/alepha188838884/accessmend | 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 12 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 AccessMend
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Design, implement, and verify accessible experiences against WCAG 2.1 and 2.2, including runtime keyboard and focus validation, accessible Markdown authoring, and accessibility…
-
WCAG accessibility auditing, compliance validation, UI testing for screen readers, keyboard navigation, and inclusive design
-
WCAG accessibility auditing, compliance validation, UI testing for screen readers, keyboard navigation, and inclusive design
-
WCAG 2.2 accessibility audit and fix for React, Next.js, Vue, Angular, Svelte, and HTML. Static scanner detecting 20+ violation types, contrast checker with suggest mode…
-
mcp-wcag-accessibility-audit com.mambabuilt/mcp-wcag-accessibility-audit
Audit websites for WCAG issues with axe-core, plus EAA exposure signals and compliance page checks.
-
wcag-accessibility io.github.aditya-ariosity/wcag-accessibility
A WCAG accessibility testing MCP for AI agents, Codex, Claude Code, and automated UI audits.
What each says it does
AccessMend
WCAG 2.2 AA accessibility audit + diff-based fixes for web apps. Born from building six apps for autistic children. Automated tools catch ~57% of issues at best — this plugin does not guarantee compliance.
Inclusify Accessibility
Accessibility and WCAG data for your own websites: fix lists, live checks, and fix validation.
How to run each
AccessMend
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: AccessMend · 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.