lockvet MCP server
Explain any lockfile or workflow-pin change: bumps, vulns, ages, deprecations — 61 formats
C68/100grade C
Adoption
New
0 stars
Reviews
Write oneNobody has reviewed lockvet yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
lockvet tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.5 · 2026-09-19 · same rubric, same numbers if you re-run it
no findings
- –Code scanpackage could not be scannedn/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitystatic API keys via environment variables6/15
- Maintenancelast push 3 days ago15/15
- Maintainer identityregistry namespace matches repository owner6/10
Overall 68/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
Install directly
claude mcp add lockvet -- docker run -i --rm ghcr.io/matteo-sung/lockvet:0.6.20
lockvet: common questions
- Is lockvet MCP server safe?
- With care: it is graded C, so read the findings first (68/100). Read the lockvet safety report
- How do I install lockvet?
- It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
- Does lockvet need an API key?
- Yes. The registry entry asks for
GITHUB_TOKEN,GITLAB_TOKEN,BITBUCKET_TOKEN,GITEA_TOKENand 1 more. - Is lockvet maintained?
- The last commit was 4 days ago (2026-09-17). The latest release is v0.6.20.