Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Craftery Developer Tools

REMOTE · CRAFTERY.DEV

Developer utilities: color conversion, WCAG contrast, timestamps, UUIDs, and hashing.

Available components

0 this week 78 Trust /100

Last scanned (14 hours ago)

Scores higher than 72% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Developer Tools

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability67
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1020 tokens (~170/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 8 Nov 26 +1
    • Stability: 0.97 → pass security
  • 7 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 17 Oct 26 0
    • Authorization: unverified → partial ▲ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “check_contrast” rewrote its description, which is the text the model reads security
    • Tool “convert_color” rewrote its description, which is the text the model reads security
    • Tool “convert_timestamp” rewrote its description, which is the text the model reads security
    • Tool “generate_uuid” rewrote its description, which is the text the model reads security
    • Tool “hash_text” rewrote its description, which is the text the model reads security
    • Tool “swiftui_color” rewrote its description, which is the text the model reads security
    • Schema quality: excellent → good functional
    • Server version: 1.0.0 → 1.0.2 functional
    • Tool “check_contrast” changed its title: Check WCAG 2.1 contrast ratio → Check Color Contrast cosmetic
    • Tool “convert_color” changed its title: Convert color to 12 platform formats → Convert Color cosmetic
    • Tool “convert_timestamp” changed its title: Convert Unix timestamp ↔ date → Convert Timestamp cosmetic
    • Tool “generate_uuid” changed its title: Generate UUIDs (v4 / v7 / NIL) → Generate UUID cosmetic
    • Tool “hash_text” changed its title: Hash text (MD5 / SHA / HMAC) → Hash Text cosmetic
    • Tool “swiftui_color” changed its title: Generate SwiftUI color code → SwiftUI Color Code cosmetic
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Sept 26 0
    • Stability: 0.97 → pass security
Diagnostics

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 Nov 2026 · Probed https://craftery.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=craftery.dev CN=WE1,O=Google Trust Services,C=US 3 Nov 2026 1 Feb 2027 ECDSA 256 ECDSA-SHA256 773bc66c372c328d1387006b3ab3dee4
SANs: craftery.dev, *.craftery.dev
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of craftery.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
craftery.dev. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://craftery.dev/mcp Verified 200
http (plaintext) http://craftery.dev/mcp Inconclusive 405
MCP tools · 6 exposed · ~933 tokens

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 →

Tool Tokens
check_contrast ~190

Computes the exact WCAG 2.1 contrast ratio between a foreground and background color (relative-luminance formula) and reports AA/AAA pass-fail for normal text (4.5 / 7), large text (3 / 4.5), and UI components (3).

NameTypeReqDescription
backgroundstringyesBackground 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).
foregroundstringyesForeground (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).

No output schema declared.

No examples provided.

convert_color ~175

Converts a color into 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. Applies each platform's alpha byte order (RRGGBBAA on the web, AARRGGBB on Android/Compose/Flutter).

NameTypeReqDescription
alphanumber–Opacity 0–1. Overrides any alpha embedded in the color input. Defaults to the input's alpha, or 1.
colorstringyesColor in any supported notation: hex (#F43, #FF6347, #FF6347CC), rgb()/rgba(), hsl()/hsla(), a CSS named color (tomato), or a Tailwind token (red-500).

No output schema declared.

No examples provided.

convert_timestamp ~152

Converts between Unix epoch timestamps and human-readable dates. 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.

NameTypeReqDescription
inputstringyesEpoch timestamp (e.g. "1735689600", "1735689600000"), ISO 8601 / RFC 2822 date string, or "now".
timezonestring–IANA timezone for the wall-clock output (e.g. "Asia/Seoul"). Default UTC.

No output schema declared.

No examples provided.

generate_uuid ~134

Generates cryptographically random UUIDs: v4 (random), v7 (RFC 9562 time-ordered; batches stay strictly ordered), or NIL. Supports uppercase, hyphen-less, and braced formatting. 1–100 per call.

NameTypeReqDescription
bracesboolean–Wrap in braces. Default false.
countinteger–How many UUIDs to generate (1–100). Default 1.
hyphensboolean–Keep hyphens. Default true.
uppercaseboolean–Uppercase output. Default false.
versionstring–UUID version. Default v4.

No output schema declared.

No examples provided.

hash_text ~98

Computes 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). Stateless; input is not stored.

NameTypeReqDescription
hmac_keystring–Optional HMAC key. When set, outputs are HMAC digests.
textstringyesText to hash (UTF-8).

No output schema declared.

No examples provided.

swiftui_color ~184

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

NameTypeReqDescription
alphanumber–Opacity 0–1. Defaults to the input's alpha, or 1.
colorstringyesColor in any supported notation: hex (#F43, #FF6347, #FF6347CC), rgb()/rgba(), hsl()/hsla(), a CSS named color (tomato), or a Tailwind token (red-500).
namestring–Optional swatch name for the `extension Color` snippet (e.g. "Brand Primary" → `Color.brandPrimary`).

No output schema declared.

No examples provided.

Install

How do I install the Craftery Developer Tools MCP server?

Craftery Developer Tools is a hosted endpoint at https://craftery.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · craftery.dev

# add to Claude Code
claude mcp add --transport http dev-craftery-tools 'https://craftery.dev/mcp'
Common questions

What is the Craftery Developer Tools MCP server?

Craftery Developer Tools is an MCP server listed in the public MCP registry as dev.craftery/tools. Developer utilities: color conversion, WCAG contrast, timestamps, UUIDs, and hashing. This page covers its hosted endpoint (https://craftery.dev/mcp).

Is the Craftery Developer Tools MCP server safe to use?

Craftery Developer Tools scores 78 out of 100 on VerifyMCP. 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 Craftery Developer Tools MCP server expose?

Craftery Developer Tools exposes 6 tools: convert_color, check_contrast, swiftui_color, generate_uuid, hash_text, convert_timestamp. Their descriptions and schemas cost roughly 933 tokens of context every time the server is loaded.

Does the Craftery Developer Tools MCP server require authentication?

No. We connected to Craftery Developer Tools without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Craftery Developer Tools MCP server still maintained?

Craftery Developer Tools is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Craftery Developer Tools MCP server?

VerifyMCP ran 12 checks on Craftery Developer Tools, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Craftery Developer Tools: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.