_ registry / mcp http-sse · checked 6h ago

chart-color-system

https://chart-color-mcp.vercel.app

Registry code: fe9936245bee7f71

api record

The Chart Color System solves, audits and simulates chart color palettes: categorical palettes that stay distinguishable under normal vision and colorblindness (deuteranopia, protanopia, tritanopia, achromatopsia), with WCAG non-text contrast against the chart background. Use solve_palette when the user needs colors (pass brand colors as anchors; they are kept exactly, in slot order). Use audit_palette to judge colors they already have. Use simulate_palette to show what a colorblind reader sees. Use build_ramp for sequential or diverging scales. Numbers are OKLab distances and WCAG contrast…

endpoint
https://chart-color-mcp.vercel.app/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is chart-color-system live?
No — it has stopped answering the hub's checks (checked 6h ago). It answered 99% of checks over the last 30 days.
Is chart-color-system free to use?
Yes — the hub reached it with no key and no payment.
What tools does chart-color-system have?
4 tools: audit_palette, simulate_palette, build_ramp, solve_palette.
Is chart-color-system safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
down
uptime, 30 days
98.6%

90 days 99.1%· all time 99.1%

latency
206ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 540 checks · signed record
  • degraded → down· timeout after 20000ms
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • generate colorblind-safe chart palette
  • audit chart colors for accessibility
  • simulate colorblind vision
  • build a color ramp
takes → gives
data → data
tools
4 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
1 open 3 never probed 1 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • solve_palette reads open 2d ago

    Generate a categorical chart palette of n colors (1-12) that maximizes perceptual separation under normal vision and colorblindness, with the given brand colors locked as anchors in slot order. Returns the palette, the worst pair distances, the engine's relaxation notes, a full accessibility audit against the background, and a link to open it in the app. Honest cap is 6 slots; above that the result says so.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "n": {
          "type": "integer",
          "default": 6,
          "maximum": 12,
          "minimum": 1,
          "description": "Number of categorical slots"
        },
        "grid": {
          "type": "string",
          "description": "Gridline color; defaults to a light or dark gray to match the background"
        },
        "anchors": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "default": [],
          "maxItems": 12,
          "description": "Brand or required colors, kept exactly, in slot order (CSS syntax)"
        },
        "posture": {
          "enum": [
            "kpi",
            "comparative",
            "exploratory"
          ],
          "type": "string",
          "default": "comparative",
          "description": "kpi: few strong colors; comparative: balanced; exploratory: many muted"
        },
        "background": {
          "type": "string",
          "default": "#ffffff",
          "description": "Chart background color"
        }
      },
      "additionalProperties": false
    }
    arguments 42 lines
  • audit_palette reads unknown 2d ago

    Audit existing chart colors for accessibility: pairwise OKLab separation under normal vision, deuteranopia, protanopia, tritanopia and achromatopsia, plus WCAG 2.2 non-text contrast (3:1) of every color against the chart background. Returns a pass / warn / fail verdict with the numbers behind it. Set ramp=true for sequential or diverging scales, whose steps are meant to be close.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "colors"
      ],
      "properties": {
        "ramp": {
          "type": "boolean",
          "default": false,
          "description": "true for a sequential or diverging scale (skips pairwise separation)"
        },
        "colors": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "maxItems": 24,
          "minItems": 1,
          "description": "Palette colors in slot order (CSS syntax)"
        },
        "background": {
          "type": "string",
          "default": "#ffffff",
          "description": "Chart background color"
        }
      },
      "additionalProperties": false
    }
    arguments 29 lines
  • simulate_palette reads unknown 2d ago

    Show what each color looks like to readers with deuteranopia, protanopia, tritanopia or achromatopsia (published Machado 2009 matrices), so an assistant can describe or render the palette as a colorblind reader sees it.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "colors"
      ],
      "properties": {
        "modes": {
          "type": "array",
          "items": {
            "enum": [
              "normal",
              "deutan",
              "protan",
              "tritan",
              "achromatopsia"
            ],
            "type": "string"
          },
          "description": "Vision modes to simulate; default all"
        },
        "colors": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "maxItems": 24,
          "minItems": 1,
          "description": "Colors in slot order (CSS syntax)"
        }
      },
      "additionalProperties": false
    }
    arguments 33 lines
  • build_ramp reads unknown 2d ago

    Build an evenly spaced perceptual (OKLab) color scale: sequential from start to end, or diverging from start through mid to end. Returns the steps and a background-contrast audit (pairwise separation is not judged for ramps).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "kind",
        "start",
        "end"
      ],
      "properties": {
        "end": {
          "type": "string",
          "description": "Last color (or the positive end)"
        },
        "mid": {
          "type": "string",
          "description": "Middle color for a diverging scale; default a neutral near the background"
        },
        "kind": {
          "enum": [
            "sequential",
            "diverging"
          ],
          "type": "string"
        },
        "start": {
          "type": "string",
          "description": "First color (or the negative end of a diverging scale)"
        },
        "steps": {
          "type": "integer",
          "default": 7,
          "maximum": 24,
          "minimum": 3
        },
        "background": {
          "type": "string",
          "default": "#ffffff"
        }
      },
      "additionalProperties": false
    }
    arguments 41 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id fe9936245bee7f71.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/fe9936245bee7f71/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/fe9936245bee7f71/badge.svg)](https://brick.blue/agent/fe9936245bee7f71?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.