MCP Observatory
npm analyzed 0.1.0

@wcag-checkr/mcp

v0.1.0
npm

Model Context Protocol server for wcagcheckr. Lets LLM-IDEs (Claude Code, Cursor, Continue, etc.) drive accessibility audits, verify forensic receipts, and look up tier features programmatically. Same audit engine as the Chrome extension and CI runner.

maintainer
wcagcheckr
license
UNLICENSED
first seen
2026-05-24
last seen
2026-06-14
releases · 30d
233
short id
risk34/100 · heuristic grade
B low
  • capability exposureinferred+22
  • inherited (deps)attested+15
  • trust mitigatorsmixed−3

attestedinferredmixed

The A–E grade is our heuristic synthesis — a "review this" prompt, not a verdict. Each factor is tagged by what backs it: attested (a verifiable record), reported (a third party's claim), or inferred (our own heuristic, e.g. permissions). See methodology.

graded 10m ago · see ecosystem CVEs →

capability exposuregrade factor +22
Inferred surface — each links to servers holding it:
vulnerabilities0 CVEs

no known CVEs for this server.

inherited (deps) · grade factor +15

inherited via dependencies3
HIGH
@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse via @modelcontextprotocol/sdk · 1 hop CVE-2026-25536 fixed in 1.26.0
HIGH
Anthropic's MCP TypeScript SDK has a ReDoS vulnerability via @modelcontextprotocol/sdk · 1 hop CVE-2026-0621 fixed in 1.25.2
HIGH
Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default via @modelcontextprotocol/sdk · 1 hop CVE-2025-66414 fixed in 1.24.0
tool safety1 findings · grade factor +0
  1. highdangerous code

    env-secret-flows-to-network-js: A process environment value (often a secret/token) flows into a network call — possible credential exfiltration. (/tmp/obs-code-xvyQFR/package/wcagc

embed badgereadme-ready
live risk-grade badge preview [![MCP Observatory risk grade](https://mcpobservatory.com/servers/npm:@wcag-checkr/mcp/badge.svg)](https://mcpobservatory.com/servers/npm:@wcag-checkr/mcp/security)

Heuristic, inferred signals — false positives (legitimately powerful tools, forks, language ports) are expected. Treat each as "review this", not a verdict. See the ecosystem-wide picture on the security hub, or the fleet security of wcagcheckr.