artifact-gauge-mcp
# artifact-gauge-mcp
Artifact Gauge is a local MCP tool for answering a simple release question: what is taking up space? It reports artifact totals, extension histograms, largest files, and dependency manifest metadata without returning file contents.
## Tools
- `inspect_artifacts`: scan a bounded local project and summarize file sizes and types.
- `inspect_manifest`: report metadata for one recognized dependency manifest without exposing its contents or dependency versions.
## Safety
- Local paths only, with `ARTIFACT_GAUGE_ROOT` boundary support and symlink checks.
- Skips Git data, dependencies, coverage, framework caches, and other common generated caches while intentionally including `dist` and `build` artifacts.
- Caps recursion, file count, file size, and output.
- Never returns file contents, package versions, secrets, or source text.
- This is a size heuristic, not a complete bundler or dependency vulnerability analyzer.
## Run
```bash
npm install
npm run build
node dist/index.js
```
TDQS
Scored across 2 tools
Both tools involve inspection, but inspect_artifacts provides a broad overview of artifact sizes and extensions, while inspect_manifest targets a single dependency manifest. The scope difference is clear, though the shared 'inspect' prefix could cause minor confusion.
Both tools use a consistent verb_noun pattern (inspect_artifacts, inspect_manifest), making their purposes predictable and the naming style uniform.
With only two tools, the server feels minimal and borderline for a meaningful tool set. However, the two tools cover different granularities, making the count somewhat reasonable for a focused inspection-only purpose.
The tools cover the main inspection needs: a high-level artifact overview and detailed single-manifest metadata. There may be gaps like per-file detail inspection, but within the stated non-invasive inspection scope, the surface is fairly complete.