io.github.vince-gonzalez/cvdsafe
NPM · CVDSAFE-MCP
Check if a palette or image is colorblind-safe, generate safe palettes, check WCAG contrast.
Available components
Last scanned (51 minutes ago)
Scores higher than 53% of npm servers
Category Design and Media
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 32 of 97 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 63 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 756 tokens (~126/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
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.
- 5 Nov 26 −3
- Stability: pass → 0.80 functional
- 30 Oct 26 0
- Stability: 0.97 → pass security
- 29 Oct 26 0
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 23 Oct 26 0
- Stability: 0.97 → pass security
- 22 Oct 26 0
- Stability: pass → 0.97 functional
- 16 Oct 26 0
- Stability: 0.97 → pass security
- 15 Oct 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.
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 · Analysed npm/cvdsafe-mcp@0.2.0
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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 97 packages
| Packages resolved | 97 |
|---|---|
| Stale | 32 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
checkContrast Check text/background contrast against WCAG ~131
Check whether a foreground color is legible on a background color per WCAG 2.x contrast ratios. Returns the ratio (1-21) and whether it passes AA and AAA. Set large=true for text >=18pt (or 14pt bold). This is the legibility axis, separate from color-blindness.
| Name | Type | Req | Description |
|---|---|---|---|
| background | string | yes | Background hex color, e.g. #ffffff |
| foreground | string | yes | Text/foreground hex color, e.g. #767676 |
| large | boolean | – | True if text is >=18pt or 14pt bold (default false) |
No output schema declared.
No examples provided.
checkImage Check an image for colorblind-safety ~265
Check whether the colors in an image, chart, screenshot or mockup stay distinguishable for people with color-vision deficiency. Extracts the image's dominant colors, simulates protanopia, deuteranopia and tritanopia, and flags the color pairs that collapse into each other — each with how much of the image's area those colors cover, so a conflict between two large regions ranks above one between two specks. Reads PNG and JPEG. Pass `path` for a local file, or a base64 `dataUri`. Set returnSimulated=true to also get back the image as a deuteranope sees it. A screening aid, not a legal (ADA/WCAG) audit.
| Name | Type | Req | Description |
|---|---|---|---|
| dataUri | string | – | Base64 data URI of the image, if you don't have a file path |
| maxColors | integer | – | How many dominant colors to extract and test (default 12) |
| path | string | – | Path to a local PNG or JPEG file, e.g. ./dashboard.png |
| returnSimulated | boolean | – | Also return the image recolored as a deuteranope sees it (default false) |
| simulateType | string | – | Which deficiency to render when returnSimulated is set (default deutan) |
No output schema declared.
No examples provided.
checkPalette Check a color palette for colorblind-safety ~103
Check whether a set of colors stays distinguishable for people with color-vision deficiency (colorblindness). Simulates protanopia, deuteranopia and tritanopia and flags the pairs whose perceptual difference collapses under simulation. A screening aid, not a legal accessibility (ADA/WCAG) audit.
| Name | Type | Req | Description |
|---|---|---|---|
| colors | array | yes | Hex colors to check together, e.g. ["#d7191c","#1a9641","#2166ac"] |
No output schema declared.
No examples provided.
fixPalette Fix a palette to be colorblind-safe ~97
Take a set of colors that fails the colorblind-safety check and return an adjusted set that passes, staying as close to the originals as possible. Conflicting colors are separated in lightness (the axis color-vision deficiency preserves). Returns the new colors, how far each moved, and whether it fully passes.
| Name | Type | Req | Description |
|---|---|---|---|
| colors | array | yes | Hex colors to fix, e.g. ["#d7191c","#1a9641"] |
No output schema declared.
No examples provided.
generateSafePalette Generate a colorblind-safe palette ~95
Return N colorblind-safe hex colors — distinct to each other under protanopia, deuteranopia and tritanopia. Seeded with the Okabe-Ito palette and safely extended above eight. Use when asked for accessible / colorblind-safe / colorblind-friendly colors for a chart, plot, map or UI. Never returns an unsafe color.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | How many colorblind-safe colors to return |
No output schema declared.
No examples provided.
simulateColor Simulate a color under colorblindness ~65
Return how a single hex color appears to someone with a given type of color blindness (protan, deutan, or tritan).
| Name | Type | Req | Description |
|---|---|---|---|
| color | string | yes | Hex color, e.g. #d7191c |
| type | string | yes | Color-vision deficiency type |
No output schema declared.
No examples provided.
How do I install the io.github.vince-gonzalez/cvdsafe MCP server?
io.github.vince-gonzalez/cvdsafe runs locally as an npm package, launched with npx -y cvdsafe-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 · cvdsafe-mcp
claude mcp add vince-gonzalez-cvdsafe -- npx -y cvdsafe-mcp
What is the io.github.vince-gonzalez/cvdsafe MCP server?
io.github.vince-gonzalez/cvdsafe is an MCP server listed in the public MCP registry as io.github.vince-gonzalez/cvdsafe. Check if a palette or image is colorblind-safe, generate safe palettes, check WCAG contrast. This page covers its npm package (cvdsafe-mcp).
Is the io.github.vince-gonzalez/cvdsafe MCP server safe to use?
io.github.vince-gonzalez/cvdsafe scores 76 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 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 io.github.vince-gonzalez/cvdsafe MCP server expose?
io.github.vince-gonzalez/cvdsafe exposes 6 tools: checkPalette, simulateColor, fixPalette, checkContrast, checkImage, generateSafePalette. Their descriptions and schemas cost roughly 756 tokens of context every time the server is loaded.
Is the io.github.vince-gonzalez/cvdsafe MCP server still maintained?
io.github.vince-gonzalez/cvdsafe 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.
What licence is the io.github.vince-gonzalez/cvdsafe MCP server under?
io.github.vince-gonzalez/cvdsafe declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.