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.

color-space

NPM · COLOR-SPACE

Conversions across 221 color spaces, tested against cited sources: CSS strings, gamut, LUTs

Available components

+4 this week 88 Trust /100

Last scanned (12 hours ago)

Scores higher than 92% 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 Security100
  • 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
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency84
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to colorjs/color-space). View diagnostics → Pass
  • License check failed: the license (CC0-1.0) isn't a recognized OSI-approved license. See how to fix → Fail
  • Actively maintained (last published 15 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability73
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 2114 tokens (~211/item across 10 items; 9 tools + 1 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 Management70
  • Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 93% of tool parameters carry a description.Partial
  • Structured output schemas are declared (89% 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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
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.

  • 5 Nov 26 +1

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

  • 3 Nov 26 +1

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

  • 1 Nov 26 +1

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

  • 30 Oct 26 +1

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

  • 28 Oct 26 +1

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

  • 26 Oct 26 +1

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

  • 23 Oct 26 +1

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

  • 21 Oct 26 +16
    • Malware scan: unverified → 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 5 Nov 2026 · Analysed npm/color-space@3.5.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo colorjs/color-space
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/colorjs/color-space/.github/workflows/release.yml@refs/heads/master
Rekor log index 3329550998
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:8dd24dfc3d19806b566719c54f9c6904e25a5f7a9d2b3cf213bf0ef297f32901af73157d8858abe7005a172dc03a637e465ae4b54fe1edcf9e6f54a79

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 9 exposed · ~1,896 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
code ~262

The conversion as code to paste: the color-space JS call with its result and – where one exists for the space on the non-sRGB side – the colour-science (Python) equivalent verified against color-space (sRGB ↔ that space), with any named caveat. The color goes in as a CSS string or as values in `from` (default: sRGB 200, 100, 50).

NameTypeReqDescription
colorstring–a CSS color instead of `from` + `values`: '#ff8000', 'rebeccapurple', 'oklch(0.7 0.1 50)', 'lab(54% 80 67)', 'color(display-p3 1 0.5 0)'
fromstring–source space id, e.g. 'rgb', 'oklch', 'lab', 'slog3', 'rec709' (the 'spaces' tool lists all 221)
tostringyestarget space id, e.g. 'rgb', 'oklch', 'lab', 'slog3', 'rec709' (the 'spaces' tool lists all 221)
valuesarray–the color in the source space
NameTypeReqDescription
jsstringyes–
pythonstring|nullyes–
pythonForstring|nullyes–

No examples provided.

convert ~387

Convert a color between any two of the 221 color spaces, identity included, in each space's conventional ranges (rgb 0-255, oklch L 0-1 / C 0-0.4 / H 0-360, lab L 0-100 …). The color goes in as a CSS string (`color`) or as channel values (`from` + `values`); a batch as `colors` – tuples in `from`, CSS strings, or both. Out-of-range in, unclamped out: `inRange` flags each channel against the target's conventional range (rgb below 0 means outside sRGB); null = undefined at that coordinate.

NameTypeReqDescription
colorstring–a CSS color instead of `from` + `values`: '#ff8000', 'rebeccapurple', 'oklch(0.7 0.1 50)', 'lab(54% 80 67)', 'color(display-p3 1 0.5 0)'
colorsarray–a batch: one tuple (in `from`) or CSS string per color, e.g. [[255, 128, 0], '#00ff80', 'oklch(0.7 0.1 50)']
fromstring–source space id, e.g. 'rgb', 'oklch', 'lab', 'slog3', 'rec709' (the 'spaces' tool lists all 221)
tostringyestarget space id, e.g. 'rgb', 'oklch', 'lab', 'slog3', 'rec709' (the 'spaces' tool lists all 221)
valuesarray–one color in the source space, e.g. [255, 128, 0] for rgb
NameTypeReqDescription
channelsarrayyes–
colorsarrayyes–
fromstring––
tostringyes–

No examples provided.

css ~272

A color as CSS Color 4 strings — rgb(), hsl(), hwb(), lab(), lch(), oklab(), oklch() and color(display-p3 | a98-rgb | prophoto-rgb | rec2020 | srgb-linear | xyz-d65 | xyz-d50) — plus #hex inside sRGB. Converted, never gamut-mapped: a string is null where CSS would clamp it into a different color (rgb/hsl/hwb outside sRGB, lightness out of range). `gamut` is the smallest display gamut that holds the color.

NameTypeReqDescription
colorstring–a CSS color instead of `from` + `values`: '#ff8000', 'rebeccapurple', 'oklch(0.7 0.1 50)', 'lab(54% 80 67)', 'color(display-p3 1 0.5 0)'
fromstring–source space id, e.g. 'rgb', 'oklch', 'lab', 'slog3', 'rec709' (the 'spaces' tool lists all 221)
notationsarray–only these, by library space id (default: all)
valuesarray–one color in the source space
NameTypeReqDescription
cssarrayyes–
gamutstring|nullyes–
hexstring|nullyes–

No examples provided.

cube ~174

Render a conversion as a .cube LUT file (Resolve, Premiere, Final Cut, OBS, ffmpeg). The header carries the measured deviation vs the direct conversion. Pure per-channel transfers auto-emit 1D. Size ≤ 33 here (larger via the library or https://color-space.io/).

NameTypeReqDescription
fromstringyessource space id, e.g. 'rgb', 'oklch', 'lab', 'slog3', 'rec709' (the 'spaces' tool lists all 221)
sizeinteger–3D lattice size (default 17)
tostringyestarget space id, e.g. 'rgb', 'oklch', 'lab', 'slog3', 'rec709' (the 'spaces' tool lists all 221)

No output schema declared.

No examples provided.

gamut ~211

Which standard display gamuts hold a color — sRGB ⊂ Display P3 ⊂ Rec. 2020, each tested in its own RGB box straight from the source space, the same ladder as the color-space.io gamut pill. `smallest` is the tightest one; null = beyond Rec. 2020. Membership only: nothing is gamut-mapped.

NameTypeReqDescription
colorstring–a CSS color instead of `from` + `values`: '#ff8000', 'rebeccapurple', 'oklch(0.7 0.1 50)', 'lab(54% 80 67)', 'color(display-p3 1 0.5 0)'
fromstring–source space id, e.g. 'rgb', 'oklch', 'lab', 'slog3', 'rec709' (the 'spaces' tool lists all 221)
valuesarray–one color in the source space
NameTypeReqDescription
gamutsarrayyes–
smalleststring|nullyes–

No examples provided.

icc ~157

One space as an ICC v2 profile (.icc): matrix + tone curve where the space is an RGB working space (Photoshop, OS color management), a CLUT on a Lab PCS otherwise (lcms, ArgyllCMS, ImageMagick). Returned as a base64 embedded resource; `class`, `pcs` and `bytes` describe it.

NameTypeReqDescription
gridinteger–CLUT lattice points per channel, CLUT profiles only (default 33 for 3 channels; fewer = a smaller file)
namestringyesthe space id, e.g. 'rgb', 'oklch', 'lab', 'slog3', 'rec709' (the 'spaces' tool lists all 221)
NameTypeReqDescription
bytesintegeryes–
classstringyes–
filestringyes–
namestringyes–
pcsstringyes–

No examples provided.

shader ~235

The conversion as shader source – GLSL (WebGL2; WebGL1 too unless the path reads a table), WGSL (WebGPU), HLSL (DirectX, Unity, Unreal) or MSL (Metal) – with an entry function `<from>_<to>` (hyphens stripped), e.g. `vec3 rgb_oklch(vec3 c)`, plus every function on the path. Each language is differentially tested against the library and compiled on real GPUs: use it instead of writing color matrices. HLSL and MSL need the optional peer `naga-wasm` installed beside color-space.

NameTypeReqDescription
fromstringyessource space id, e.g. 'rgb', 'oklch', 'lab', 'slog3', 'rec709' (the 'spaces' tool lists all 221)
languagestring–default glsl
tostringyestarget space id, e.g. 'rgb', 'oklch', 'lab', 'slog3', 'rec709' (the 'spaces' tool lists all 221)
NameTypeReqDescription
codestringyes–
entrystringyes–
languagestringyes–

No examples provided.

space ~102

The dossier of one color space: display name (as color-space.io shows it), description, channels + conventional ranges, defining references, provenance (year, author), illuminant/observer, encoding class, family and purpose, and its direct conversion neighbours.

NameTypeReqDescription
namestringyesthe space id, e.g. 'rgb', 'oklch', 'lab', 'slog3', 'rec709' (the 'spaces' tool lists all 221)
NameTypeReqDescription
channelsarrayyes–
familystringyes–
namestringyes–
neighborsarrayyes–
purposearrayyes–
sourcestringyes–
titlestringyes–

No examples provided.

spaces ~96

List the 221 color spaces with display name, family, purpose, channels and one-line use. Optional filters: `query` (words matched against id, name, use line and description; best matches first), `family`, `purpose`.

NameTypeReqDescription
familystring––
purposestring––
querystring–free text, e.g. 'camera log', 'cielab', 'display p3'
NameTypeReqDescription
countintegeryes–
spacesarrayyes–

No examples provided.

Install

How do I install the color-space MCP server?

color-space runs locally as an npm package, launched with npx -y color-space. 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-space

# add to Claude Code
claude mcp add colorjs-color-space -- npx -y color-space
Common questions

What is the color-space MCP server?

color-space is an MCP server listed in the public MCP registry as io.github.colorjs/color-space. Conversions across 221 color spaces, tested against cited sources: CSS strings, gamut, LUTs. This page covers its npm package (color-space).

Is the color-space MCP server safe to use?

color-space scores 88 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 color-space MCP server expose?

color-space exposes 9 tools: convert, gamut, css, space, spaces, and 4 more. Their descriptions and schemas cost roughly 1,896 tokens of context every time the server is loaded.

Is the color-space MCP server still maintained?

color-space 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 color-space MCP server under?

color-space declares the CC0-1.0 licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.