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.

io.github.cyanheads/toolkit-mcp-server

NPM · @CYANHEADS/TOOLKIT-MCP-SERVER · SCANNED AUG 7

Generate IDs, QR codes, and hashes, encode values, geolocate IPs, plus gated host diagnostics.

+28 this week 66 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 51 of 156 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability63
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1229 tokens (~245/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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @cyanheads/toolkit-mcp-server

# add to Claude Code
claude mcp add cyanheads-toolkit-mcp-server -- npx -y @cyanheads/toolkit-mcp-server
# add to Codex CLI
codex mcp add cyanheads-toolkit-mcp-server -- npx -y @cyanheads/toolkit-mcp-server
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cyanheads-toolkit-mcp-server": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@cyanheads/toolkit-mcp-server"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add cyanheads-toolkit-mcp-server --command npx --arg -y --arg @cyanheads/toolkit-mcp-server
# ~/.hermes/config.yaml
mcp_servers:
  cyanheads-toolkit-mcp-server:
    command: "npx"
    args: ["-y", "@cyanheads/toolkit-mcp-server"]
// mcp.json
{
  "mcpServers": {
    "cyanheads-toolkit-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@cyanheads/toolkit-mcp-server"
      ]
    }
  }
}
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.

  • 7 Aug 26 +4
    • Known CVEs: partial → pass security
    • Dependency health: partial → 0.83 functional
  • 6 Aug 26 +27
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • MCP protocol: unverified → pass functional
    • Tool coverage: unverified → 100 functional
    • First check of Tool coverage: 100 functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: excellent functional
    • First check of Schema quality: fail functional
    • First check of Tool coverage: 100 functional
  • 5 Aug 26 +1
    • CVE-2026-69207 no longer affects this package security
    • Known CVEs: fail → partial security
  • 4 Aug 26 −1
    • CVE-2026-69207 affects this package: medium security
    • Known CVEs: partial → fail security
  • 2 Aug 26 +7
    • Provenance: fail → unverified security
    • Install scripts: pass → unverified security
    • Known CVEs: unverified → partial security
    • License: pass → unverified functional
    • Maintenance: pass → unverified functional
    • Dependency health: unverified → partial functional
    • Licence: Apache-2.0 functional
  • 1 Aug 26 −10
    • Known CVEs: partial → unverified security
    • Dependency health: partial → unverified functional
  • 31 Jul 26 −8
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 29 Jul 26 +22
    • Provenance: unverified → fail security
    • Known CVEs: unverified → partial security
    • Install scripts: unverified → pass security
    • Maintenance: unverified → pass functional
    • Dependency health: unverified → partial functional
    • License: unverified → pass functional
    • Schema quality: Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess. functional
    • Tool coverage: Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess. functional
    • Licence: Apache-2.0 functional
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 7 Aug 2026 · Analysed npm/@cyanheads/[email protected]

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm
Dependencies 156 packages
Packages resolved 156
Stale 51
Tree resolution Complete
MCP tools · 5 exposed · ~1,229 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.

Tool Tokens
toolkit_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.

NameTypeReqDescription
encodingstringyesThe encoding to apply: base64, URL-safe base64url, hex, or URL percent-encoding.
operationstringyes"encode" transforms text into the encoding; "decode" recovers text from an encoded value.
valuestringyesThe value to transform — raw text for encode, an encoded string for decode.
NameTypeReqDescription
encodingstringyesThe encoding that was applied.
operationstringyesThe operation that was performed.
resultstringyesThe transformed value (encoded text, or the decoded original).

No examples provided.

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

NameTypeReqDescription
countintegerHow many identifiers to mint (1–1000). The full batch is always returned.
typestringIdentifier format: uuid_v4 (random), uuid_v7 (time-ordered), or ulid (sortable Crockford-base32).
NameTypeReqDescription
countnumberyesThe number of identifiers minted (equals the requested count).
idsarrayyesThe minted identifiers — exactly count of them, in mint order; for uuid_v7 and ulid that order is strictly increasing (sorted by creation).
typestringyesThe identifier format that was minted.

No examples provided.

toolkit_generate_qr ~304

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.

NameTypeReqDescription
datastringyesThe 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…
errorCorrectionstringError-correction level: L (~7% recoverable) to H (~30%). Higher tolerance lowers data capacity.
formatstringOutput format: svg markup, png_base64 (raster bytes), or a terminal-renderable string.
marginintegerQuiet-zone width in modules around the symbol. The spec recommends 4.
scaleintegerPixels per module for raster (png_base64) output. Ignored for terminal.
NameTypeReqDescription
byteLengthnumberDecoded byte size of the PNG. Present only for png_base64.
contentstringyesThe QR artifact: SVG markup, a terminal-renderable string, or base64 PNG bytes for png_base64.
formatstringyesThe format that was produced.
mimeTypestringMIME type of content for image formats. Absent for the terminal format.
versionnumberyesQR symbol version (1–40); higher versions hold denser data and indicate denser content.

No examples provided.

toolkit_geolocate_ip ~212

Resolve a public IP address (or hostname) to geographic and network metadata: country, region, city, latitude/longitude, the owning ASN and organization, and timezone. 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. Private/reserved addresses have no public geolocation and are rejected. The source field names which provider answered.

NameTypeReqDescription
targetyesA public IPv4/IPv6 address or a hostname (e.g. "8.8.8.8" or "example.com").
NameTypeReqDescription
asnstringAutonomous System number, e.g. "AS15169". Absent on providers that omit it.
citystringCity name. Absent when unknown.
countrystringCountry name. Absent when the provider does not report it.
countryCodestringISO 3166-1 alpha-2 country code. Absent when unknown.
latitudenumberLatitude in decimal degrees. Absent when unknown.
longitudenumberLongitude in decimal degrees. Absent when unknown.
orgstringOwning organization or ISP, e.g. "Google LLC". Absent when unknown.
regionstringRegion or state name. Absent when unknown.
resolvedIpstringyesThe IP that was actually located (a supplied hostname is resolved to this first).
sourcestringyesThe provider that answered the lookup, e.g. "ip-api".
targetstringyesThe target as supplied (IP or hostname).
timezonestringIANA timezone, e.g. "America/Los_Angeles". Absent when unknown.

No examples provided.

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

NameTypeReqDescription
algorithmstringDigest algorithm. sha256 (default) or sha512 for security; md5/sha1 are checksum/compat only — not for security.
expectedstringThe expected lowercase-hex digest to compare against. Required when operation is "compare".
inputEncodingstringHow value (and expected's pre-image, when relevant) is decoded before hashing: utf8 text, hex, or base64.
operationstring"generate" produces a digest; "compare" constant-time-checks value against expected.
valuestringyesThe data to hash, interpreted per inputEncoding (raw text by default).
NameTypeReqDescription
algorithmstringyesThe algorithm used.
digeststringLowercase-hex digest of value. Present for operation "generate".
lengthInBytesnumberDigest size in bytes (32 for sha256, 64 for sha512, 20 for sha1, 16 for md5). Present for "generate".
matchesbooleanConstant-time equality of the computed digest against expected. Present for operation "compare".
operationstringyesThe operation performed.

No examples provided.