npm Lockfile Check MCP server
io.sslip.149-56-208-69/npm-lockfile-check149-56-208-69.sslip.iostreamable-httpv1.0.0Scanned
Compares package.json with its lockfile and reports drifting direct dependencies. x402 per call.
1 tool: 1 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the npm Lockfile Check MCP server can do
The npm Lockfile Check MCP server is published by 149-56-208-69.sslip.io, a domain the MCP Registry verified. It has 1 tool. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Last scanned Nov 20, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
1 tool
Only reads 1Show 1 read-only tool
controle-verrouillageCompare 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…No findings
Why it is in this group
- The description's first verb is "compare": a word for reading.
Description, as the server wrote it 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.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http npm-lockfile-check https://149-56-208-69.sslip.io/api/saas/topic-dependencies-packagesclaude mcp add --transport http npm-lockfile-check https://149-56-208-69.sslip.io/api/saas/topic-dependencies-packagesRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__npm-lockfile-check__controle-verrouillage"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as npm-lockfile-check. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.sslip.149-56-208-69/npm-lockfile-check/verify?hash=c30042ee2ee17df20204cb4031b12a94a9412cf381d2d2d7ec9fa638e8dd4edd" | jq -e '.changed == false'Pinned hash c30042ee2ee1, from Nov 20, 2026, 23:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.sslip.149-56-208-69/npm-lockfile-check/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.sslip.149-56-208-69/npm-lockfile-check)Source: MCP Registry. Synced Nov 20, 2026, 23:18 UTC.
npm Lockfile Check MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the npm Lockfile Check MCP server safe?
- No scan can promise that. What its definitions show: 1 tool, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the npm Lockfile Check MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the npm Lockfile Check MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the npm Lockfile Check MCP server have?
- 1 tool: 1 read. controle-verrouillage.
Does the npm Lockfile Check MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the npm Lockfile Check MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.