Toolchain Lens Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.0Updated Nov 5, 2026

Local explanation of reproducibility signals and toolchain contradictions without exact versions...

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

A local MCP server that inspects a small project's toolchain and CI files and explains reproducibility signals and contradictions without exposing exact…

What you can do
  • Inspect a local project's toolchain files: package-manager files, runtime declarations, container files and CI configuration
  • Report coarse contradictions and missing anchors as structural signal labels
  • Return only filenames, categories and signal labels, with no exact versions, dependency names, command output, environment values or secret contents
When to use it
Useful when you want an assistant to sanity-check whether a small project pins its toolchain consistently across package manager, runtime, container and CI files, without revealing version or dependency details.
Requirements
Runs as a local stdio process installed from the npm package toolchain-lens-mcp; needs Node.js and a build step (npm install, npm run build). Access is bounded by the TOOLCHAIN_LENS_ROOT environment variable, which must point at the project root. No authentication or API keys are declared.
Before you install
It reads files from the local filesystem, limited to a bounded allowlist under TOOLCHAIN_LENS_ROOT with realpath checks; Git data, dependencies, build output, coverage, caches and vendor directories are skipped. It is an explanation aid only, not a build executor, lockfile validator or vulnerability scanner, so its findings should not be treated as authoritative validation.

Installation

In SourceWeft

  1. Open Toolchain Lens 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

toolchain-lens-mcp

Toolchain Lens is a local MCP tool for explaining reproducibility signals in small projects. It looks at package-manager files, runtime declarations, container files, and CI configuration, then reports coarse contradictions and missing anchors.

Tool

  • explain_toolchain: inspect a local project without returning exact versions, dependency names, command output, environment values, or secret contents.

Safety

  • Local paths only, bounded by TOOLCHAIN_LENS_ROOT and realpath checks.
  • Reads only a bounded allowlist of toolchain and CI files.
  • Skips Git data, dependencies, build output, coverage, caches, and vendor directories.
  • Returns filenames, categories, and structural signal labels only.
  • This is an explanation aid, not a build executor, lockfile validator, or vulnerability scanner.

Run

bash
npm installnpm run buildnode dist/index.js

Source: README.md at commit b38f4fd

Tools

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

Version history

1
  1. v1.0.0LatestSep 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.