WCAG Compliance MCP v0.7.1

OpenAI Plugins submission metadata and safety annotations for all 16 MCP tools, plus the OpenAI Apps domain-verification challenge endpoint. The attached demo uses only a sanitized example.com production scan and a neutral tool inventory; it contains no account identity, personal chat list, private site list, or customer data. Automated results are not certification or a compliance guarantee.

v0.2.4

Fixes the default API base URL: the package pointed at http://localhost:8081 (a development default), so a client config that set only WCAGC_MCP_KEY — as the README instructed — silently talked to a port that wasn't there. It now defaults to https://api.wcagc.com; set WCAGC_API_BASE_URL only when self-hosting.

Also corrects the MCP Registry namespace to the organisation's exact casing.

npx -y @wcagc/mcp · hosted: https://mcp.wcagc.com/mcp

v0.2.2

First tagged release of the wcagc MCP server.

Hosted — add as a remote MCP connector, with a mcp:scan API key as the bearer token:

https://mcp.wcagc.com/mcp

Local (stdio) — npx -y @wcagc/mcp

Both transports ship from this one codebase, so the tool catalog is identical either way. GET /health reports the running version, and releases are blocked unless the hosted server matches the version published to npm.

Tools: scan_url, check_pdf, get_scan, get_findings on every plan (daily quota on Free/Starter); list_sites, scan_site, get_run, get_run_findings, run_journey, get_trends on Pro+.

Every scan result carries an automated-coverage disclaimer in both the text and structured content — never a score, grade, or pass/fail verdict.

Docs: https://wcagc.com/integrations/mcp