io.github.cyanheads/toolkit-mcp-server
REMOTE · TOOLKIT.CASEYJHAND.COM · 2 COMPONENTS · SCANNED SEP 22
Generate IDs, QR codes, and hashes, encode values, geolocate IPs, plus gated host diagnostics.
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 Security66
- 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 5 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1346 tokens (~269/item across 5 items; 5 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the io.github.cyanheads/toolkit-mcp-server server?
io.github.cyanheads/toolkit-mcp-server is a hosted endpoint at https://toolkit.caseyjhand.com/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 · toolkit.caseyjhand.com
claude mcp add --transport http cyanheads-toolkit-mcp-server 'https://toolkit.caseyjhand.com/mcp'
{
"mcpServers": {
"cyanheads-toolkit-mcp-server": {
"url": "https://toolkit.caseyjhand.com/mcp"
}
}
} {
"servers": {
"cyanheads-toolkit-mcp-server": {
"type": "http",
"url": "https://toolkit.caseyjhand.com/mcp"
}
}
} [mcp_servers.cyanheads-toolkit-mcp-server] url = "https://toolkit.caseyjhand.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"cyanheads-toolkit-mcp-server": {
"type": "remote",
"url": "https://toolkit.caseyjhand.com/mcp",
"enabled": true
}
}
} openclaw mcp add cyanheads-toolkit-mcp-server --url 'https://toolkit.caseyjhand.com/mcp' --transport streamable-http
mcp_servers:
cyanheads-toolkit-mcp-server:
url: "https://toolkit.caseyjhand.com/mcp" {
"McpServers": {
"cyanheads-toolkit-mcp-server": {
"Transport": "http",
"Url": "https://toolkit.caseyjhand.com/mcp"
}
}
} assistant mcp add cyanheads-toolkit-mcp-server -t streamable-http -u 'https://toolkit.caseyjhand.com/mcp'
{
"mcpServers": {
"cyanheads-toolkit-mcp-server": {
"type": "http",
"url": "https://toolkit.caseyjhand.com/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.
- 19 Sept 26 0
- Server version: 2.2.3 → 2.2.4 functional
- 17 Sept 26 +1
- Stability: 0.97 → pass security
- 15 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.
- 13 Sept 26 +1
- Server version: 2.2.2 → 2.2.3 functional
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 4 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 22 Sept 2026 · Probed https://toolkit.caseyjhand.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=caseyjhand.com | CN=WE1,O=Google Trust Services,C=US | 4 Sept 2026 | 3 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | a6985204ed51ae050e7738aa6be668e9 |
| SANs: caseyjhand.com, *.caseyjhand.com | ||||||
| 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 secure
Validation of toolkit.caseyjhand.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| caseyjhand.com. | present | 2371 | 13 | Verified |
| toolkit.caseyjhand.com. | Verified address RRset verified with the apex keys |
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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://toolkit.caseyjhand.com/mcp | Verified | 200 | |
| http (plaintext) | http://toolkit.caseyjhand.com/mcp | HTTPS enforced | 301 | https://toolkit.caseyjhand.com/mcp |
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 →
toolkit_encode_value toolkit-mcp-server: encode value ~194
Encode or decode a value across base64, base64url, hex, or URL (percent) encoding, in either direction. Set operation to "encode" to transform raw UTF-8 text into the chosen encoding, or "decode" to recover the original text from an encoded value. base64url uses the URL-safe alphabet (- and _ instead of + and /); url applies encodeURIComponent / decodeURIComponent. Decoding a value that is malformed for the chosen encoding is reported as a recoverable error, not a silent best-effort.
| Name | Type | Req | Description |
|---|---|---|---|
| encoding | string | yes | The encoding to apply: base64, URL-safe base64url, hex, or URL percent-encoding. |
| operation | string | yes | "encode" transforms text into the encoding; "decode" recovers text from an encoded value. |
| value | string | yes | The value to transform — raw text for encode, an encoded string for decode. |
| Name | Type | Req | Description |
|---|---|---|---|
| encoding | string | – | The encoding that was applied. |
| error | object | – | Present when the call failed. Absent on success. |
| operation | string | – | The operation that was performed. |
| result | string | – | The transformed value (encoded text, or the decoded original). |
No examples provided.
toolkit_generate_id toolkit-mcp-server: generate id ~226
Mint cryptographically-random identifiers using the platform CSPRNG — the correct source for IDs that must be unpredictable, unlike model-generated values. type selects the format: uuid_v4 (random, the default), uuid_v7 (time-ordered, sortable by creation), or ulid (26-char Crockford-base32, lexicographically sortable). Set count to mint a batch in one call (up to 1000); the returned ids array always contains exactly count values and is never truncated. For uuid_v7 and ulid, a batch is monotonic — strictly increasing even within the same millisecond — so the ids array stays in sorted creation order. IDs from this tool feed into toolkit_generate_qr (pass ids[0] as data) to create a scannable code.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | How many identifiers to mint (1–1000). The full batch is always returned. |
| type | string | – | Identifier format: uuid_v4 (random), uuid_v7 (time-ordered), or ulid (sortable Crockford-base32). |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | The number of identifiers minted (equals the requested count). |
| error | object | – | Present when the call failed. Absent on success. |
| ids | array | – | The minted identifiers — exactly count of them, in mint order; for uuid_v7 and ulid that order is strictly increasing (sorted by creation). |
| type | string | – | The identifier format that was minted. |
No examples provided.
toolkit_generate_qr toolkit-mcp-server: generate QR code ~385
Encode text or a URL into a QR code. data is the content to encode (a link, a generated identifier such as toolkit_generate_id's ids[0], or any string). format selects the output: svg returns inline SVG markup, png_base64 returns base64-encoded PNG bytes (with mimeType and byteLength), and terminal returns a block of Unicode block characters renderable in a monospace terminal. errorCorrection (L/M/Q/H) trades data capacity for damage tolerance, margin sets the quiet-zone width, and scale sets pixels per module for raster output. The returned version (1–40) reflects how dense the encoded data is. png_base64 renders (modules + 2 × margin) × scale pixels per side and rejects anything past 2048 px with a typed raster_too_large error, so a dense symbol needs a lower scale; svg carries no such limit.
| Name | Type | Req | Description |
|---|---|---|---|
| data | string | yes | The text or URL to encode. 2953 is the absolute ceiling (QR version 40, level L, byte mode); usable capacity drops at higher errorCorrection levels, so over-capacity data is rejected with a typed dat… |
| errorCorrection | string | – | Error-correction level: L (~7% recoverable) to H (~30%). Higher tolerance lowers data capacity. |
| format | string | – | Output format: svg markup, png_base64 (raster bytes), or a terminal-renderable string. |
| margin | integer | – | Quiet-zone width in modules around the symbol. The spec recommends 4. |
| scale | integer | – | Pixels per module for raster (png_base64) output. Ignored for terminal. png_base64 also bounds the whole image at 2048 px per side, so a dense symbol or a wide margin admits a lower scale than 32. |
| Name | Type | Req | Description |
|---|---|---|---|
| byteLength | number | – | Decoded byte size of the PNG. Present only for png_base64. |
| content | string | – | The QR artifact: SVG markup, a terminal-renderable string, or base64 PNG bytes for png_base64. |
| error | object | – | Present when the call failed. Absent on success. |
| format | string | – | The format that was produced. |
| mimeType | string | – | MIME type of content for image formats. Absent for the terminal format. |
| version | number | – | QR symbol version (1–40); higher versions hold denser data and indicate denser content. |
No examples provided.
toolkit_geolocate_ip toolkit-mcp-server: geolocate IP ~248
Resolve a public IP address (or hostname) to geographic and network metadata: country, region, city, latitude/longitude, the owning ASN and organization, timezone, and the proxy/hosting/mobile quality flags. target accepts an IPv4/IPv6 address or a hostname — a hostname is DNS-resolved first and the resolvedIp field echoes which IP was actually located. The provider is called directly (never the target), so this is SSRF-free and safe to expose anywhere. Results are best-effort and provider-bounded: VPNs, proxies, mobile NAT, and anycast all defeat IP-to-location, accuracy is city-level at best, and many fields can be absent for reserved or thinly-documented ranges — absent fields are reported as unknown, never invented. Read proxy, hosting, and mobile before trusting the coordinates: a true on any of them means the location describes infrastructure, not the user. Private/reserved addresses have no public geolocation and are rejected. The source field names which provider answered.
| Name | Type | Req | Description |
|---|---|---|---|
| target | – | yes | A public IPv4/IPv6 address or a hostname (e.g. "8.8.8.8" or "example.com"). |
| Name | Type | Req | Description |
|---|---|---|---|
| asn | string | – | Autonomous System number, e.g. "AS15169". Absent on providers that omit it. |
| city | string | – | City name. Absent when unknown. |
| country | string | – | Country name. Absent when the provider does not report it. |
| countryCode | string | – | ISO 3166-1 alpha-2 country code. Absent when unknown. |
| error | object | – | Present when the call failed. Absent on success. |
| hosting | boolean | – | True when the address belongs to a hosting or datacenter network, so the location is a facility rather than a person. Absent when unreported. |
| latitude | number | – | Latitude in decimal degrees. Absent when unknown. |
| longitude | number | – | Longitude in decimal degrees. Absent when unknown. |
| mobile | boolean | – | True when the address belongs to a mobile carrier network, where NAT can place the location far from the device. Absent when unreported. |
| org | string | – | Owning organization or ISP, e.g. "Google LLC". Absent when unknown. |
| proxy | boolean | – | True when the address is a known proxy, VPN, or Tor exit — the location describes the exit node, not the user. Absent when the provider does not report it. |
| region | string | – | Region or state name. Absent when unknown. |
| resolvedIp | string | – | The IP that was actually located (a supplied hostname is resolved to this first). |
| source | string | – | The provider that answered the lookup, e.g. "ip-api". |
| target | string | – | The target as supplied (IP or hostname). |
| timezone | string | – | IANA timezone, e.g. "America/Los_Angeles". Absent when unknown. |
No examples provided.
toolkit_hash_value toolkit-mcp-server: hash value ~293
Generate a cryptographic digest of a value, or verify a value against an expected digest. Set operation to "generate" for a lowercase-hex digest, or "compare" to constant-time-check value against the expected digest — compare is timing-safe and avoids manual string equality checks. Algorithm defaults to sha256; sha512 is also secure, while md5 and sha1 are exposed for checksum and file-integrity compatibility ONLY and must not be used for passwords, signatures, or any security purpose. inputEncoding controls how value and expected are read before hashing (utf8 default, or hex/base64 for raw binary data) so binary blobs need no decode round-trip. The canonical use is matching a download against a vendor-published checksum.
| Name | Type | Req | Description |
|---|---|---|---|
| algorithm | string | – | Digest algorithm. sha256 (default) or sha512 for security; md5/sha1 are checksum/compat only — not for security. |
| expected | string | – | The expected lowercase-hex digest to compare against. Required when operation is "compare". |
| inputEncoding | string | – | How value (and expected's pre-image, when relevant) is decoded before hashing: utf8 text, hex, or base64. |
| operation | string | – | "generate" produces a digest; "compare" constant-time-checks value against expected. |
| value | string | yes | The data to hash, interpreted per inputEncoding (raw text by default). |
| Name | Type | Req | Description |
|---|---|---|---|
| algorithm | string | – | The algorithm used. |
| digest | string | – | Lowercase-hex digest of value. Present for operation "generate". |
| error | object | – | Present when the call failed. Absent on success. |
| lengthInBytes | number | – | Digest size in bytes (32 for sha256, 64 for sha512, 20 for sha1, 16 for md5). Present for "generate". |
| matches | boolean | – | Constant-time equality of the computed digest against expected. Present for operation "compare". |
| operation | string | – | The operation performed. |
No examples provided.
What is the io.github.cyanheads/toolkit-mcp-server server?
io.github.cyanheads/toolkit-mcp-server is listed in the public MCP registry as io.github.cyanheads/toolkit-mcp-server. Generate IDs, QR codes, and hashes, encode values, geolocate IPs, plus gated host diagnostics. This page covers its hosted endpoint (https://toolkit.caseyjhand.com/mcp).
Is the io.github.cyanheads/toolkit-mcp-server server safe to use?
io.github.cyanheads/toolkit-mcp-server scores 81 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 io.github.cyanheads/toolkit-mcp-server server expose?
io.github.cyanheads/toolkit-mcp-server exposes 5 tools: toolkit_hash_value, toolkit_generate_id, toolkit_generate_qr, toolkit_encode_value, toolkit_geolocate_ip. Their descriptions and schemas cost roughly 1,346 tokens of context every time the server is loaded.
Does the io.github.cyanheads/toolkit-mcp-server server require authentication?
No. We connected to io.github.cyanheads/toolkit-mcp-server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.cyanheads/toolkit-mcp-server server still maintained?
io.github.cyanheads/toolkit-mcp-server is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.