_ registry / mcp streamable-http · checked 2h ago

contrastkit

https://contrastkit.mike-tusa.workers.dev

Registry code: 11af0b674d2c542d

api record

ContrastKit checks color contrast against WCAG 2.x (the ratio used by WCAG 2.0, 2.1 and 2.2 success criteria 1.4.3, 1.4.6 and 1.4.11), finds the nearest passing color, converts CSS colors and checks every pair in a palette. Colors: #rgb, #rrggbb, #rrggbbaa, rgb(), hsl() (comma or space syntax, optional alpha) or CSS color names. Levels: aa (4.5:1, normal text), aa-large (3:1, 18pt or 14pt bold), aaa (7:1), aaa-large (4.5:1), ui (3:1, non-text UI components and graphics). Ratios are reported floored to 2 decimals and pass/fail never rounds up (4.49:1 fails AA). Translucent foregrounds are…

endpoint
https://contrastkit.mike-tusa.workers.dev/mcp
protocol
streamable-http ·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 contrastkit live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is contrastkit free to use?
Yes — the hub reached it with no key and no payment.
What tools does contrastkit have?
4 tools: check_contrast, check_palette, convert_color, suggest_accessible_color.
Is contrastkit 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
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
515ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 4 tools
4 never probed 0 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.

  • check_contrast unknown 2h ago

    Compute the WCAG 2.x contrast ratio between a text (foreground) color and a background color, with pass/fail for AA, AA large text, AAA, AAA large text and non-text UI (3:1). Handles translucent colors. Read-only. Same engine as GET /api/contrast.

    mcp-tool

    {
      "type": "object",
      "required": [
        "foreground",
        "background"
      ],
      "properties": {
        "background": {
          "type": "string",
          "maxLength": 64,
          "minLength": 1,
          "description": "Background color as a CSS color: \"#1a73e8\", \"#fff\", \"rgb(26 115 232)\", \"hsl(217 80% 51%)\", \"rgba(0,0,0,.6)\" or a name like \"navy\"."
        },
        "foreground": {
          "type": "string",
          "maxLength": 64,
          "minLength": 1,
          "description": "Text / foreground color as a CSS color: \"#1a73e8\", \"#fff\", \"rgb(26 115 232)\", \"hsl(217 80% 51%)\", \"rgba(0,0,0,.6)\" or a name like \"navy\"."
        }
      },
      "additionalProperties": false
    }
    arguments 22 lines
  • check_palette unknown 2h ago

    Contrast ratio for every pair of 2 to 12 colors (up to 66 pairs), highest first, each flagged against the chosen WCAG level. Use it to see which brand colors can be used together for text. Read-only. Same engine as GET /api/palette.

    mcp-tool

    {
      "type": "object",
      "required": [
        "colors"
      ],
      "properties": {
        "level": {
          "enum": [
            "aa",
            "aa-large",
            "aaa",
            "aaa-large",
            "ui"
          ],
          "type": "string",
          "default": "aa",
          "description": "WCAG target: aa 4.5:1 (default), aa-large 3:1, aaa 7:1, aaa-large 4.5:1, ui 3:1 (non-text)."
        },
        "colors": {
          "type": "array",
          "items": {
            "type": "string",
            "maxLength": 64,
            "minLength": 1,
            "description": "Palette color as a CSS color: \"#1a73e8\", \"#fff\", \"rgb(26 115 232)\", \"hsl(217 80% 51%)\", \"rgba(0,0,0,.6)\" or a name like \"navy\"."
          },
          "maxItems": 12,
          "minItems": 2,
          "description": "2 to 12 CSS colors."
        }
      },
      "additionalProperties": false
    }
    arguments 33 lines
  • convert_color unknown 2h ago

    Convert a CSS color to hex, rgb() and hsl(), with its relative luminance, its contrast on white and on black, and the better text color (black or white) to put on it. Read-only. Same engine as GET /api/convert.

    mcp-tool

    {
      "type": "object",
      "required": [
        "color"
      ],
      "properties": {
        "color": {
          "type": "string",
          "maxLength": 64,
          "minLength": 1,
          "description": "Color as a CSS color: \"#1a73e8\", \"#fff\", \"rgb(26 115 232)\", \"hsl(217 80% 51%)\", \"rgba(0,0,0,.6)\" or a name like \"navy\"."
        }
      },
      "additionalProperties": false
    }
    arguments 15 lines
  • suggest_accessible_color unknown never probed

    For a failing color pair, find the closest color (same hue and saturation, lightness changed as little as possible) that meets the chosen WCAG level. Adjust the foreground (default), the background, or both (best first). Read-only. Same engine as GET /api/suggest.

    mcp-tool

    {
      "type": "object",
      "required": [
        "foreground",
        "background"
      ],
      "properties": {
        "level": {
          "enum": [
            "aa",
            "aa-large",
            "aaa",
            "aaa-large",
            "ui"
          ],
          "type": "string",
          "default": "aa",
          "description": "WCAG target: aa 4.5:1 (default), aa-large 3:1, aaa 7:1, aaa-large 4.5:1, ui 3:1 (non-text)."
        },
        "adjust": {
          "enum": [
            "foreground",
            "background",
            "both"
          ],
          "type": "string",
          "default": "foreground",
          "description": "Which color may change."
        },
        "background": {
          "type": "string",
          "maxLength": 64,
          "minLength": 1,
          "description": "Background color as a CSS color: \"#1a73e8\", \"#fff\", \"rgb(26 115 232)\", \"hsl(217 80% 51%)\", \"rgba(0,0,0,.6)\" or a name like \"navy\"."
        },
        "foreground": {
          "type": "string",
          "maxLength": 64,
          "minLength": 1,
          "description": "Text / foreground color as a CSS color: \"#1a73e8\", \"#fff\", \"rgb(26 115 232)\", \"hsl(217 80% 51%)\", \"rgba(0,0,0,.6)\" or a name like \"navy\"."
        }
      },
      "additionalProperties": false
    }
    arguments 44 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 11af0b674d2c542d.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/11af0b674d2c542d/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/11af0b674d2c542d/badge.svg)](https://brick.blue/agent/11af0b674d2c542d?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.