Overlayrisk Witness

io.github.mertcanvuralPublished by GitHub account mertcanvuralv0.1.0Updated Oct 24, 2026

Independent before/after accessibility-overlay (accessiBe/UserWay) witness for any public URL.

VerifiedSTDIODesktop onlyWeb Search & ScrapingDeveloper Tools

Overview

AI-generated overview

A local MCP server that runs a free, independent before/after accessibility-overlay witness on a public URL and returns one documented finding.

What you can do
Run a witness on a public page URL, loading it with the overlay on and off and capturing both states through a hosted API that does the detection and claim extraction. Receive the free-witness result: run ID, site URL, overlay vendor, pages and claims tested, which claims did not hold up, one free finding, and a count of locked findings. Get structured error codes such as overlay_no_effect, page_fetch_failed or witness_timeout. The server is a thin client with no scanning logic of its own.
When to use it
Useful when you want an assistant to check whether an accessibility overlay widget (accessiBe, UserWay or similar) actually changes a public page for assistive-technology users, and to get a timestamped evidence finding rather than a compliance ruling.
Requirements
Runs locally over stdio, typically via npx with the npm package overlayrisk-witness-mcp. Needs network access to the hosted witness endpoint. No API key is required. Optional environment variables OVERLAYRISK_API_URL (endpoint override) and OVERLAYRISK_TIMEOUT_MS (default 200000). A run can take up to about 3 minutes, so clients without progress-based timeout reset should raise their request timeout.
Before you install
The single tool sends the submitted public URL to a third-party hosted service for scanning. Findings are evidence, not a legal compliance ruling. The full timestamped Risk Packet is a paid checkout on the website; the server itself never handles payment. The server is described as independent of accessiBe and UserWay.

Installation

In SourceWeft

  1. Open Overlayrisk Witness in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

OverlayRiskWitness MCP server

A Model Context Protocol server that runs the free, independent before/after accessibility-overlay witness from OverlayRiskWitness on any public URL.

Accessibility overlay widgets (accessiBe, UserWay, and similar) are sold as one-line ADA/WCAG compliance fixes, but independent testing routinely shows the underlying page is unchanged for real assistive-technology users. This server lets an AI agent run the witness: it loads a page with the overlay on, then off, captures both states, and returns one documented finding where the page's public accessibility/compliance claims don't hold up — with a UTC timestamp.

Findings are evidence, not a legal compliance ruling. This server is independent of accessiBe and UserWay; it tests their effect, it does not sell or defend an overlay.

What this server is (and isn't)

This is a thin client. It contains no scanning logic and no secrets. Its single tool POSTs to the hosted API at https://overlayrisk.com/api/witness, which does the real work (overlay detection, headless before/after capture, claim extraction). The full timestamped Risk Packet is a paid checkout on the website — see overlayrisk.com/pricing. The MCP server is a free funnel; it never handles payment.

Tool

witness_page

Input{ "url": "https://example.com/checkout" } — a public HTTP/HTTPS page URL
SuccessThe free-witness JSON: runId, siteUrl, overlayVendor (accessibe/userway), pagesTested, claimsTested, didNotHoldUp, freeFinding, lockedFindingCount — plus a note linking to the paid Risk Packet
Error{ status, code, error } (e.g. overlay_no_effect, page_fetch_failed, witness_timeout)

A single witness run can take up to ~3 minutes on cold/heavy sites. That exceeds many MCP clients' default 60s request timeout. The server emits periodic progress notifications, so clients that honor resetTimeoutOnProgress stay connected automatically; clients that don't should raise their per-request timeout.

Install

Run directly with npx (no global install):

bash
npx overlayrisk-witness-mcp

The process speaks MCP over stdio.

Claude Desktop / Cursor / other MCP clients

Add to your client's MCP config:

json
{  "mcpServers": {    "overlayrisk-witness": {      "command": "npx",      "args": ["-y", "overlayrisk-witness-mcp"]    }  }}

Configuration

Env varDefaultPurpose
OVERLAYRISK_API_URLhttps://overlayrisk.com/api/witnessOverride the witness endpoint (e.g. for local dev)
OVERLAYRISK_TIMEOUT_MS200000Request timeout in ms

No API key is required — the free one-page witness is public.

Develop

bash
npm installnpm run smoke   # offline handshake test (lists tools, no network)npm start       # run the server on stdio

License

MIT © Mert Can Vural

Source: README.md at commit 3dd25b7

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts