Craftery Developer Tools
REMOTE · CRAFTERY.DEV · SCANNED SEP 27
Developer utilities: color conversion, WCAG contrast, timestamps, UUIDs, and hashing.
Available components
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1110 tokens (~185/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
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
claude mcp add --transport http dev-craftery-tools 'https://craftery.dev/mcp'
{
"mcpServers": {
"dev-craftery-tools": {
"url": "https://craftery.dev/mcp"
}
}
} {
"servers": {
"dev-craftery-tools": {
"type": "http",
"url": "https://craftery.dev/mcp"
}
}
} [mcp_servers.dev-craftery-tools] url = "https://craftery.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-craftery-tools": {
"type": "remote",
"url": "https://craftery.dev/mcp",
"enabled": true
}
}
} openclaw mcp add dev-craftery-tools --url 'https://craftery.dev/mcp' --transport streamable-http
mcp_servers:
dev-craftery-tools:
url: "https://craftery.dev/mcp" {
"McpServers": {
"dev-craftery-tools": {
"Transport": "http",
"Url": "https://craftery.dev/mcp"
}
}
} assistant mcp add dev-craftery-tools -t streamable-http -u 'https://craftery.dev/mcp'
{
"mcpServers": {
"dev-craftery-tools": {
"type": "http",
"url": "https://craftery.dev/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 26 Sept 26 +1
- Stability: 0.97 → pass security
- 25 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
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
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 27 Sept 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 | 5 Sept 2026 | 4 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | b917ce7438a83bf413b0205393ffd9e1 |
| 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. | present | 60074 | 8 | Verified |
| craftery.dev. | absent | 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 |
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 →
check_contrast Check WCAG 2.1 contrast ratio ~205
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.
| Name | Type | Req | Description |
|---|---|---|---|
| background | string | yes | 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 | string | yes | 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). |
No output schema declared.
No examples provided.
convert_color Convert color to 12 platform formats ~190
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.
| Name | Type | Req | Description |
|---|---|---|---|
| alpha | number | – | Opacity 0–1. Overrides any alpha embedded in the color input. Defaults to the input's alpha, or 1. |
| color | string | yes | 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_timestamp Convert Unix timestamp ↔ date ~153
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.
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | Epoch timestamp (e.g. "1735689600", "1735689600000"), ISO 8601 / RFC 2822 date string, or "now". |
| timezone | string | – | IANA timezone for the wall-clock output (e.g. "Asia/Seoul"). Default UTC. |
No output schema declared.
No examples provided.
generate_uuid Generate UUIDs (v4 / v7 / NIL) ~142
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.
| Name | Type | Req | Description |
|---|---|---|---|
| braces | boolean | – | Wrap in braces. Default false. |
| count | integer | – | How many UUIDs to generate (1–100). Default 1. |
| hyphens | boolean | – | Keep hyphens. Default true. |
| uppercase | boolean | – | Uppercase output. Default false. |
| version | string | – | UUID version. Default v4. |
No output schema declared.
No examples provided.
hash_text Hash text (MD5 / SHA / HMAC) ~135
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.
| Name | Type | Req | Description |
|---|---|---|---|
| hmac_key | string | – | Optional HMAC key. When set, outputs are HMAC digests. |
| text | string | yes | Text to hash (UTF-8). |
No output schema declared.
No examples provided.
swiftui_color Generate SwiftUI color code ~184
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.
| Name | Type | Req | Description |
|---|---|---|---|
| alpha | number | – | Opacity 0–1. Defaults to the input's alpha, or 1. |
| color | string | yes | Color in any supported notation: hex (#F43, #FF6347, #FF6347CC), rgb()/rgba(), hsl()/hsla(), a CSS named color (tomato), or a Tailwind token (red-500). |
| name | string | – | Optional swatch name for the `extension Color` snippet (e.g. "Brand Primary" → `Color.brandPrimary`). |
No output schema declared.
No examples provided.
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 72 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 1,009 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 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.