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

color-omikuji-dev

https://color.omikuji.dev

Registry code: f5348bda31f4c27f

api record

Traditional color names and their values (hex, RGB) from Japan, China, Korea, the West, India, the Middle East, Africa, Latin America and Southeast Asia, with sources. Use find_color to look up a color by name (Japanese kanji, reading in hiragana/katakana, or English), nearest_colors to name a hex code with the closest traditional colors, list_colors to browse by culture/category/era/tag, and list_cultures to see what is covered. Do not guess hex codes; if a name is not found, say so.

endpoint
https://color.omikuji.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 color-omikuji-dev live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is color-omikuji-dev free to use?
Yes — the hub reached it with no key and no payment.
What tools does color-omikuji-dev have?
4 tools: nearest_colors, list_colors, find_color, list_cultures.
Is color-omikuji-dev 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
288ms

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

_ 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.

  • list_cultures open 1h ago

    List the cultures covered, with color counts and categories.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • nearest_colors unknown never probed

    Given a hex code, return the closest traditional colors by CIEDE2000 color difference (delta_e). Use it to answer "what is this color called in Japanese tradition?".

    mcp-tool

    {
  "type": "object",
  "required": [
    "hex"
  ],
  "properties": {
    "hex": {
      "type": "string",
      "description": "#RRGGBB or #RGB"
    },
    "limit": {
      "type": "integer",
      "default": 5,
      "maximum": 20,
      "minimum": 1
    },
    "culture": {
      "type": "string",
      "description": "Culture id from list_cultures (e.g. japanese, chinese, western) or its name."
    }
  },
  "additionalProperties": false
}
    arguments 23 lines
  • list_colors unknown 1h ago

    List colors filtered by culture, category (e.g. 青系, 赤系), era (e.g. 平安, 江戸) or tag. At most 50 per call.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "era": {
      "type": "string",
      "description": "Part of the era text, e.g. 平安, 江戸, 19世紀."
    },
    "tag": {
      "type": "string"
    },
    "limit": {
      "type": "integer",
      "default": 30,
      "maximum": 50,
      "minimum": 1
    },
    "offset": {
      "type": "integer",
      "default": 0,
      "maximum": 1000,
      "minimum": 0
    },
    "culture": {
      "type": "string",
      "description": "Culture id from list_cultures (e.g. japanese, chinese, western) or its name."
    },
    "category": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 32 lines
  • find_color unknown 1h ago

    Look up traditional colors by name and get hex/RGB with sources. Accepts Japanese kanji (浅葱色), reading in hiragana or katakana (あさぎいろ), English (Asagi, Prussian Blue), with or without 色. Exact name matches come first.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "default": 10,
      "maximum": 50,
      "minimum": 1
    },
    "query": {
      "type": "string",
      "description": "Color name."
    },
    "culture": {
      "type": "string",
      "description": "Culture id from list_cultures (e.g. japanese, chinese, western) or its name."
    }
  },
  "additionalProperties": false
}
    arguments 23 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 f5348bda31f4c27f.

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

_ also on omikuji.dev 3 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.