lockvet
OCI · GHCR.IO/MATTEO-SUNG/LOCKVET:0.6.20
Explain any lockfile or workflow-pin change: bumps, vulns, ages, deprecations — 61 formats
Available components
Last scanned (12 hours ago)
Scores higher than 98% of OCI servers
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to matteo-sung/lockvet). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 50 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2602 tokens (~433/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 1 Nov 26 0
- Stability: 0.97 → pass security
- 31 Oct 26 0
- Stability: pass → 0.97 functional
- 25 Oct 26 0
- Stability: 0.97 → pass security
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed oci/ghcr.io/matteo-sung/lockvet:0.6.20
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | oci |
| Reason | Verified |
| Discovered via | OCI referrers API |
| Source repo | matteo-sung/lockvet |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/matteo-sung/lockvet/.github/workflows/docker.yml@refs/tags/v0.6.20 |
| Rekor log index | 2846751252 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha256:6663dbf3f359bdc2df14d33d9fd7902740c0dc2470b5782a10b9d4dfe16a37f4 |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
audit Audit what the lockfiles pin right now ~259
Audit the CURRENT dependency set of a project — not a change: every lockfile under the directory is checked in full (a .lockvetignore file there is honoured). Reports each pinned version that is affected by a known advisory (OSV.dev), missing from its registry's index (what an unpublished or pulled — often malicious — release looks like), deprecated/retracted/yanked/abandoned upstream, or published only days ago. Run it to answer "is anything we currently depend on known-bad?" — e.g. after news of a supply-chain attack, or as a periodic hygiene check.
| Name | Type | Req | Description |
|---|---|---|---|
| dir | string | – | directory to audit (walked recursively; node_modules/vendor/.git skipped; default: current directory) |
| format | string | – | output format (default "markdown") |
| fresh_days | integer | – | flag versions published fewer than N days ago (default 7; 0 shows ages but never flags) |
| offline | boolean | – | skip all network lookups (no vulnerability, age, or deprecation data) |
| only | string | – | only report packages whose name — or any package in their "via" chain — matches this pattern (glob, case-insensitive, comma list ok, e.g. "@babel/*") |
No output schema declared.
No examples provided.
queue Triage every open Dependabot/Renovate PR at once ~350
Vet EVERY open dependency-update PR/MR of a repo, user, org, group, workspace, or project in one table, sorted most-alarming first: which introduce vulnerabilities, which are major or brand-new bumps, which look routine. Scope: a GitHub owner or owner/repo, or a GitLab / Gitea / Bitbucket / Azure DevOps URL (e.g. gitlab.com/gitlab-org, codeberg.org/forgejo, bitbucket.org/atlassian, dev.azure.com/ORG/PROJECT). Defaults to Dependabot+Renovate authors; bot usernames vary on self-hosted forges — pass author to override, or "any" for every open PR touching a lockfile.
| Name | Type | Req | Description |
|---|---|---|---|
| author | string | – | bot accounts to search for (comma list; "any" = every open PR/MR that touches a lockfile) |
| format | string | – | output format (default "markdown") |
| fresh_days | integer | – | flag versions published fewer than N days ago (default 7; 0 shows ages but never flags) |
| limit | integer | – | vet at most N pull/merge requests (default 30) |
| offline | boolean | – | skip all network lookups (no vulnerability, age, or deprecation data) |
| only | string | – | only report packages whose name — or any package in their "via" chain — matches this pattern (glob, case-insensitive, comma list ok, e.g. "@babel/*") |
| scope | string | yes | GitHub owner or owner/repo, or a GitLab group/project, Gitea owner/repo, Bitbucket workspace/repo, or Azure DevOps project URL |
No output schema declared.
No examples provided.
vet_files Vet two lockfiles or SBOMs on disk ~295
Explain the dependency changes between two files on disk, no git needed: two lockfiles (any of the 61 supported formats; one side may carry a suffix, e.g. Cargo.lock.orig vs Cargo.lock) or two CycloneDX/SPDX JSON SBOMs under any filename — e.g. syft scans of two container images.
| Name | Type | Req | Description |
|---|---|---|---|
| changelogs | boolean | – | also fetch upstream release notes for every bump, including the releases a multi-version jump skips over (GitHub Releases first, then the repo's CHANGELOG/CHANGES/NEWS/HISTORY file at the verified ta… |
| format | string | – | output format (default "markdown") |
| fresh_days | integer | – | flag versions published fewer than N days ago (default 7; 0 shows ages but never flags) |
| new_path | string | yes | path to the new lockfile or SBOM |
| offline | boolean | – | skip all network lookups (no vulnerability, age, or deprecation data) |
| old_path | string | yes | path to the old lockfile or SBOM |
| only | string | – | only report packages whose name — or any package in their "via" chain — matches this pattern (glob, case-insensitive, comma list ok, e.g. "@babel/*") |
No output schema declared.
No examples provided.
vet_git Vet lockfile changes in a local git repository ~345
Explain the lockfile/dependency changes in a local git repository: working tree vs HEAD by default, or any revision range (base=HEAD~5, or base=main target=my-branch). Same report as vet_url: bumps with semver severity, vulnerabilities introduced/fixed, release ages, deprecations, license changes, via-chains. A .lockvetignore file in the repo (acknowledged findings) is honoured. Run it before committing or merging a dependency update.
| Name | Type | Req | Description |
|---|---|---|---|
| base | string | – | base revision (default "HEAD"); ranges like "main...topic" work too |
| changelogs | boolean | – | also fetch upstream release notes for every bump, including the releases a multi-version jump skips over (GitHub Releases first, then the repo's CHANGELOG/CHANGES/NEWS/HISTORY file at the verified ta… |
| dir | string | – | path to the git repository (default: current directory) |
| format | string | – | output format (default "markdown") |
| fresh_days | integer | – | flag versions published fewer than N days ago (default 7; 0 shows ages but never flags) |
| offline | boolean | – | skip all network lookups (no vulnerability, age, or deprecation data) |
| only | string | – | only report packages whose name — or any package in their "via" chain — matches this pattern (glob, case-insensitive, comma list ok, e.g. "@babel/*") |
| target | string | – | target revision (default: working tree) |
No output schema declared.
No examples provided.
vet_package Vet a package before installing it ~481
Vet one or more packages BEFORE they are in any lockfile — the moment you are deciding whether to npm install / pip install / cargo add them. Reports known advisories affecting the version (OSV.dev, including MAL malicious-package records), release age (brand-new releases are higher-risk), deprecation/retraction/yank status with the upstream reason, versions missing from the registry index (what an unpublished or pulled — often malicious — release looks like), and typosquat suspicion (names one edit from a popular package). Specs look like eco:name[@version] — npm:left-pad, pypi:requests@2.32.0, cargo:serde, go:github.com/gin-gonic/gin, maven:com.google.guava:guava, jsr:@std/http, swift:Alamofire/Alamofire. With no version, the registry's latest is looked up (npm, PyPI, crates.io, RubyGems, Packagist, Go, Hex, Pub, JSR, NuGet, Maven, CocoaPods, Terraform, conda, CRAN, Hackage, Bazel, Helm charts (helm:<repo-url>/<chart>), Ansible Galaxy (ansible:namespace.name — collections and classic roles), GitHub Actions, Swift, pre-commit:owner/repo hook repos, component:host/project/name GitLab CI components, orb:namespace/name CircleCI orbs, vcpkg:<port> vcpkg ports, tool:node / tool:terraform asdf-mise tools verified against the tool's own repository tags). Run this before adding any new dependency.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | output format (default "markdown") |
| fresh_days | integer | – | flag versions published fewer than N days ago (default 7; 0 shows ages but never flags) |
| offline | boolean | – | skip all network lookups (no vulnerability, age, or deprecation data) |
| only | string | – | only report packages whose name — or any package in their "via" chain — matches this pattern (glob, case-insensitive, comma list ok, e.g. "@babel/*") |
| packages | array | yes | package specs, eco:name[@version] (e.g. ["npm:left-pad", "pypi:requests@2.32.0"]) |
No output schema declared.
No examples provided.
vet_url Vet a pull request, compare range, or commit by URL ~525
Explain the lockfile/dependency changes of a pull/merge request, compare range, or commit on GitHub, GitLab, Bitbucket Cloud, Gitea/Forgejo (incl. Codeberg), or Azure DevOps — no clone needed. Reports every added/removed/bumped package with semver severity, vulnerabilities introduced/fixed/unresolved (OSV.dev), release age, deprecations, license changes, unlisted versions, typosquat-suspect additions (new young packages one edit from a popular name), integrity changes on unchanged versions, SwiftPM/workflow/toolchain (.tool-versions, mise.toml) pins verified against upstream tags (moved-tag and not-a-release catches) and private-to-public registry resolution moves (dependency-confusion shape), npm install-script and npm/PyPI/crates.io/RubyGems provenance-dropped transitions (ages/deprecations cover Packagist, hex.pm, pub.dev, jsr.io, CocoaPods, CRAN, Helm chart repositories and Ansible Galaxy too), direct-vs-transitive origin with via-chains, and verified upstream changelog/diff links. Accepts PR/MR URLs, compare URLs, commit URLs, or shorthands like owner/repo#123 (GitHub) and group/project!123 (GitLab). Uses GITHUB_TOKEN / GITLAB_TOKEN / BITBUCKET_TOKEN / GITEA_TOKEN / AZURE_DEVOPS_TOKEN from the environment when present; public repos work unauthenticated.
| Name | Type | Req | Description |
|---|---|---|---|
| changelogs | boolean | – | also fetch upstream release notes for every bump, including the releases a multi-version jump skips over (GitHub Releases first, then the repo's CHANGELOG/CHANGES/NEWS/HISTORY file at the verified ta… |
| format | string | – | output format (default "markdown") |
| fresh_days | integer | – | flag versions published fewer than N days ago (default 7; 0 shows ages but never flags) |
| offline | boolean | – | skip all network lookups (no vulnerability, age, or deprecation data) |
| only | string | – | only report packages whose name — or any package in their "via" chain — matches this pattern (glob, case-insensitive, comma list ok, e.g. "@babel/*") |
| url | string | yes | PR/MR, compare, or commit URL (or owner/repo#123 / group/project!123 shorthand) |
No output schema declared.
No examples provided.
How do I install the lockvet MCP server?
lockvet runs locally as a container image, launched with docker run --rm -i -e GITHUB_TOKEN -e GITLAB_TOKEN -e BITBUCKET_TOKEN -e GITEA_TOKEN -e AZURE_DEVOPS_TOKEN ghcr.io/matteo-sung/lockvet:0.6.20. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/matteo-sung/lockvet:0.6.20
claude mcp add matteo-sung-lockvet -- docker run --rm -i -e GITHUB_TOKEN -e GITLAB_TOKEN -e BITBUCKET_TOKEN -e GITEA_TOKEN -e AZURE_DEVOPS_TOKEN ghcr.io/matteo-sung/lockvet:0.6.20
This image reads GITHUB_TOKEN, GITLAB_TOKEN, BITBUCKET_TOKEN, GITEA_TOKEN and AZURE_DEVOPS_TOKEN. Set them in your client's env block for this server; docker run -e passes each one through to the container.
What is the lockvet MCP server?
lockvet is an MCP server listed in the public MCP registry as io.github.matteo-sung/lockvet. Explain any lockfile or workflow-pin change: bumps, vulns, ages, deprecations, 61 formats. This page covers its container image (ghcr.io/matteo-sung/lockvet:0.6.20).
Is the lockvet MCP server safe to use?
lockvet scores 62 out of 100 on VerifyMCP. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the lockvet MCP server expose?
lockvet exposes 6 tools: vet_url, vet_git, audit, vet_files, vet_package, queue. Their descriptions and schemas cost roughly 2,255 tokens of context every time the server is loaded.
Is the lockvet MCP server still maintained?
lockvet is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the lockvet MCP server under?
lockvet declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.