io.github.socraticstatic/chart-color-audit
NPM · CHART-COLOR-AUDIT · SCANNED SEP 21
CI-friendly accessibility audit for chart color palettes: WCAG contrast, CVD simulation, OKLab ΔE.
Available components
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
- 31 of 97 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to socraticstatic/chart-color-audit). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 35 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
- Tool/resource definitions use about 245 tokens (~122/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 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
How do I install the io.github.socraticstatic/chart-color-audit MCP server?
io.github.socraticstatic/chart-color-audit runs locally as an npm package, launched with npx -y chart-color-audit. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · chart-color-audit
claude mcp add socraticstatic-chart-color-audit -- npx -y chart-color-audit
{
"mcpServers": {
"socraticstatic-chart-color-audit": {
"command": "npx",
"args": [
"-y",
"chart-color-audit"
]
}
}
} {
"servers": {
"socraticstatic-chart-color-audit": {
"command": "npx",
"args": [
"-y",
"chart-color-audit"
]
}
}
} codex mcp add socraticstatic-chart-color-audit -- npx -y chart-color-audit
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"socraticstatic-chart-color-audit": {
"type": "local",
"command": [
"npx",
"-y",
"chart-color-audit"
],
"enabled": true
}
}
} openclaw mcp add socraticstatic-chart-color-audit --command npx --arg -y --arg chart-color-audit
mcp_servers:
socraticstatic-chart-color-audit:
command: "npx"
args: ["-y", "chart-color-audit"] {
"McpServers": {
"socraticstatic-chart-color-audit": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"chart-color-audit"
]
}
}
} assistant mcp add socraticstatic-chart-color-audit -t stdio -c npx -a -y chart-color-audit
{
"mcpServers": {
"socraticstatic-chart-color-audit": {
"command": "npx",
"args": [
"-y",
"chart-color-audit"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 18 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.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 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 +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.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 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 21 Sept 2026 · Analysed npm/chart-color-audit@0.2.4
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 | socraticstatic/chart-color-audit |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/socraticstatic/chart-color-audit/.github/workflows/release.yml@refs/tags/v0.2.4 |
| Rekor log index | 2489844079 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:31a153185ff7c9bcfb992454283a7cd12fb9a16a598a9086137063310ffeb5ff5893e8004c51c81bb11e765d1329f359af36012ca190f5e96c9df6943 |
Background: How many MCP packages publish verified provenance →
Dependencies 97 packages
| Packages resolved | 97 |
|---|---|
| Stale | 31 |
| 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 →
audit_palette Audit a chart color palette ~180
Audit chart colors for accessibility: pairwise OKLab ΔE separation under normal vision, deuteranopia, protanopia, tritanopia (published Machado 2009 matrices) and grayscale, plus WCAG 2.2 SC 1.4.11 non-text contrast (≥3:1) against the background. Returns per-vision findings with human-word bands and a pass/fail verdict with reasons.
| Name | Type | Req | Description |
|---|---|---|---|
| background | string | yes | Background color the chart marks render on. |
| colors | array | yes | Palette colors in slot order — any CSS color syntax (#hex, hsl(), rgb(), named). |
| mode | string | – | Floors preset. perceptual (default) fails what an eye can't tell apart (ΔE<2); redundant-encodings for palettes paired with dash/decal/shape channels; strict demands clear separation. |
No output schema declared.
No examples provided.
audit_tokens Audit chart tokens from a config file ~65
Run the same audit against a chartaudit.config.json on disk — the config names a CSS or design-tokens file plus which tokens are the categorical palette, background, and semantic roles.
| Name | Type | Req | Description |
|---|---|---|---|
| config_path | string | yes | Absolute or cwd-relative path to chartaudit.config.json. |
No output schema declared.
No examples provided.
What is the io.github.socraticstatic/chart-color-audit MCP server?
io.github.socraticstatic/chart-color-audit is an MCP server listed in the public MCP registry as io.github.socraticstatic/chart-color-audit. CI-friendly accessibility audit for chart color palettes: WCAG contrast, CVD simulation, OKLab ΔE. This page covers its npm package (chart-color-audit).
Is the io.github.socraticstatic/chart-color-audit MCP server safe to use?
io.github.socraticstatic/chart-color-audit scores 94 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 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 io.github.socraticstatic/chart-color-audit MCP server expose?
io.github.socraticstatic/chart-color-audit exposes 2 tools: audit_palette, audit_tokens. Their descriptions and schemas cost roughly 245 tokens of context every time the server is loaded.
Is the io.github.socraticstatic/chart-color-audit MCP server still maintained?
io.github.socraticstatic/chart-color-audit is still listed as active in the MCP registry. We last reached this channel on 21 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 io.github.socraticstatic/chart-color-audit MCP server under?
io.github.socraticstatic/chart-color-audit declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.