Tanod MCP server

utilpeek: redact PII from text

redact_pii

Read-onlyIdempotent

Mask personally identifiable information in text by replacing emails, phone numbers, card numbers, IBANs, SSNs, IPs, crypto addresses, and URL secrets with tags, stars, or hashes for safe sharing.

Instructions

utilpeek: Redact PII from text: emails, phone numbers, card numbers, IBANs, SSNs, IPs and crypto addresses. For API keys and tokens use check_text_for_secrets. Returns the text with emails, phone numbers, payment cards (Luhn), IBANs (mod-97), US SSNs, IPv4 / IPv6, EVM / BTC addresses and secret URL query values replaced by a tag ([EMAIL]), same-length stars or a short hash, plus each entity's type, input offsets and replacement, and counts by type. RE2 patterns, every hit re-checked; prices, dates and order numbers are left alone. Person names and street addresses are not detected (see not_detected). National phone numbers: North American or trunk-0 formats only, elsewhere the + code is needed. Typically under 1 s. Price: USD 0.002. Free: 10 utilpeek calls per IP per UTC day. The submitted text is never logged or stored. Docs: https://tanod.dev/learn/pii-redaction-api-prices.html

Input Schema

TableJSON Schema

Name	Required	Description	Default
`mask`	No	tag (default: [EMAIL], [PHONE], [CARD] ...), stars (the same number of *, so the length is kept) or hash ([EMAIL:8 hex of SHA-256 of the normalised value]: equal values get equal tags).	tag
`text`	Yes	The text (at most 200,000 characters).
`types`	No	Limit detection to these types: email, phone, card, iban, ssn, ipv4, ipv6, crypto_address, url_secret (default: all).

Output Schema

TableJSON Schema

Name	Required	Description
`mask`	No
`text`	No
`count`	No
`error`	No	Only on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
`notes`	No
`types`	No
`source`	No
`by_type`	No
`entities`	No
`not_detected`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Oct 15, 2026

TDQS

A4.8/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well beyond the annotations, which only cover safety (readOnly/idempotent/non-destructive). It discloses detection mechanics (RE2 with re-checking, Luhn, mod-97), format caveats (national phone formats need + code), latency (<1s), price, free-tier limit, and a no-logging guarantee.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads purpose and the routing to the sibling in the first two sentences; the rest is dense but each clause carries operational value (limits, caveats, docs). Slightly packed, with pricing/docs link tacked onto the tail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, yet the description still summarizes the return shape (masked text plus per-entity type, offsets, replacement, counts). Combined with detection exclusions, format caveats, and limits, an agent has everything needed to invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents all three parameters. The description still adds practical meaning, notably the phone-format constraint on 'phone' detection and how mask modes affect output, going modestly beyond the schema text.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Redact PII from text') and enumerates exactly which entity types are handled (emails, phones, cards, IBANs, SSNs, IPs, crypto). It also names the sibling that handles the adjacent task, so it is distinguishable without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes the agent: 'For API keys and tokens use check_text_for_secrets.' It also gives when-not guidance by listing what is left alone (prices, dates, order numbers) and what is not detected (person names, street addresses).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server