MCP.so
Sign In

Cleanor Tools

@cleanor-app

About Cleanor Tools

Zero-auth hosted MCP for AI builders — 22 tools: image optimize/convert (WebP/AVIF/JPEG), QR, cited Cleanor Labs storage & image-format data, plus 18 deterministic dev utilities (hash, HMAC, UUID, JWT, JSON, regex, cron, datetime, color, diff…) LLMs get wrong. No API key.

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "cleanor": {
      "url": "https://mcp.cleanor.app/mcp"
    }
  }
}

Tools

22

Fetch an image from a public URL and re-encode it smaller (WebP/AVIF/JPEG), optionally resizing to a target width. Returns the optimized image plus before/after byte sizes. Use this when an AI-generated or dropped-in asset (hero image, screenshot, illustration) is too large to ship.

How many photos or minutes of video actually fit in a given storage size, corrected for real OS/filesystem overhead. Backed by Cleanor Labs measured per-item sizes. Use for realistic sample copy, dashboards, or "how many photos fit in 128 GB" answers.

How much smaller WebP, AVIF or JPEG XL are than JPEG at matched perceptual quality, from Cleanor Labs’ controlled benchmark. Also reports the "HEIC conversion tax" (converting an iPhone HEIC to JPG/PNG makes it bigger). Use to justify a format choice when building a site or app.

Encode text or a URL as a QR code and return a crisp, dependency-free SVG you can paste straight into a page, deck or doc.

Compute a cryptographic hash of text (SHA-1, SHA-256, SHA-384 or SHA-512) and return the hex digest. Use for checksums, cache keys, or verifying content. MD5 is intentionally not offered (broken, and unavailable in Web Crypto). LLMs cannot compute these reliably by hand, so always use this tool instead of guessing.

Generate one or more UUIDs. v4 is fully random; v7 is time-sortable (recommended for database keys). LLMs cannot produce cryptographically random or correctly-formatted UUIDs, so always use this tool.

Encode text to Base64 or decode Base64 back to text (UTF-8 safe). Supports URL-safe alphabet. Use whenever you need to encode/decode data URIs, tokens, or config values instead of guessing the bytes.

Validate JSON and pretty-print or minify it, optionally sorting object keys. Returns a precise parse error (with position) if invalid. Use to check and clean JSON instead of eyeballing it.

Decode a JSON Web Token into its header and payload so you can inspect claims (iss, exp, sub, scopes). The signature is NOT verified and no secret is required or stored. Use to read a token during debugging.

Convert a color (hex, rgb() or hsl()) and return hex, RGB and HSL representations at once. Use when picking or translating colors for CSS, design tokens or themes.

Turn a title or phrase into a clean, URL-safe slug (lowercase, hyphenated, accents stripped). Use when generating page paths, filenames or anchor IDs.

Accurately count characters (Unicode code points), UTF-16 units, words, lines and UTF-8 bytes in text. LLMs are notoriously bad at counting, so always use this tool for "how many characters/words" questions.

Test a JavaScript regular expression against sample text and return whether it matches, plus every match with its captured groups and index. Use to verify a pattern instead of reasoning about it in your head. Input and pattern are length-capped to keep it fast and safe.

Parse a standard 5-field cron expression (minute hour day-of-month month day-of-week) into a plain-English breakdown and the next few run times in UTC. Use to sanity-check a schedule instead of guessing what the fields mean.

Convert a value between units of length, mass, data size, time, speed or temperature. Supported units: mm, cm, m, km, in, ft, yd, mi, nmi, mg, g, kg, t, oz, lb, st, bit, byte, kb, kib, mb, mib, gb, gib, tb, tib, ms, s, min, h, day, week, mps, kph, mph, fps, knot, c, f, k. Use for exact conversions instead of approximating.

Get the current date/time, or convert a given timestamp, into a target IANA timezone with ISO, Unix and human-readable forms. Pass a Unix timestamp (seconds or ms) or an ISO string as input; omit it for "now". LLMs cannot know the real current time, so use this instead of guessing.

Break a URL into its components: scheme, host, port, path, decoded query parameters and fragment. Use to inspect or debug a URL instead of parsing it by eye.

Convert an integer between number bases 2–36 (e.g. hex to binary, decimal to base-36). Arbitrary precision via BigInt, so large values stay exact. Use for radix conversions instead of doing them by hand.

Compute a line-by-line diff between two texts, marking removed lines with "-", added with "+" and unchanged with two spaces, plus a change count. Use to see exactly what changed instead of comparing by eye. Capped at 1000 lines per side.

Compute an HMAC (keyed hash) of a message with a secret, using SHA-1/256/384/512, returned as hex or Base64. Use to sign webhook payloads or verify a signature instead of guessing. LLMs cannot compute this by hand.

Generate a lightweight SVG placeholder image at any size, with an optional label and custom background/text colors. Dependency-free, pastes straight into a page or mockup. Use for wireframes and design stubs instead of hotlinking a placeholder service.

Build a harmonious color palette from a base color using color-theory rules (complementary, analogous, triadic, tetradic, or monochromatic). Returns each color as hex and HSL. Use to derive a theme or design tokens from one brand color.

Overview

What is Cleanor Tools?

Cleanor Tools is a zero‑auth, hosted Model Context Protocol (MCP) server that optimizes images and returns cited research data from Cleanor Labs. It is designed for AI builders who need image re‑encoding and verified device‑storage or image‑format statistics without signing up or managing API keys.

How to use Cleanor Tools?

Connect any MCP client to the Streamable HTTP endpoint https://mcp.cleanor.app/mcp. Alternatively, run the server locally via npx using the @cleanor/mcp package. Example configurations for Claude Code, Cursor, and Claude Desktop are provided in the README.

Key features of Cleanor Tools

  • Zero‑auth, hosted, and free MCP server
  • Optimize images to WebP, AVIF, or JPEG (optional resize)
  • Return cited research on storage capacity and format savings
  • 22 read‑only tools for image, data, and developer operations
  • Streamable HTTP transport, no API key required
  • All responses link sources on cleanor.app

Use cases of Cleanor Tools

  • An AI agent optimizes a user‑generated image before storing or sharing it
  • A storage planning tool uses cited data to estimate photo/video capacity per GB tier
  • A workflow compares real‑world file‑size savings of modern image formats
  • A developer utility decodes JWTs, formats JSON, or tests regex without extra libraries
  • A design tool generates QR codes, color palettes, or placeholder images instantly

FAQ from Cleanor Tools

Does Cleanor Tools require an API key or signup?

No. The server is zero‑auth and every response is free with no account needed.

What is the server endpoint?

https://mcp.cleanor.app/mcp via Streamable HTTP. Local usage is also supported with npx -y @cleanor/mcp.

How many tools are available and are any dangerous?

22 tools are currently available. All are read‑only and explicitly safe to expose to autonomous agents. The first four handle image optimization and cited research data; the remaining 18 are deterministic developer utilities.

Where does the research data come from?

Real, cited data from Cleanor Labs studies, covering device storage capacity, next‑generation image‑format savings (WebP, AVIF,

Frequently asked questions

Does Cleanor Tools require an API key or signup?

No. The server is zero‑auth and every response is free with no account needed.

What is the server endpoint?

`https://mcp.cleanor.app/mcp` via Streamable HTTP. Local usage is also supported with `npx -y @cleanor/mcp`.

How many tools are available and are any dangerous?

22 tools are currently available. All are read‑only and explicitly safe to expose to autonomous agents. The first four handle image optimization and cited research data; the remaining 18 are deterministic developer utilities.

Where does the research data come from?

Real, cited data from Cleanor Labs studies, covering device storage capacity, next‑generation image‑format savings (WebP, AVIF,

Comments

More Developer Tools MCP servers