Toolchain Lens MCP server

by mrfentmen·io.github.mrfentmen/toolchain-lens-mcp·v1.0.0

No reviews yet

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

A85/100grade A

Write a review Install

What users say

No reviews yet

Be the first

Safety scan

A85/100

full report

Adoption

New

0 stars

Reviews

Write one

Nobody has reviewed Toolchain Lens yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Toolchain Lens tools (1)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

explain_toolchain
Explain local reproducibility signals and contradictions without returning exact versions, dependency names, or secret values.

Public scan report

scanner v0.1.10 · 2026-11-01 · same rubric, same numbers if you re-run it

no findings

Code scan8 source files scanned25/25
–Live reliabilityno gateway calls yet and no remote to proben/a
–Tool poisoningtools not inspected (local package is not executed); not countedn/a
Auth qualitylocal package, no credentials required12/15
Maintenancelast push 85 days ago12/15
Maintainer identityregistry namespace matches repository owner6/10

Overall 85/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

How Toolchain Lens compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score: 85/100; higher than 70% of 48,255 servers
Tools: 1; the typical server has 7
Tools that change things: 0%; typical: 0%. Fewer write tools means less an agent can break

What its tools let an agent do: 1 read

Install Toolchain Lens in Claude Code, Cursor or VS Code

Runs npx -y toolchain-lens-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add toolchain-lens-mcp -- npx -y toolchain-lens-mcp

Add to Cursor

What the publisher says

From the Toolchain Lens repository's README, as published. We do not edit it. Read it on GitHub

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 TOOLCHAINLENSROOT 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

npm install
npm run build
node dist/index.js

Nothing above is checked by us. What we check is on the safety report.

Toolchain Lens: common questions

Is Toolchain Lens MCP server safe?: Yes, by our scan: it is graded A (85/100). Read the Toolchain Lens safety report
How do I install Toolchain Lens?: It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Toolchain Lens need an API key?: Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Toolchain Lens maintained?: The last commit was 87 days ago (2026-08-09). The latest release is v1.0.0.
How does Toolchain Lens compare with other MCP servers?: safety score 85/100 (higher than 70% of 48,255 servers); tools 1 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.