MCP

Check hygiene of Russian text pasted from chat

For scanning chat-paste leftovers in Russian before you decide to polish. Install humanizer-ru with pip first, and do not run polish on Markdown as-is.

Official source · humanizer-ru

Install

pip install humanizer-ru

Who it is for

For people who want a checkable hygiene pass on Russian pasted from a chat UI, then decide whether to polish. humanizer-ru is for Russian text and offers verifiable paste-hygiene handling. Over MCP, the same commands are exposed as humanizer-mcp on stdio, matching the tools in contract.v1.json. Text stays in this process; these tools do not send it out.

Not for people whose main work is Markdown drafts and who plan to run polish immediately: polish strips ##, **, book-title-style quotes, and dashes. Only with --preserve-markup may you polish marked-up text. Also not for people who have not installed the Python package and only change client config — the service command is humanizer-mcp after install.

First try in 3 minutes

Use only one official path: install the package, then write the only MCP config as humanizer-mcp. Do not add a second installer beside it.

pip install humanizer-ru

Client config location is this row in the MCP server table:

{
  "mcpServers": {
    "humanizer-ru": { "command": "humanizer-mcp" }
  }
}

Prerequisites: a Python that can run pip on this machine, and a client that can start stdio MCP. Do not put a key placeholder in the config; this service does not ask for an API key.

The first call uses the scan command written in the source: look at markers first, do not polish yet. Prepare the sample and scan as in the source:

python -c "open('primer.txt','w',encoding='utf-8').write('Согласно отчёту :contentReference[oaicite:3]{index=3}, рост заявок.\n')"
humanizer-markers --scan primer.txt; echo "rc=$?"

Success: the command finishes and prints the exit code after rc=, and you can see whether the scan marked chat leftovers in the sample. On the MCP side the same commands travel in a JSON-RPC envelope; errors follow the contract as isError. This is a local file read and scan, not zero risk: it writes primer.txt on this machine and reads that file.

After the scan works, if you want polish, then consider the MCP tool humanizer_polish. For Markdown you must add --preserve-markup, or it will strip headings and bold markers.

Use cases

Case 1: check leftover markers in a chat paste. Use humanizer-markers --scan (the same command set over MCP) on Russian just pasted into the editor. For confirming “are there chat-citation leftovers” before rewriting. The source only demonstrates a scan of primer.txt and an exit code; it does not enumerate every marker kind.

Case 2: after you confirm this is not a typeset draft, do a fact check or polish. MCP offers humanizer_facts, and humanizer_polish in the same pattern as the CLI. Do not run polish on Markdown as-is; use --preserve-markup when markers must stay. The source gives no parameter table for these two tools; if it is missing, stop at the names and the limits above.

Limits

The package name is humanizer-ru, the MCP process is humanizer-mcp, the contract is contract.v1.json. Text does not leave the process, but local files are still read, and a sample such as primer.txt may be written. polish breaks Markdown unless --preserve-markup. The source does not write an undo path. JSON-RPC errors use isError. Official notes:

https://github.com/Vladimir-Human/humanizer-ru