Home / MCP registry index / dev.tanod/text
Tanod Text
dev.tanod/text in the official MCP registry.
Endpoint https://tanod.dev/mcp/text.
The registry describes it as: Text tools: stats, language, case, lines, replace, extract, keywords, summary, sentiment, diff.
We read its 26 tools on 2026-10-28. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
text_stats detect_language text_case text_lines text_replace text_extract redact_pii text_frequency text_keywords text_summarize text_sentiment text_spellcheck text_unicode_inspect text_numbers text_lorem diff_text make_slug markdown_to_html html_to_text convert_subtitles check_subtitle_delivery pdf_redact pdf_redaction_check check_text_for_secrets check_text_sources check_text_duplicate
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/dev-tanod-text)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.