Lockstep MCP server

by mrfentmen·io.github.mrfentmen/lockstep-mcp·v1.0.0

No reviews yet

Local lockfile and package-manager reproducibility analysis without dependency details. Tools...

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 Lockstep yet.

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

Lockstep tools (1)

write = sends, deletes, buys or posts

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

inspect_reproducibility
Inspect local package-manager lockfile presence and structural signals without returning dependency names or versions.

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 Lockstep 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 Lockstep in Claude Code, Cursor or VS Code

Runs npx -y @mrfentmen/lockstep-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add lockstep-mcp -- npx -y @mrfentmen/lockstep-mcp

Add to Cursor

What the publisher says

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

lockstep-mcp

Lockstep is a local MCP tool for spotting reproducibility drift in small projects. It identifies package-manager lockfiles, counts their bytes and lines, detects structural lockfile markers, and flags a package manifest with no matching lockfile.

Tool

inspect_reproducibility: inspect lockfile presence and package-manager signals without returning dependency names or versions.

Safety

Local paths only, bounded by LOCKSTEP_ROOT and realpath checks.
Skips Git data, dependencies, build output, coverage, and caches.
Never returns dependency names, versions, lockfile contents, or environment values.
Caps recursion, file count, file size, and output.
This is a reproducibility aid, not a dependency vulnerability scanner or build oracle.

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

Lockstep: common questions

Is Lockstep MCP server safe?: Yes, by our scan: it is graded A (85/100). Read the Lockstep safety report
How do I install Lockstep?: It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Lockstep need an API key?: Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Lockstep maintained?: The last commit was 87 days ago (2026-08-09). The latest release is v1.0.0.
How does Lockstep 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.