
Layercheck
io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Nov 3, 2026
Dockerfile layer and waste analyzer: layer sizes biggest first, with deterministic waste flags.
Overview
Layercheck's local MCP server; no sign-in required; STDIO.
No AI overview yet: these facts come from the registry entry and the server itself.
Installation
In SourceWeft
- Open Layercheck in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
layercheck
Every RUN, COPY, and ADD in a Dockerfile leaves a layer in the image, and layers are where image size and build-cache pain live. layercheck reads a Dockerfile as plain text — no docker daemon, no build — and reports what it finds:
- every instruction, parsed with
\continuations joined and blank lines and#comments skipped, each marked with whether it produces a layer - the layer count, and — when you supply per-layer sizes
(as
docker historyreports them) — the total size and the layers ranked biggest first, so the fattest layer is the first thing you see - deterministic waste flags, each with the line it fires on:
CONSECUTIVE_RUN— a RUN immediately after another RUN; the two could be one layerBROAD_COPY_EARLY— aCOPY . .(or./) placed before the dependency install step, busting its cache on every source changeAPT_LEFTOVER—apt-get installwithout removing/var/lib/apt/listsin the same RUNADD_LOCAL— ADD used for an ordinary local file, where COPY is the clearer instruction (remote URLs and archives are fine)
If the supplied sizes do not line up with the number of layer-producing instructions, layercheck says so and names both counts instead of silently misaligning them.
CLI
sizes.json is a JSON array of numbers: the size in bytes
of each layer-producing instruction, in Dockerfile order.
The analysis is printed as one JSON object:
{layer_count, total_size_bytes, instructions, biggest_layers, waste_flags}.
Exit codes: 0 on success, 1 on a runtime error
(including an unreadable file or a sizes length mismatch),
2 on a usage error.
MCP server
MCP client config:
Tools
analyze_dockerfile_layers— Analyze a Dockerfile's layers and flag wasted ones.dockerfile(string, required) — the Dockerfile textlayer_sizes(array of numbers, optional) — size in bytes of each layer-producing instruction, in Dockerfile order; its length must equal the number of layer-producing instructions
Docker
Development
License
MIT — Copyright (c) 2026 Rene Turcios
Source: README.md at commit 010d19d
Tools
0Version history
1- v0.1.0LatestNov 3, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts