io.github.groundlogic-ai-source/accessibility-ai
REMOTE · ACCESSIBILITY.GROUNDLOGIC.AI
Scan URLs for WCAG 2.1 violations, generate AI fixes, and produce VPAT 2.5 compliance reports.
Available components
Last scanned (4 hours ago)
Scores higher than 8% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Testing and QA
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 404. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Transport: pass → fail ▼ security
- HSTS header: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 22 Sept 26 0
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 21 Sept 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 18 Sept 26 0
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 17 Sept 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 16 Sept 26 0
- Authorization: unverified → partial ▲ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ 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 5 Nov 2026 · Probed https://accessibility.groundlogic.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=accessibility.groundlogic.ai | CN=YE2,O=Let's Encrypt,C=US | 8 Sept 2026 | 7 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 54fbf630bf9afc9d6f2ac7088b414ce6a11 |
| SANs: accessibility.groundlogic.ai | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of accessibility.groundlogic.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| groundlogic.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 404 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://accessibility.groundlogic.ai/mcp | HTTP error | 404 | |
| http (plaintext) | http://accessibility.groundlogic.ai/mcp | HTTPS enforced | 301 | https://accessibility.groundlogic.ai:443/mcp |
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 →
generate_fixes ~99
Takes scan results and generates specific code fixes for each accessibility violation. Returns ready-to-apply code patches and a copy-paste summary for Claude Code or Replit Agent.
| Name | Type | Req | Description |
|---|---|---|---|
| anthropic_api_key | string | yes | Your Anthropic API key (used only for this request, never stored) |
| framework | string | – | The frontend framework of the codebase being fixed |
| scan_id | string | yes | The scan_id returned by scan_accessibility |
No output schema declared.
No examples provided.
generate_vpat ~189
Generates a complete VPAT 2.5 EN 301 549 accessibility conformance report based on scan results. Returns structured JSON and a downloadable PDF (base64-encoded). Covers all EN 301 549 clauses; non-web clauses are marked Not Evaluated with professional notes.
| Name | Type | Req | Description |
|---|---|---|---|
| anthropic_api_key | string | yes | Your Anthropic API key (used only for this request, never stored) |
| company_name | string | yes | Company or organization name |
| contact_email | string | yes | Contact email for accessibility questions |
| evaluation_date | string | – | Evaluation date (YYYY-MM-DD). Defaults to today. |
| notes | string | – | Additional context about the product or evaluation scope |
| product_name | string | yes | Name of the product being evaluated |
| product_version | string | – | Version of the product |
| scan_id | string | yes | The scan_id from scan_accessibility |
No output schema declared.
No examples provided.
re_verify ~84
Re-scans a URL after fixes have been applied and compares results against the original scan. Returns which violations were resolved, which persist, and any new issues introduced.
| Name | Type | Req | Description |
|---|---|---|---|
| anthropic_api_key | string | yes | Your Anthropic API key (used only for this request, never stored) |
| scan_id | string | yes | The original scan_id from scan_accessibility to compare against |
No output schema declared.
No examples provided.
scan_accessibility ~192
Scans a URL for WCAG 2.1 accessibility violations using DOM analysis (axe-core) and visual AI (Claude Vision). Returns structured violation data and a scan_id for use with other tools.
| Name | Type | Req | Description |
|---|---|---|---|
| anthropic_api_key | string | yes | Your Anthropic API key (used only for this request, never stored) |
| max_pages | integer | – | Maximum pages to scan when scan_depth is full_site |
| scan_depth | string | – | Whether to scan a single page or crawl the full site (max 10 pages) |
| url | string | yes | The URL to scan for accessibility violations |
| vision_mode | string | – | Vision analysis depth. 'standard' runs one Claude Vision pass on the full page (fast, default). 'thorough' analyzes the page section-by-section with a two-pass consensus to reduce false positives (sl… |
No output schema declared.
No examples provided.
How do I install the io.github.groundlogic-ai-source/accessibility-ai MCP server?
io.github.groundlogic-ai-source/accessibility-ai is a hosted endpoint at https://accessibility.groundlogic.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · accessibility.groundlogic.ai
claude mcp add --transport http groundlogic-ai-source-accessibility-ai 'https://accessibility.groundlogic.ai/mcp'
What is the io.github.groundlogic-ai-source/accessibility-ai MCP server?
io.github.groundlogic-ai-source/accessibility-ai is an MCP server listed in the public MCP registry as io.github.groundlogic-ai-source/accessibility-ai. Scan URLs for WCAG 2.1 violations, generate AI fixes, and produce VPAT 2.5 compliance reports. This page covers its hosted endpoint (https://accessibility.groundlogic.ai/mcp).
Is the io.github.groundlogic-ai-source/accessibility-ai MCP server safe to use?
io.github.groundlogic-ai-source/accessibility-ai scores 23 out of 100 on VerifyMCP. 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.groundlogic-ai-source/accessibility-ai MCP server expose?
io.github.groundlogic-ai-source/accessibility-ai exposes 4 tools: scan_accessibility, generate_fixes, re_verify, generate_vpat. Their descriptions and schemas cost roughly 564 tokens of context every time the server is loaded.
Does the io.github.groundlogic-ai-source/accessibility-ai MCP server require authentication?
Its publisher declares no required credentials for io.github.groundlogic-ai-source/accessibility-ai. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the io.github.groundlogic-ai-source/accessibility-ai MCP server still maintained?
io.github.groundlogic-ai-source/accessibility-ai is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.