npm Lockfile Check
Server Details
Compares package.json with its lockfile and reports drifting direct dependencies. x402 per call.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-06-18
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 1 tool
There is only one tool, and its purpose—comparing package.json against an npm lockfile—is stated explicitly with no competing functionality. An agent cannot misselect between tools because no alternatives exist.
The single French name 'controle-verrouillage' (noun phrase, kebab-case) is readable and internally coherent, but there is no multi-tool set against which to verify a consistent verb_noun convention. It also deviates from the common English/verb-first pattern used by most MCP servers, which could slow recognition for non-French agents.
One tool is thin even for a narrow domain; a check-only surface leaves no room for related operations like repairing drift or listing resolved versions. It is defensible for a tightly scoped utility, but borderline by the rubric's 1-2 tool guidance.
The tool covers detection (direct dependency alignment, divergent versions, missing lockfile entries) but offers no remediation or write operations, so an agent that finds drift hits a dead end. Output-format or recursive/transitive-dependency handling also appear absent.
Available Tools
1 toolcontrole-verrouillageAInspect
Compare un manifeste npm (package.json) à son lockfile (package-lock.json / npm-shrinkwrap.json) : aligne les dépendances directes, signale les versions divergentes et localise les entrées absentes du lockfile.
Inputs: lockfile (required), manifeste (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Deterministic package.json upgrade plans: age gate, aligned peers, reasons per change. No AI.
Diff two npm/PyPI versions or lockfiles: new install scripts, network/shell/eval calls, new deps.
Check PyPI and npm upgrades: known vulnerabilities, the safe version, and what each upgrade breaks.
npm/PyPI package dependency upgrade reviews: security, runtime compatibility, cited migration.
Related MCP Servers
- AlicenseAqualityBmaintenanceRead-only npm dependency diagnostics: inventory, audit and health checks from package-lock.json, no account needed.4265 npmMIT
- AlicenseAqualityBmaintenanceEnables AI coding agents to ground dependency setup, compatibility checks, and major-version migration advice in a project's real runtime, lockfiles, and config files. It parses local project state and npm registry metadata deterministically, then returns tag-pinned install commands, breaking changes, and upgrade steps rather than generic documentation.521 npmMIT
- AlicenseAqualityDmaintenanceGives coding agents the exact installed version of each dependency in a project from node_modules and lockfile, preventing deprecated API usage by grounding them in reality.34 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables comparing the Node.js major versions declared in package.json, CI workflow YAML, and Dockerfile image tags to surface mismatches, below-minimum sources, and unpinned images before a build breaks. Runs as a pure local computation with no network access or configuration.79 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.