Home / MCP registry index / app.cleanor/cleanor
Cleanor
app.cleanor/cleanor in the official MCP registry.
Endpoint https://mcp.cleanor.app/mcp. Source: github.com/cleanor-app/cleanor-mcp.
The registry describes it as: Zero-auth MCP: image optimize, cited storage/format data, and dev utilities LLMs get wrong.
We read its 22 tools on 2026-10-22. 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
optimize_image storage_capacity image_format_savings qr_code hash uuid base64 json_format jwt_decode color slugify count regex_test cron_describe unit_convert datetime url_parse base_convert diff hmac placeholder_image color_palette
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/app-cleanor-cleanor)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.