Artifact Gauge Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.7Updated Oct 30, 2026

Local build artifact size and dependency weight inspection without file content output. Tools...

VerifiedSTDIODesktop onlyFiles & StorageDeveloper Tools

Overview

AI-generated overview

Local MCP server that inspects build artifact sizes and dependency manifest metadata in a project without returning file contents.

What you can do
  • Scan a bounded local project and summarize file sizes and types, including extension histograms and largest files
  • Report metadata for one recognized dependency manifest without exposing its contents or dependency versions
  • Keep results within a configured root boundary, skipping Git data, dependencies, coverage and caches while including dist and build output
When to use it
Useful when you want an assistant to answer release questions like what is taking up space in a build, or to get a quick size and file-type breakdown of a project before shipping.
Requirements
Runs as a local stdio process installed from the npm package; requires Node.js and a build step. Optionally set the ARTIFACT_GAUGE_ROOT environment variable to bound scanning to a directory. No authentication or API keys declared.
Before you install
It reads local project paths, so point it at the intended directory and rely on the root boundary and symlink checks. It reports sizes and manifest metadata only, not file contents, versions or secrets, and it is a size heuristic rather than a full bundler or vulnerability analyzer.

Installation

In SourceWeft

  1. Open Artifact Gauge Mcp in the dashboard and add it to a workspace.
  2. 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

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 installnpm run buildnode dist/index.js

Source: README.md at commit c93dd38

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v1.0.7LatestOct 29, 2026
  2. v1.0.1Sep 22, 2026

Score

40% 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

    Declare a license in the repository or the registry entry.