Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

com.nexaaly/a11y-check

REMOTE · NEXAALY.COM · SCANNED AUG 3

Real-browser WCAG audit that also finds keyboard-inoperable controls axe-core misses, with fixes.

Available components

remote · nexaaly.com 68
68 Trust /100
Trust breakdown (6 categories)

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 →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 157 tokens (~157/item across 1 items; 1 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
  • Stability observed for 3 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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · nexaaly.com

# add to Claude Code
claude mcp add --transport http com-nexaaly-a11y-check https://nexaaly.com/mcp
# ~/.codex/config.toml
[mcp_servers.com-nexaaly-a11y-check]
url = "https://nexaaly.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-nexaaly-a11y-check": {
      "type": "remote",
      "url": "https://nexaaly.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-nexaaly-a11y-check --url https://nexaaly.com/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-nexaaly-a11y-check:
    url: "https://nexaaly.com/mcp"
// mcp.json
{
  "mcpServers": {
    "com-nexaaly-a11y-check": {
      "type": "http",
      "url": "https://nexaaly.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 3 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Aug 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 31 Jul 26 66

    First indexed and scored.

Diagnostics

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 3 Aug 2026 · Probed https://nexaaly.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=nexaaly.com CN=YE1,O=Let's Encrypt,C=US 16 Jul 2026 14 Oct 2026 ECDSA 256 ECDSA-SHA384 5648e7958340cb704e1edc6dccf365ce4a8
SANs: nexaaly.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
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
DNSSEC insecure

Validation of nexaaly.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
nexaaly.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://nexaaly.com/mcp Verified 200
http (plaintext) http://nexaaly.com/mcp HTTPS enforced 308 https://nexaaly.com/mcp
MCP tools — 1 exposed · ~157 tokens

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.

Tool Tokens
check_accessibility ~157

Audit one web page for accessibility problems using a real browser. Runs axe-core (WCAG 2.1 AA) plus checks that standard scanners do not perform: controls that look clickable but cannot be operated by keyboard, error messages not programmatically linked to their field, CAPTCHA barriers, duplicate main landmarks, and missing skip links. Returns findings WITH the code change that fixes each one. Use this when someone asks whether a site is accessible, whether it meets WCAG or the European Accessibility Act, or whether keyboard and screen-reader users can operate its controls.

NameTypeReqDescription
urlstringyesPage to check. A bare domain is fine ("example.com"). Prefer a product or checkout page over a homepage — that is where accessibility failures cost sales.

No output schema declared.

No examples provided.