io.github.MMasey/atag-mcp
NPM · ATAG-MCP · SCANNED SEP 20
ATAG 2.0 (Authoring Tool Accessibility Guidelines) guidance for authoring tool developers
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 & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to MMasey/atag-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 74 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 754 tokens (~58/item across 13 items; 13 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 79% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 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.MMasey/atag-mcp server?
io.github.MMasey/atag-mcp runs locally as an npm package, launched with npx -y atag-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 · atag-mcp
claude mcp add mmasey-atag-mcp -- npx -y atag-mcp
{
"mcpServers": {
"mmasey-atag-mcp": {
"command": "npx",
"args": [
"-y",
"atag-mcp"
]
}
}
} {
"servers": {
"mmasey-atag-mcp": {
"command": "npx",
"args": [
"-y",
"atag-mcp"
]
}
}
} codex mcp add mmasey-atag-mcp -- npx -y atag-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mmasey-atag-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"atag-mcp"
],
"enabled": true
}
}
} openclaw mcp add mmasey-atag-mcp --command npx --arg -y --arg atag-mcp
mcp_servers:
mmasey-atag-mcp:
command: "npx"
args: ["-y", "atag-mcp"] {
"McpServers": {
"mmasey-atag-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"atag-mcp"
]
}
}
} assistant mcp add mmasey-atag-mcp -t stdio -c npx -a -y atag-mcp
{
"mcpServers": {
"mmasey-atag-mcp": {
"command": "npx",
"args": [
"-y",
"atag-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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −2
- Stability: pass → 0.80 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 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.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −2
- Stability: pass → 0.80 functional
- 9 Sept 26 0
- Stability: 0.97 → pass security
- 8 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
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 20 Sept 2026 · Analysed npm/atag-mcp@1.0.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | MMasey/atag-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/MMasey/atag-mcp/.github/workflows/publish.yml@refs/tags/v1.0.2 |
| Rekor log index | 2102779190 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:d13b5e4e06eb678460e9ca7fde12593689adaf3a342707ee3468955ac667f48345bd9a850273f7b92f4f67ad7ab75ef702492fc9fcffae6f70fecdccf |
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 →
explain-atag ~42
Get an overview of ATAG 2.0 — what it is, who it applies to, how it differs from WCAG, and its two-part structure.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get-criteria-by-level ~76
Get all ATAG 2.0 success criteria at a specific conformance level (A, AA, or AAA). Optionally filter by part.
| Name | Type | Req | Description |
|---|---|---|---|
| level | string | yes | ATAG conformance level |
| part | string | – | Part A (tool UI accessibility) or Part B (supporting accessible content production) |
No output schema declared.
No examples provided.
get-criterion ~81
Get full details for a specific ATAG 2.0 success criterion by ID (e.g. 'B.2.3.1' or 'A.3.1.2'), including description, conformance level, and implementation notes.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Success criterion ID, e.g. 'B.2.3.1' |
No output schema declared.
No examples provided.
get-glossary-term ~50
Get the definition of a specific ATAG 2.0 term.
| Name | Type | Req | Description |
|---|---|---|---|
| term | string | yes | The term to look up, e.g. 'authoring tool' or 'editing-view' |
No output schema declared.
No examples provided.
get-guidance ~93
Given a description of an authoring tool feature or scenario, return the most relevant ATAG 2.0 success criteria. Use this to find which criteria apply when building a specific feature.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | Describe the authoring tool feature or scenario, e.g. 'We are building an image upload dialog that lets authors insert images into content' or 'Our tool automatically generates HTML from a visual lay… |
No output schema declared.
No examples provided.
get-guideline ~64
Get full details for a specific ATAG 2.0 guideline by ID (e.g. 'B.2.3'), including its description and all child success criteria.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Guideline ID, e.g. 'B.2.3' |
No output schema declared.
No examples provided.
get-server-info ~34
Get information about this ATAG MCP server including the total number of principles, guidelines, success criteria, and glossary terms available.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list-glossary-terms ~23
List all ATAG 2.0 glossary terms.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list-guidelines ~72
List ATAG 2.0 guidelines. Optionally filter by part (A or B) and/or principle ID (e.g. 'A.3').
| Name | Type | Req | Description |
|---|---|---|---|
| part | string | – | Part A (tool UI accessibility) or Part B (supporting accessible content production) |
| principleId | string | – | – |
No output schema declared.
No examples provided.
list-parts ~26
List both parts of ATAG 2.0 with their descriptions and principle counts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list-principles ~52
List ATAG 2.0 principles. Optionally filter by part (A or B).
| Name | Type | Req | Description |
|---|---|---|---|
| part | string | – | Part A (tool UI accessibility) or Part B (supporting accessible content production) |
No output schema declared.
No examples provided.
list-success-criteria ~87
List ATAG 2.0 success criteria. Filter by part, principle ID, guideline ID, and/or conformance level.
| Name | Type | Req | Description |
|---|---|---|---|
| guidelineId | string | – | – |
| level | string | – | ATAG conformance level |
| part | string | – | Part A (tool UI accessibility) or Part B (supporting accessible content production) |
| principleId | string | – | – |
No output schema declared.
No examples provided.
search-atag ~54
Search across all ATAG 2.0 content (principles, guidelines, success criteria, glossary) using keywords.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Search query, e.g. 'keyboard access' or 'alternative text' |
No output schema declared.
No examples provided.
What is the io.github.MMasey/atag-mcp server?
io.github.MMasey/atag-mcp is listed in the public MCP registry as io.github.MMasey/atag-mcp. ATAG 2.0 (Authoring Tool Accessibility Guidelines) guidance for authoring tool developers. This page covers its npm package (atag-mcp).
Is the io.github.MMasey/atag-mcp server safe to use?
io.github.MMasey/atag-mcp scores 93 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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.MMasey/atag-mcp server expose?
io.github.MMasey/atag-mcp exposes 13 tools: get-server-info, explain-atag, list-parts, list-principles, list-guidelines, and 8 more. Their descriptions and schemas cost roughly 754 tokens of context every time the server is loaded.
Is the io.github.MMasey/atag-mcp server still maintained?
io.github.MMasey/atag-mcp is still listed as active in the MCP registry. We last reached this channel on 20 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.MMasey/atag-mcp server under?
io.github.MMasey/atag-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.