io.github.cyanheads/toolkit-mcp-server

Est-ce que io.github.cyanheads/toolkit-mcp-server est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.cyanheads/toolkit-mcp-server » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 5 outils

• toolkit_encode_value≈ 1138 tokens

  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 bytes from an encoded value. Decoded bytes come back as UTF-8 text by default; set outputEncoding to "hex" or "base64" to receive them re-encoded instead, which is lossless for binary data and transcodes between encodings (a base64 digest to hex, for example). Decoding never substitutes replacement characters: bytes that are not valid UTF-8 text are reported as a recoverable error that points at outputEncoding. Whitespace in hex, base64, and base64url values is ignored, so line-wrapped MIME bodies and PEM bodies decode as-is (drop PEM's -----BEGIN/END----- lines, which are not base64). base64url uses the URL-safe alphabet (- and _ instead of + and /); url applies encodeURIComponent and percent-decoding. A value that is malformed for the chosen encoding is reported as a recoverable error, not a silent best-effort.

  Paramètres, retour & exemple (4)

  Paramètres

  • value · string · requis
    The value to transform — raw text for encode, an encoded string for decode. Whitespace is ignored when decoding hex, base64, or base64url; a url value is taken literally.
  • encoding · string · requis · base64 | base64url | hex | url
    The encoding to apply: base64, URL-safe base64url, hex, or URL percent-encoding.
  • operation · string · requis · encode | decode
    "encode" transforms text into the encoding; "decode" recovers the bytes from an encoded value.
  • outputEncoding · string · optionnel · utf8 | hex | base64
    Decode only: how the recovered bytes are returned. utf8 (used when omitted) returns text and fails when the bytes are not valid UTF-8; hex and base64 return the raw bytes re-encoded, losslessly. Rejected when operation is "encode".

  Exemple d'appel

  {"name": "toolkit_encode_value", "arguments": {"value": "texte", "encoding": "base64", "operation": "encode"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"error": {}, "result": "texte", "encoding": "base64", "operation": "encode", "outputEncoding": "utf8"}}

• toolkit_generate_id≈ 787 tokens

  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 minted in the same millisecond are separated by random gaps, so no id in a batch can be derived from another. IDs from this tool feed into toolkit_generate_qr (pass ids[0] as data) to create a scannable code.

  Paramètres, retour & exemple (2)

  Paramètres

  • type · string · optionnel · uuid_v4 | uuid_v7 | ulid
    Identifier format: uuid_v4 (random), uuid_v7 (time-ordered), or ulid (sortable Crockford-base32).
  • count · integer · optionnel
    How many identifiers to mint (1–1000). The full batch is always returned.

  Exemple d'appel

  {"name": "toolkit_generate_id", "arguments": {"type": "uuid_v4", "count": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"ids": [], "type": "uuid_v4", "count": 1, "error": {}}}

• toolkit_generate_qr≈ 1214 tokens

  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 sized in pixels, png_base64 returns base64-encoded PNG bytes (with mimeType and byteLength), and terminal returns plain Unicode half-block characters (no escape codes) for a monospace display, drawn for a dark background: light modules, quiet zone included, are blocks and dark modules are spaces. errorCorrection (L/M/Q/H) trades data capacity for damage tolerance, margin sets the quiet-zone width in modules, and scale sets pixels per module for svg and png_base64, so both are (modules + 2 × margin) × scale pixels per side. The returned version (1–40) reflects how dense the encoded data is. png_base64 rejects an image past 2048 px per side with a typed raster_too_large error, so a dense symbol needs a lower scale; svg is vector markup and carries no such limit.

  Paramètres, retour & exemple (5)

  Paramètres

  • data · string · requis
    The text or URL to encode, stored as UTF-8. Capacity is counted in bytes: 2953 UTF-8 bytes is the absolute ceiling (QR version 40, level L, byte mode). The 2953-character limit here is only an upper bound, since a non-ASCII character takes 2–4 bytes. Usable capacity drops at higher errorCorrection levels, so over-capacity data is rejected with a typed data_too_large error rather than a generic failure.
  • scale · integer · optionnel
    Pixels per module for svg (its width and height) and png_base64. 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 there.
  • format · string · optionnel · svg | png_base64 | terminal
    Output format: svg markup, png_base64 (raster bytes), or terminal (plain Unicode half-blocks, drawn for a dark background).
  • margin · integer · optionnel
    Quiet-zone width in modules around the symbol. The spec recommends 4.
  • errorCorrection · string · optionnel · L | M | Q | H
    Error-correction level: L (~7% recoverable) to H (~30%). Higher tolerance lowers data capacity.

  Exemple d'appel

  {"name": "toolkit_generate_qr", "arguments": {"data": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"error": {}, "format": "svg", "content": "texte", "version": 1, "mimeType": "image/svg+xml", "byteLength": 1}}

• toolkit_geolocate_ip≈ 2692 tokens

  Resolve a public IP or dotted hostname to country, region, city, coordinates, ASN, organization, timezone, and proxy/hosting/mobile flags. Supply target for one lookup or targets for an ordered batch, never both; blank target and empty targets are unset. Batches process the first 100 positions (duplicates retained) and disclose every remainder in unprocessedTargets; at most 1000 inputs are accepted. Each batch position reports its result or an error with recovery, so cached and local outcomes survive quota refusals. The provider is called directly, never the target. Hostnames are DNS-resolved and resolvedIp names the located address. Private/reserved addresses have no public geolocation. Results are best-effort, city-level at best; VPNs, proxies, mobile NAT, and anycast defeat IP-to-location. Read proxy, hosting, and mobile before trusting coordinates: true describes infrastructure, not the user. Absent metadata remains unknown. source names the provider. Single and batch quotas are independent; cache hits consume neither quota.

  Paramètres, retour & exemple (2)

  Paramètres

  • target · ? · optionnel
    One public IP or dotted hostname; mutually exclusive with nonempty targets.
  • targets · array · optionnel
    Ordered public IPs or dotted hostnames; first 100 positions are served, every remainder is disclosed. Mutually exclusive with nonblank target.

  Exemple d'appel

  {"name": "toolkit_geolocate_ip", "arguments": {"target": "texte", "targets": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"asn": "texte", "org": "texte", "city": "texte", "error": {}, "proxy": true, "mobile": true, "region": "texte", "source": "texte", "target": "texte", "country": "texte", "hosting": true, "results": []}}

• toolkit_hash_value≈ 1559 tokens

  Generate a cryptographic digest of a value, or verify a value against an expected digest. Set operation to "generate" for a digest, or "compare" to constant-time-check value against the expected digest — compare is timing-safe and avoids manual string equality checks. Omitting operation compares when expected is supplied and generates otherwise. Algorithm defaults to sha256; sha384 and sha512 are 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. digestEncoding selects the generated digest form: lowercase hex (default), base64, or sri (<algorithm>-<base64>, the npm lockfile integrity and Subresource Integrity form, sha256/sha384/sha512 only). expected is accepted as hex, base64, or SRI, recognized by its shape at the algorithm's digest length, so a published checksum can be pasted as-is; an SRI value may hold several space-separated entries, as an npm integrity field can, and matches when any entry for algorithm does. inputEncoding controls how value is 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 or a lockfile integrity entry.

  Paramètres, retour & exemple (6)

  Paramètres

  • value · string · requis
    The data to hash, interpreted per inputEncoding (raw text by default).
  • expected · string · optionnel
    The digest to compare against, as hex (any case), standard base64, or SRI (<algorithm>-<base64>); the form is recognized from its shape at the algorithm's digest length, and a string of only hex digits is always read as hex. An SRI value may carry several space-separated entries: entries for other algorithms are skipped, and it matches when any entry for algorithm matches. Supplying it with operation omitted runs a compare; it is rejected with operation "generate".
  • algorithm · string · optionnel · sha256 | sha384 | sha512 | sha1 | md5
    Digest algorithm. sha256 (default), sha384, or sha512 for security; md5/sha1 are checksum/compat only — not for security.
  • operation · string · optionnel · generate | compare
    "generate" produces a digest; "compare" constant-time-checks value against expected. When omitted, resolves to "compare" if expected is supplied and "generate" otherwise.
  • inputEncoding · string · optionnel · utf8 | hex | base64
    How value is decoded before hashing: utf8 text, hex, or base64.
  • digestEncoding · string · optionnel · hex | base64 | sri
    Form of the generated digest: lowercase hex (default), standard base64, or sri (<algorithm>-<base64>, sha256/sha384/sha512 only). Applies to operation "generate".

  Exemple d'appel

  {"name": "toolkit_hash_value", "arguments": {"value": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"error": {}, "digest": "texte", "matches": true, "algorithm": "sha256", "operation": "generate", "lengthInBytes": 1}}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://toolkit.caseyjhand.com/mcp