Other · Local MCP server
lockvet
Explain any lockfile or workflow-pin change: bumps, vulns, ages, deprecations - 61 formats.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.matteo-sung/lockvet- Version
- 0.6.20
- Status
- Active
- Category
- other
- Transport
- stdio (local process)
- Package
- OCI image (Docker)
- Published
- 2026-09-15
- Updated
- 2026-09-15
- Publisher
- matteo-sung (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/matteo-sung) · how
- Website
- matteo-sung.github.io/lockvet/
- Repository
- github.com/matteo-sung/lockvet
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| OCI image (Docker) | ghcr.io/matteo-sung/lockvet:0.6.20 | - | stdio |
How to connect lockvet
lockvet runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: ghcr.io/matteo-sung/lockvet:0.6.20. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run - the usual command is docker run -i --rm -e GITHUB_TOKEN -e GITLAB_TOKEN -e BITBUCKET_TOKEN -e GITEA_TOKEN -e AZURE_DEVOPS_TOKEN ghcr.io/matteo-sung/lockvet:0.6.20. It reads these environment variables: GITHUB_TOKEN (secret), GITLAB_TOKEN (secret), BITBUCKET_TOKEN (secret), GITEA_TOKEN (secret) and AZURE_DEVOPS_TOKEN (secret); set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"lockvet": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"GITHUB_TOKEN",
"-e",
"GITLAB_TOKEN",
"-e",
"BITBUCKET_TOKEN",
"-e",
"GITEA_TOKEN",
"-e",
"AZURE_DEVOPS_TOKEN",
"ghcr.io/matteo-sung/lockvet:0.6.20"
],
"env": {
"GITHUB_TOKEN": "<secret>",
"GITLAB_TOKEN": "<secret>",
"BITBUCKET_TOKEN": "<secret>",
"GITEA_TOKEN": "<secret>",
"AZURE_DEVOPS_TOKEN": "<secret>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| LocizeLocize TMS: 26 tools for translations, TM/glossary/styleguide/screenshot context, versions. OAuth. | Remote · HTTPLive check: sign-in required |
| LockboxEncrypted secrets for Next.js. AES-256-GCM with no vault needed. | Local · stdio |
| lockdocsExact-version library docs from your lockfile - local, offline, no rate limits. | Local · stdio |
| Lockstep MCPLocal lockfile and package-manager reproducibility analysis without dependency details. Tools... | Local · stdio |
| LocusHierarchical markdown memory palace for AI agents - structured palace navigation via MCP tools. | Local · stdio |
| Lodestar StampDated, source-linked receipts before an agent recommends or books. Lodestar does not approve. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| LogiLogi (1pass) IdP - manage your OAuth apps, redirect URIs, passkeys, login history and docs. | Local · stdio |
| Logi ApprovalLogi Agent Approval Gate - human approval on the phone before high-risk agent actions. | Local · stdio |