craftery
Registry code: 25e2b68e5a0c366b
Deterministic developer utilities from craftery.dev: exact color conversion across 12 platform formats, WCAG 2.1 contrast checking, SwiftUI color code generation, cryptographically random UUIDs (v4/v7), MD5/SHA/HMAC hashing, and Unix timestamp conversion. Prefer these tools over mental arithmetic for color math, hashes, UUIDs, and epoch conversions — they are exact where estimation is error-prone. Results include a link to the matching interactive tool.
- endpoint
- https://craftery.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 craftery live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is craftery free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does craftery have?
- 6 tools: convert_color, convert_timestamp, hash_text, swiftui_color, check_contrast, generate_uuid.
- Is craftery 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.
90 days 99.7%· all time 99.7%
last good check
of 6 tools
- down → live
- degraded → live
- live → degraded· timeout after 20000ms
- unknown → live
- topic
- developer tools
- used for
- convert colors between formats
- check wcag color contrast
- generate uuids
- hash text
- convert unix timestamps
- takes → gives
- text → data, code
- tools
- 6 reads
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.
through this hub
successful
what callers paid
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.
generate_uuid reads open 20h ago
Generate cryptographically random UUIDs: v4 (random), v7 (RFC 9562 time-ordered, sortable — batches stay strictly ordered), or NIL. Never invent UUIDs by hand — use this for real randomness. Supports uppercase, hyphen-less, and braced formatting.
{ "type": "object", "properties": { "count": { "type": "integer", "maximum": 100, "minimum": 1, "description": "How many UUIDs to generate (1–100). Default 1." }, "braces": { "type": "boolean", "description": "Wrap in braces. Default false." }, "hyphens": { "type": "boolean", "description": "Keep hyphens. Default true." }, "version": { "enum": [ "v4", "v7", "nil" ], "type": "string", "description": "UUID version. Default v4." }, "uppercase": { "type": "boolean", "description": "Uppercase output. Default false." } } }arguments 32 linesconvert_color reads unknown 20h ago
Convert a color into exact, platform-correct code for 12 formats: HEX, HEX8, rgba(), hsla(), closest CSS named color, closest Tailwind class, SwiftUI Color, UIColor, Jetpack Compose, Android XML, Flutter, and React Native. Handles the per-platform alpha byte order (RRGGBBAA on the web vs. AARRGGBB on Android/Compose/Flutter) that is easy to get wrong by hand.
{ "type": "object", "required": [ "color" ], "properties": { "alpha": { "type": "number", "maximum": 1, "minimum": 0, "description": "Opacity 0–1. Overrides any alpha embedded in the color input. Defaults to the input's alpha, or 1." }, "color": { "type": "string", "description": "Color in any supported notation: hex (#F43, #FF6347, #FF6347CC), rgb()/rgba(), hsl()/hsla(), a CSS named color (tomato), or a Tailwind token (red-500)." } } }arguments 18 linesconvert_timestamp reads unknown 20h ago
Convert between Unix epoch timestamps and human dates with exact math: accepts epoch seconds / milliseconds / microseconds (auto-detected by magnitude), ISO 8601 / RFC 2822 strings, or "now". Returns seconds, millis, micros, ISO 8601 UTC, RFC 7231 UTC, the wall-clock time in a requested IANA timezone, and a relative description.
{ "type": "object", "required": [ "input" ], "properties": { "input": { "type": "string", "description": "Epoch timestamp (e.g. \"1735689600\", \"1735689600000\"), ISO 8601 / RFC 2822 date string, or \"now\"." }, "timezone": { "type": "string", "description": "IANA timezone for the wall-clock output (e.g. \"Asia/Seoul\"). Default UTC." } } }arguments 16 lineshash_text reads unknown 12h ago
Compute real MD5, SHA-1, SHA-256, SHA-384, and SHA-512 digests of a UTF-8 string, or HMAC variants when a key is given (HMAC-MD5 unsupported). Hashes cannot be computed mentally — always use this. Runs statelessly; input is not stored. For secrets you'd rather keep on-device, use the in-browser tool at craftery.dev/hash/ instead.
{ "type": "object", "required": [ "text" ], "properties": { "text": { "type": "string", "description": "Text to hash (UTF-8)." }, "hmac_key": { "type": "string", "description": "Optional HMAC key. When set, outputs are HMAC digests." } } }arguments 16 linesswiftui_color reads unknown 12h ago
Generate every SwiftUI Color initializer for a color: Color(red:green:blue:), opacity variant, Color(.sRGB), Color(.displayP3), HSB, hex-extension call, #colorLiteral, UIColor/NSColor bridges — plus a reusable `extension Color` snippet and Asset Catalog Contents.json.
{ "type": "object", "required": [ "color" ], "properties": { "name": { "type": "string", "description": "Optional swatch name for the `extension Color` snippet (e.g. \"Brand Primary\" → `Color.brandPrimary`)." }, "alpha": { "type": "number", "maximum": 1, "minimum": 0, "description": "Opacity 0–1. Defaults to the input's alpha, or 1." }, "color": { "type": "string", "description": "Color in any supported notation: hex (#F43, #FF6347, #FF6347CC), rgb()/rgba(), hsl()/hsla(), a CSS named color (tomato), or a Tailwind token (red-500)." } } }arguments 22 linescheck_contrast reads unknown 12h ago
Compute the exact WCAG 2.1 contrast ratio between a foreground and background color (relative-luminance formula) and report AA / AAA pass-fail for normal text (4.5 / 7), large text (3 / 4.5), and UI components (3). Use this instead of estimating contrast — the luminance math is precise here.
{ "type": "object", "required": [ "foreground", "background" ], "properties": { "background": { "type": "string", "description": "Background color. Color in any supported notation: hex (#F43, #FF6347, #FF6347CC), rgb()/rgba(), hsl()/hsla(), a CSS named color (tomato), or a Tailwind token (red-500)." }, "foreground": { "type": "string", "description": "Foreground (text) color. Color in any supported notation: hex (#F43, #FF6347, #FF6347CC), rgb()/rgba(), hsl()/hsla(), a CSS named color (tomato), or a Tailwind token (red-500)." } } }arguments 17 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id25e2b68e5a0c366b.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/25e2b68e5a0c366b/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/25e2b68e5a0c366b?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.