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.

io.github.aimsise/color-engine-mcp

NPM · COLOR-ENGINE-MCP

Six pure, in-memory CSS color tools: parse, convert, WCAG/APCA contrast, gamut map, ramps, solver

Available components

0 this week 77 Trust /100

Last scanned (16 hours ago)

Scores higher than 56% of npm servers

Category Design and Media

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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 1.29.0, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 31 of 94 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability66
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1601 tokens (~266/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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.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 7 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 21 Nov 26 0
    • Stability: 0.97 → pass security
  • 20 Nov 26 0
    • Security disclosure: unverified → fail ▼ functional
    • Stability: pass → 0.97 functional
  • 19 Nov 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 14 Nov 26 0
    • Stability: 0.97 → pass security
  • 13 Nov 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.

  • 12 Nov 26 −1
    • Stability: pass → 0.93 functional
  • 6 Nov 26 0
    • Stability: 0.97 → pass security
  • 5 Nov 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.

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 21 Nov 2026 · Analysed npm/color-engine-mcp@1.0.1

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 8 findings
ID CVE Severity Vector Fix available
GHSA-rmxm-3fg6-px4f CVE-2026-118663 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N yes
GHSA-22jm-h49p-29qw CVE-2026-111767 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L yes
GHSA-46jr-4wx8-v453 CVE-2026-111768 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-6prh-2h8m-c8cw CVE-2026-111769 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N yes
GHSA-6qxp-vccf-f47h CVE-2026-104850 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N yes
GHSA-f897-62hf-6gxq high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-rvq5-wwqv-78pq CVE-2026-111771 medium CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N yes
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 94 packages
Packages resolved 94
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~1,331 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
contrast ~186

Compute the WCAG 2.1 contrast ratio between two fully opaque CSS color strings and return WCAG tier flags (AA/AAA normal/large text). Set apca:true to also get the signed APCA-W3 Lc for text `a` over background `b`.

NameTypeReqDescription
astringyesFirst CSS color string, e.g. "#000000", "black", "oklch(0 0 0)" (max 256 chars)
apcaboolean–When true, additionally compute the APCA-W3 (SAPC-4g) lightness contrast Lc for text `a` over background `b` (returned as `apcaLc`)
bstringyesSecond CSS color string, e.g. "#ffffff", "white", "oklch(1 0 0)" (max 256 chars)
NameTypeReqDescription
aaLargebooleanyesMeets WCAG 2.1 AA for large text (raw ratio >= 3)
aaNormalbooleanyesMeets WCAG 2.1 AA for normal text (raw ratio >= 4.5)
aaaLargebooleanyesMeets WCAG 2.1 AAA for large text (raw ratio >= 4.5)
aaaNormalbooleanyesMeets WCAG 2.1 AAA for normal text (raw ratio >= 7)
apcaLcnumber–Signed APCA-W3 (SAPC-4g) Lc for text `a` over background `b`, rounded to 2 decimals (positive = dark-on-light, negative = light-on-dark); present only when input `apca` is true
rationumberyes2-decimal display value; tier flags derive from the unrounded raw ratio

No examples provided.

convert_color ~75

Convert a CSS color string into a canonical hex, rgb, hsl, or oklch format string.

NameTypeReqDescription
inputstringyesCSS color string to convert, e.g. "#ff0000", "tomato" (max 256 chars)
tostringyesTarget color format to convert the input into
NameTypeReqDescription
resultstringyesThe input color formatted in the requested target format (oklch is raw/lossless; hex/rgb/hsl are sRGB-clamped for out-of-gamut inputs)

No examples provided.

gamut_map ~99

Map any CSS color string into the sRGB gamut via perceptual OKLCH chroma reduction. Returns the nearest in-gamut hex, raw OKLCH components, and a `clamped` flag indicating whether the input was out-of-gamut.

NameTypeReqDescription
inputstringyesAny CSS color string, e.g. "#ff0000", "oklch(0.6 0.4 30)" (max 256 chars)
NameTypeReqDescription
clampedbooleanyestrue when input was out-of-sRGB-gamut and was mapped
hexstringyesLowercase #rrggbb of the gamut-mapped (in-sRGB) color
oklchobjectyesRaw (pre-rounding) OKLCH components of the mapped result

No examples provided.

generate_ramp ~347

Generate a tint-to-shade color ramp from a base CSS color. Returns an ordered list of swatches (light → dark) each with its in-gamut hex, display-rounded OKLCH components (l/c 5dp, h 2dp), WCAG contrast ratios (2dp) + tiers vs white and black, and an in-gamut flag. Optionally emits the ramp as design tokens via tokenFormat ("tailwind" JSON or a "css-variables" :root block).

NameTypeReqDescription
basestringyesAny CSS color string, e.g. "#3b82f6", "oklch(0.6 0.35 30)" (max 256 chars)
deltaLnumber–Total lightness span (> 0) centered on the base L — endpoints at base L ± deltaL/2 (overrides the fixed range).
lightnessMaxnumber–Upper lightness endpoint (OKLCH L, 0..1). Default 0.97.
lightnessMinnumber–Lower lightness endpoint (OKLCH L, 0..1). Default 0.05.
stepsinteger–Number of swatches (integer 2..512). Default 5.
tokenFormatstring–Optional design-token format for the ramp ("tailwind" JSON object or a "css-variables" :root block); when present the output includes a `tokens` string.
tokenNamestring–Base name for emitted tokens (letters/digits/hyphens, must start with a letter, 1-64 chars). Default "color".
NameTypeReqDescription
swatchesarrayyes–
tokensstring–Design-token string for the ramp (pretty-printed Tailwind JSON or a :root CSS-variables block); present only when tokenFormat was supplied

No examples provided.

parse_color ~70

Parse a CSS color string and return hex, rgb, oklch, and gamut info.

NameTypeReqDescription
inputstringyesCSS color string, e.g. "tomato", "#ff6347", "oklch(0.6 0.18 27)" (max 256 chars)
NameTypeReqDescription
hexstringyesLowercase #rrggbb sRGB-clamped hex of the parsed color
inGamutbooleanyesfalse when the input fell outside the sRGB gamut
oklchobjectyesRaw (lossless) OKLCH components of the parsed color
rgbobjectyessRGB-clamped 0-255 integer channels; see inGamut

No examples provided.

solve_for_contrast ~554

Find a foreground color that meets one or more WCAG 2.1 contrast targets against a background. Binary-searches OKLCH lightness (holding hue/chroma fixed) and returns the nearest-compliant hex plus the achieved ratio. Pass `target` for one target or `targets` for several; `prefer` selects lighter/darker/either; `hue`/`chroma` pin the foreground chromaticity. If BOTH `target` and `targets` are provided, `targets` takes precedence. The response shape differs by mode: a single `target` returns `{ met, color, ratio }` (with an optional `nearMiss` flag); `targets` returns `{ results: [{ met, color, ratio, nearMiss? }, ...] }`. The output schema is an all-optional superset of both shapes (SDK 1.29 single-shape limitation). An unparseable background returns the PARSE_FAILED error; a translucent background (alpha < 1, e.g. rgba()/hsla()/#rgba/#rrggbbaa) returns ALPHA_UNSUPPORTED — composite it over its backdrop first.

NameTypeReqDescription
backgroundstringyesBackground CSS color string, e.g. "#FFFFFF", "oklch(0.6 0.1 240)" (max 256 chars).
chromanumber–Fixed OKLCH chroma (>= 0) held constant during the lightness search (reduced along the fixed hue when the sRGB gamut requires it). Defaults to the background's own chroma when omitted; pass chroma ex…
huenumber–Fixed OKLCH hue (degrees, cyclic) held constant during the lightness search. Giving hue WITHOUT chroma does not add saturation: chroma then defaults to the background's own chroma, which is 0 for ach…
preferstring–Search direction relative to the background lightness. Default "either".
targetnumber–Single WCAG 2.1 contrast target (e.g. 4.5, 7). Use this OR `targets` (targets wins if both given).
targetsarray–Multiple WCAG 2.1 contrast targets (1-50 entries; an empty array is rejected). Takes precedence over `target`. Returns one result per target.
NameTypeReqDescription
color––SINGLE-target: nearest-compliant foreground hex, or null when unreachable
metboolean–SINGLE-target: whether the target contrast was achievable
nearMissboolean–SINGLE-target: present/true when met was granted via the near-ceiling tolerance
ratio––SINGLE-target: achieved WCAG 2.1 ratio (display-rounded), or peak attainable when not met
resultsarray–MULTI-target: one result per requested target (present only for the `targets` path)

No examples provided.

Install

How do I install the io.github.aimsise/color-engine-mcp server?

io.github.aimsise/color-engine-mcp runs locally as an npm package, launched with npx -y color-engine-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 · color-engine-mcp

# add to Claude Code
claude mcp add aimsise-color-engine-mcp -- npx -y color-engine-mcp
Common questions

What is the io.github.aimsise/color-engine-mcp server?

io.github.aimsise/color-engine-mcp is listed in the public MCP registry as io.github.aimsise/color-engine-mcp. Six pure, in-memory CSS color tools: parse, convert, WCAG/APCA contrast, gamut map, ramps, solver. This page covers its npm package (color-engine-mcp).

Is the io.github.aimsise/color-engine-mcp server safe to use?

io.github.aimsise/color-engine-mcp scores 77 out of 100 on VerifyMCP. We recorded 8 known advisories against it as of 21 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.aimsise/color-engine-mcp server expose?

io.github.aimsise/color-engine-mcp exposes 6 tools: parse_color, convert_color, contrast, gamut_map, generate_ramp, solve_for_contrast. Their descriptions and schemas cost roughly 1,331 tokens of context every time the server is loaded.

Is the io.github.aimsise/color-engine-mcp server still maintained?

io.github.aimsise/color-engine-mcp is still listed as active in the MCP registry. We last reached this channel on 21 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.aimsise/color-engine-mcp server under?

io.github.aimsise/color-engine-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.

What did VerifyMCP test on the io.github.aimsise/color-engine-mcp server?

VerifyMCP ran 16 checks on io.github.aimsise/color-engine-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.