Tanod Util

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as dev.tanod/util and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 8 Oct 2026. Not supplied by the maker.

• text_encode

  utilpeek: the text encoded or decoded with `codec`: base64, base64url, base32, hex, url (percent), html (entities), quoted_printable, rot13, punycode, idna or jwt. Decoders are strict (bad input is a

• hash_text

  utilpeek: hex digests of the text (as UTF-8) or base64 bytes you send: md5, sha1, sha256, sha512, sha3_256, blake2b (64-byte), keccak256 (Ethereum's Keccak-256, not sha3_256) and crc32. md5 and sha1 a

• hmac_sign_verify

  utilpeek: the HMAC of a message under a shared key (sign), or whether a signature matches it, compared in constant time (verify). Built for webhook signatures: GitHub's X-Hub-Signature-256 (`sha256=<h

• generate_ids

  utilpeek: 1-100 new identifiers: random UUID v4, time-ordered UUID v7 (RFC 9562) or ULIDs, optionally strictly increasing within the response (v7 and ULID; per response on purpose, so one caller canno

• validate_json

  utilpeek: whether a JSON value is valid against a JSON Schema (draft from $schema, default 2020-12; 2019-09, 7, 6, 4 and 3 recognised), with up to 100 errors (instance path, schema path, message, vali

• convert_data

  utilpeek: the document converted from json, yaml, csv, toml or xml to json, yaml, csv or toml. YAML is read with libyaml's restricted loader (no Python tags) and alias bombs are refused; XML with DTDs

• validate_identifier

  utilpeek: check the format and check digits of an identifier. Input: `kind` (iban, bic, vat, isbn, issn, ean, isin, lei, imo, luhn, or a national format: au_abn, br_cnpj, br_cpf, ca_bn, ch_uid, de_idn

• parse_phone_number

  utilpeek: parse and format a phone number. Input: `number` (1-64 chars; international form +CC ..., or a national form together with `region`, an ISO 3166-1 alpha-2 code such as US). Returns `valid`,

Is this tool yours?

Claim this listing and we’ll verify ownership before handing it over.