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

com.overlayqa/mcp

NPM · @OVERLAYQA/MCP · SCANNED SEP 20

Run accessibility, contrast, and design token audits and file QA issues from your AI coding tool.

Available components

0 this week 78 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 34 of 106 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
Schema Quality & AI Usability79
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 690 tokens (~76/item across 9 items; 9 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
  • Stability observed for 27 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the com.overlayqa/mcp server?

com.overlayqa/mcp runs locally as an npm package, launched with npx -y @overlayqa/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @overlayqa/mcp

# add to Claude Code
claude mcp add com-overlayqa-mcp -- npx -y @overlayqa/mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "com-overlayqa-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@overlayqa/mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-overlayqa-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@overlayqa/mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add com-overlayqa-mcp -- npx -y @overlayqa/mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-overlayqa-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@overlayqa/mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-overlayqa-mcp --command npx --arg -y --arg @overlayqa/mcp
# ~/.hermes/config.yaml
mcp_servers:
  com-overlayqa-mcp:
    command: "npx"
    args: ["-y", "@overlayqa/mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-overlayqa-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@overlayqa/mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add com-overlayqa-mcp -t stdio -c npx -a -y @overlayqa/mcp
// mcp.json
{
  "mcpServers": {
    "com-overlayqa-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@overlayqa/mcp"
      ]
    }
  }
}
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.

  • 19 Sept 26 +1

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

  • 17 Sept 26 +1

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

  • 16 Sept 26 −3
    • Stability: pass → 0.77 functional
  • 15 Sept 26 0
    • Stability: 0.97 → pass security
  • 14 Sept 26 +1

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

  • 11 Sept 26 +1

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

  • 9 Sept 26 −2
    • Stability: pass → 0.80 functional
  • 8 Sept 26 0
    • Stability: 0.97 → pass security
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 20 Sept 2026 · Analysed npm/@overlayqa/mcp@0.1.7

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 106 packages
Packages resolved 106
Stale 34
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 9 exposed · ~690 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. 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 →

Tool Tokens
audit_tokens ~111

Audit a live URL's design-system token usage. Returns a 0-100 token-health score plus findings (inconsistent font sizes, text colors, spacing, font families, border radii) with severity and evidence. Audits the live page only; the figmaFileKey argument is accepted but Figma comparison is not yet available via MCP.

NameTypeReqDescription
figmaFileKeystringOptional Figma file key for token comparison
urlstringyesThe URL to audit for design token usage

No output schema declared.

No examples provided.

compare_visual ~106

Coming soon — not yet implemented; the server returns a not-implemented notice (use the OverlayQA browser extension for visual comparison today). Will compare a live URL against a Figma frame and return visual differences and a match score.

NameTypeReqDescription
figmaFileKeystringyesFigma file key (from the Figma URL)
figmaNodeIdstringyesFigma node ID of the frame to compare against
urlstringyesThe live URL to compare

No output schema declared.

No examples provided.

create_issue ~97

Create an issue in an OverlayQA project. Title is required; severity, type, and description default to medium / design-bug / empty.

NameTypeReqDescription
descriptionstringIssue description
projectIdstringyesProject to create the issue in
severitystringIssue severity (default: medium)
titlestringyesIssue title
typestringIssue type (default: design-bug)

No output schema declared.

No examples provided.

create_project ~51

Create a new OverlayQA project. Returns the project id, name, slug, displayPrefix, and url.

NameTypeReqDescription
namestringyesProject name
urlstringPrimary URL for this project

No output schema declared.

No examples provided.

list_issues ~55

List issues in a project, optionally filtered by status and severity.

NameTypeReqDescription
projectIdstringyesProject to list issues from
severitystringFilter by severity
statusstringFilter by status

No output schema declared.

No examples provided.

list_projects ~19

List all OverlayQA projects in the authenticated user's team.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

scan_accessibility ~80

Run an accessibility audit on a URL. Returns WCAG violations with severity, descriptions, and an overall score. Scans one page per call. Free plans include 3 scans per day; Pro is unlimited.

NameTypeReqDescription
projectIdstringOptional project ID to associate results with
urlstringyesThe URL to scan for accessibility issues

No output schema declared.

No examples provided.

scan_and_create_issues ~106

Run an accessibility scan on a URL and automatically create issues in the given project for each violation at or above the minimum severity. Returns scan summary + issue IDs created. Scans one page per call. Free plans include 3 scans per day; Pro is unlimited.

NameTypeReqDescription
minSeveritystringMinimum severity to create issues for (default: medium)
projectIdstringyesProject to create issues in
urlstringyesThe URL to scan

No output schema declared.

No examples provided.

scan_contrast ~65

Run a color contrast audit on a URL. Returns elements failing WCAG contrast ratios with severity and details. Scans one page per call. Free plans include 3 scans per day; Pro is unlimited.

NameTypeReqDescription
urlstringyesThe URL to scan for color contrast issues

No output schema declared.

No examples provided.

Common questions

What is the com.overlayqa/mcp server?

com.overlayqa/mcp is listed in the public MCP registry as com.overlayqa/mcp. Run accessibility, contrast, and design token audits and file QA issues from your AI coding tool. This page covers its npm package (@overlayqa/mcp).

Is the com.overlayqa/mcp server safe to use?

com.overlayqa/mcp scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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 com.overlayqa/mcp server expose?

com.overlayqa/mcp exposes 9 tools: scan_accessibility, scan_contrast, scan_and_create_issues, compare_visual, audit_tokens, and 4 more. Their descriptions and schemas cost roughly 690 tokens of context every time the server is loaded.

Is the com.overlayqa/mcp server still maintained?

com.overlayqa/mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the com.overlayqa/mcp server under?

com.overlayqa/mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.