# ellmos-clatcher-mcp

Utility MCP server: JSON repair, encoding fixes, conversion, duplicates, batch rename, archives.

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the package rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 1.0.10
- **Author:** io.github.ellmos-ai
- **License:** Unknown
- **npm:** ellmos-clatcher-mcp
- **Source:** https://github.com/ellmos-ai/ellmos-clatcher-mcp
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

60/100 (B), scored on the package rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 12 days

## Security scan

- **Status:** warnings
- **Scanned:** 2026-08-16T12:58:24.317Z
- **Version scanned:** 1.0.14
- **CVEs:** none found by OSV at scan time

## Tools

12 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `fix_json`
- `fix_encoding`
- `fix_umlauts`
- `convert_format`
- `detect_dupes`
- `folder_diff`
- `batch_rename`
- `archive`
- `checksum`
- `cleanup_file`
- `scan_emoji`
- `regex_test`

## Install

**Verdict: review** — Installable, but 1 thing to check first: No publisher has proved control of this listing; it is indexed, not vouched for.
**Cautions** (coverage gaps and advisories — never blocking)
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"ellmos-clatcher\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"ellmos-clatcher-mcp\"\n      ]\n    }\n  }\n}"
```

## Blast radius

Moderate to extensive — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: mutates data; runs on your machine.
- Floor 30, ceiling 54 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/ellmos-clatcher-mcp
- Install plan: https://forgeregistry.com/api/v1/packages/ellmos-clatcher-mcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/ellmos-clatcher-mcp
- HTML page: https://forgeregistry.com/registry/ellmos-clatcher-mcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.