io.github.joe-watkins/magentaa11y
NPM · MAGENTAA11Y-MCP · SCANNED SEP 25
MCP server providing accessibility criteria from MagentaA11y
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 8 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 716 tokens (~65/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.joe-watkins/magentaa11y MCP server?
io.github.joe-watkins/magentaa11y runs locally as an npm package, launched with npx -y magentaa11y-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · magentaa11y-mcp
claude mcp add joe-watkins-magentaa11y -- npx -y magentaa11y-mcp
{
"mcpServers": {
"joe-watkins-magentaa11y": {
"command": "npx",
"args": [
"-y",
"magentaa11y-mcp"
]
}
}
} {
"servers": {
"joe-watkins-magentaa11y": {
"command": "npx",
"args": [
"-y",
"magentaa11y-mcp"
]
}
}
} codex mcp add joe-watkins-magentaa11y -- npx -y magentaa11y-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"joe-watkins-magentaa11y": {
"type": "local",
"command": [
"npx",
"-y",
"magentaa11y-mcp"
],
"enabled": true
}
}
} openclaw mcp add joe-watkins-magentaa11y --command npx --arg -y --arg magentaa11y-mcp
mcp_servers:
joe-watkins-magentaa11y:
command: "npx"
args: ["-y", "magentaa11y-mcp"] {
"McpServers": {
"joe-watkins-magentaa11y": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"magentaa11y-mcp"
]
}
}
} assistant mcp add joe-watkins-magentaa11y -t stdio -c npx -a -y magentaa11y-mcp
{
"mcpServers": {
"joe-watkins-magentaa11y": {
"command": "npx",
"args": [
"-y",
"magentaa11y-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 −3
- Stability: pass → 0.80 functional
- 23 Sept 26 0
- Stability: 0.97 → pass security
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Sept 2026 · Analysed npm/magentaa11y-mcp@1.0.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_component_condensed ~57
Get condensed acceptance criteria for a component. These are shorter, more focused testing instructions.
| Name | Type | Req | Description |
|---|---|---|---|
| component | string | yes | Component name (e.g., "button", "checkbox") |
| platform | string | yes | Platform (web or native) |
No output schema declared.
No examples provided.
get_component_developer_notes ~61
Get developer implementation notes for a component. Includes code examples, WCAG mappings, and technical guidance.
| Name | Type | Req | Description |
|---|---|---|---|
| component | string | yes | Component name (e.g., "button", "checkbox") |
| platform | string | yes | Platform (web or native) |
No output schema declared.
No examples provided.
get_component_gherkin ~65
Get Gherkin-style acceptance criteria for a component. These are detailed Given/When/Then scenarios for testing accessibility.
| Name | Type | Req | Description |
|---|---|---|---|
| component | string | yes | Component name (e.g., "button", "checkbox") |
| platform | string | yes | Platform (web or native) |
No output schema declared.
No examples provided.
get_component_native_notes ~57
Get platform-specific developer notes for native components (iOS or Android implementation details).
| Name | Type | Req | Description |
|---|---|---|---|
| component | string | yes | Component name (e.g., "button", "switch") |
| platform | string | yes | Native platform (ios or android) |
No output schema declared.
No examples provided.
get_native_component ~74
Get detailed accessibility criteria for a specific native component. Returns iOS and Android implementation details, platform-specific properties, and code examples.
| Name | Type | Req | Description |
|---|---|---|---|
| component | string | yes | Component name (e.g., "button", "switch", "picker") |
| include_code_examples | boolean | – | Include platform-specific code examples (default: true) |
No output schema declared.
No examples provided.
get_web_component ~74
Get detailed accessibility criteria for a specific web component. Returns acceptance criteria, WCAG mappings, code examples, and implementation guidelines.
| Name | Type | Req | Description |
|---|---|---|---|
| component | string | yes | Component name (e.g., "button", "checkbox", "text-input") |
| include_code_examples | boolean | – | Include code examples in response (default: true) |
No output schema declared.
No examples provided.
list_component_formats ~61
List all available content formats for a specific component (e.g., gherkin, condensed, developer notes).
| Name | Type | Req | Description |
|---|---|---|---|
| component | string | yes | Component name (e.g., "button", "checkbox") |
| platform | string | yes | Platform (web or native) |
No output schema declared.
No examples provided.
list_native_components ~53
List all available native (iOS/Android) accessibility components from MagentaA11y. Optionally filter by category.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional category filter (e.g., "controls", "components") |
No output schema declared.
No examples provided.
list_web_components ~59
List all available web accessibility components from MagentaA11y. Optionally filter by category (e.g., controls, forms, components).
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional category filter (e.g., "controls", "forms", "components") |
No output schema declared.
No examples provided.
search_native_criteria ~81
Search native accessibility criteria using keywords. Find platform-specific implementation details for iOS (VoiceOver) and Android (TalkBack).
| Name | Type | Req | Description |
|---|---|---|---|
| max_results | number | – | Maximum number of results to return (default: 10) |
| query | string | yes | Search term or phrase (e.g., "voiceover", "talkback", "accessibility label") |
No output schema declared.
No examples provided.
search_web_criteria ~74
Search web accessibility criteria using keywords. Find criteria related to WCAG guidelines, implementation patterns, or specific accessibility requirements.
| Name | Type | Req | Description |
|---|---|---|---|
| max_results | number | – | Maximum number of results to return (default: 10) |
| query | string | yes | Search term or phrase (e.g., "focus indicator", "aria-label") |
No output schema declared.
No examples provided.
What is the io.github.joe-watkins/magentaa11y MCP server?
io.github.joe-watkins/magentaa11y is an MCP server listed in the public MCP registry as io.github.joe-watkins/magentaa11y. MCP server providing accessibility criteria from MagentaA11y. This page covers its npm package (magentaa11y-mcp).
Is the io.github.joe-watkins/magentaa11y MCP server safe to use?
io.github.joe-watkins/magentaa11y scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.joe-watkins/magentaa11y MCP server expose?
io.github.joe-watkins/magentaa11y exposes 11 tools: list_web_components, get_web_component, search_web_criteria, list_native_components, get_native_component, and 6 more. Their descriptions and schemas cost roughly 716 tokens of context every time the server is loaded.
Is the io.github.joe-watkins/magentaa11y MCP server still maintained?
io.github.joe-watkins/magentaa11y is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.joe-watkins/magentaa11y MCP server under?
io.github.joe-watkins/magentaa11y declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.