dependency-version MCP server
Commit Oct 26, 2026Lets an AI client look up package versions, scan for vulnerabilities, and analyze dependencies across multiple registries like npm, PyPI, and Docker Hub.
Also known as Tripletex/mcp-dependency-version
- Stars
- 5
- Tools
- 17
- Downloads, 30 days
- —
- Latest version
- —
- Last commit
- Oct 26, 2026
- License
- MIT
What is dependency-version MCP?
dependency-version lets an AI client look up package versions, scan for vulnerabilities, and analyze dependencies across multiple registries like npm, PyPI, and Docker Hub. It exposes 17 tools, such as registry, package, includePrerelease.
Summary generated from the project's README
About dependency-version MCP server
Checking package versions and scanning for vulnerabilities across multiple registries is what this MCP server enables for developers using AI clients. It provides a centralized way to inspect dependencies from sources like npm, PyPI, Maven Central, Docker Hub, and GitHub Actions. By integrating this server, an AI can assist in maintaining secure and up-to-date software supply chains by identifying the latest stable releases and checking them against OSV and NVD databases.
Users can run the server locally using Node.js, Bun, or Deno, or deploy it via Docker. It supports complex setups through a configuration file that allows for private registries and custom mirrors using bearer tokens or basic authentication. The server includes specialized tools for Docker and GitHub Actions to help users move from mutable tags to secure, immutable references like image digests or commit SHAs.
What you can do with it
- 1Find latest stable versionsRequest the most recent stable version of a specific package from registries like npm or PyPI.
- 2Secure Docker deploymentsRetrieve specific image digests to replace mutable tags in your Dockerfiles for better security.
Written from the project's README. Every use case is checked against a quote from it.
dependency-version MCP tools 17
Detected from the READMEregistrypackageincludePrereleaseversionPrefixversionReferencecurrentDigestlimitversionseverityThresholdcontentcheckVulnerabilitiespackages
Show all 17 toolsShow fewer tools
foundnot-declaredregistry-unsupportederrorisCopyleft
Configuration
MCP_DEPENDENCY_VERSION_CONFIG
Automated checks
Ran Nov 14, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachabletripletex/mcp-dependency-version is public and reachablegithub.com/tripletex/mcp-dependency-version ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-10-26github.com/tripletex/mcp-dependency-version ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model17 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNo tool named like delete, drop or execPass
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHubMCP Dependency Version
A Model Context Protocol (MCP) server for looking up package versions across multiple package registries.
Features
- Multi-registry support: npm, Maven Central, PyPI, crates.io, Go proxy, JSR, NuGet, Docker Hub, RubyGems, Packagist, pub.dev, Swift PM, GitHub Actions
- Version lookup: Get the latest stable (and optionally prerelease) versions
- Version listing: List all available versions with metadata
- Vulnerability scanning: Check packages against OSV and NVD databases with deduplicated, CVSS-scored results
- License lookup: Fetch the declared license for one or many packages in a single call, with explicit status for unsupported registries or undeclared licenses
- Dependency analysis: Analyze dependency files and check for updates
- Docker support: Look up image tags and analyze Dockerfile/docker-compose.yml dependencies
Security: Use Exact Versions
Always use exact versions instead of version ranges to prevent supply chain attacks.
| Bad (vulnerable) | Good (secure) |
|---|---|
^1.2.3 |
1.2.3 |
~1.2.3 |
1.2.3 |
>=1.2.3 |
1.2.3 |
1.x |
1.2.3 |
Version ranges (like ^1.2.3 or ~1.2.3) allow automatic updates when new
minor or patch versions are published. If an attacker compromises a package and
publishes a malicious version, your project could automatically pull it in
without your knowledge.
Using exact versions ensures you control exactly which code runs in your project. When you want to update, explicitly change the version and review the changes.
Docker: Use Digest-Pinned References
Docker tags are NOT immutable. Unlike package versions in npm/PyPI/etc., a Docker tag can be moved to point to a completely different image at any time.
| Bad (vulnerable) | Good (secure) |
|---|---|
nginx:1.27.3 |
nginx@sha256:1948e0c46... |
postgres:16 |
postgres@sha256:abc123... |
When you use nginx:1.27.3, the image you pull today may be different from the
one you pull tomorrow if the tag is updated. This creates a supply chain attack
vector.
Use digest-pinned references (image@sha256:...) to ensure you always pull
the exact same image. The lookup_version and list_versions tools return the
digest and secureReference fields for Docker images to make this easy.
GitHub Actions: Use Commit SHA-Pinned References
GitHub Action tags are NOT immutable. Tags like v4 can be force-pushed to
point to a different commit at any time, creating a supply chain attack vector.
| Bad (vulnerable) | Good (secure) |
|---|---|
actions/checkout@v4 |
actions/checkout@b4ffde65... # v4.2.0 |
actions/setup-node@v4 |
actions/setup-node@1a4442c... # v4.0.1 |
Use commit SHA-pinned references (owner/repo@sha) to ensure you always use
the exact same action code. The lookup_version and list_versions tools
return the digest (commit SHA) and secureReference fields for GitHub Actions
to make this easy.
Monorepo actions
Actions that live as subdirectories of a shared repository are referenced with
their path (uses: org/actions/deploy@...) and are supported as
owner/repo/path package names. Two versioning conventions are recognized:
- Per-action tags: the repository tags each action's releases by prefixing
the version with the action name —
deploy-v1.2.3ordeploy@v1.2.3(the action name may itself contain dashes). When such tags exist for the action, only they are considered, and repo-level tags (v54,v1.2.3) are ignored for that action. - Repo-level tags: repositories like
github/codeql-actionversion their subpath actions (init,analyze, ...) with plain repository-wide semver tags. When an action has no prefixed tags, these are used as a fallback.
Version lookups, listings, update analysis, and commit SHA pinning all work on the per-action versions.
Supported Registries
| Registry | API Endpoint | Package Format |
|---|---|---|
| npm | registry.npmjs.org | package-name, @scope/package |
| maven | repo1.maven.org/maven2 | groupId:artifactId |
| pypi | pypi.org | package-name |
| cargo | crates.io | crate-name |
| go | proxy.golang.org | github.com/user/repo |
| jsr | api.jsr.io | @scope/name |
| nuget | api.nuget.org | Package.Name |
| docker | hub.docker.com | image, user/image |
| rubygems | rubygems.org | gem-name |
| packagist | packagist.org | vendor/package |
| pub | pub.dev | package_name |
| swift | api.github.com | owner/repo |
| github-actions | api.github.com | owner/repo |
Installation
Prerequisites
Install one of these runtimes, depending on how you want to start the server:
- Node.js v18.18 or later for
npx - Bun v1.2 or later for
bunxor direct Bun runs - Deno v2.x or later for source-based Deno runs
Run with npx or bunx
npx -y --package github:Tripletex/mcp-dependency-version mcp-dependency-version
bunx --bun github:Tripletex/mcp-dependency-version
These commands start an MCP stdio server, so direct terminal runs wait for MCP JSON-RPC input and do not print a prompt.
Setup with Claude Code CLI
Choose one of these commands.
Using npx:
claude mcp add mcp-dependency-version -- npx -y --package github:Tripletex/mcp-dependency-version mcp-dependency-version
Using Bun:
claude mcp add mcp-dependency-version -- bunx --bun github:Tripletex/mcp-dependency-version
Using Deno from a local checkout:
claude mcp add mcp-dependency-version -- deno run --allow-net --allow-env --allow-read /path/to/mcp-dependency-version/main.ts
Setup with Codex CLI
Choose one of these commands.
Using npx:
codex mcp add mcp-dependency-version -- npx -y --package github:Tripletex/mcp-dependency-version mcp-dependency-version
Using Bun:
codex mcp add mcp-dependency-version -- bunx --bun github:Tripletex/mcp-dependency-version
Using Deno from a local checkout:
codex mcp add mcp-dependency-version -- deno run --allow-net --allow-env --allow-read /path/to/mcp-dependency-version/main.ts
Setup with Codex config.toml
Codex stores MCP configuration in ~/.codex/config.toml. You can also use a
project-scoped .codex/config.toml in trusted projects.
Using npx:
[mcp_servers."mcp-dependency-version"]
command = "npx"
args = ["-y", "--package", "github:Tripletex/mcp-dependency-version", "mcp-dependency-version"]
Using Bun:
[mcp_servers."mcp-dependency-version"]
command = "bunx"
args = ["--bun", "github:Tripletex/mcp-dependency-version"]
Using Deno from a local checkout:
[mcp_servers."mcp-dependency-version"]
command = "deno"
args = ["run", "--allow-net", "--allow-env", "--allow-read", "/path/to/mcp-dependency-version/main.ts"]
Setup with Claude Desktop using npx
{
"mcpServers": {
"mcp-dependency-version": {
"command": "npx",
"args": [
"-y",
"--package",
"github:Tripletex/mcp-dependency-version",
"mcp-dependency-version"
]
}
}
}
Setup with Claude Desktop using bunx
{
"mcpServers": {
"mcp-dependency-version": {
"command": "bunx",
"args": ["--bun", "github:Tripletex/mcp-dependency-version"]
}
}
}
Setup with Claude Desktop using Deno
Add to your Claude Desktop configuration file
(~/Library/Application Support/Claude/claude_desktop_config.json on macOS,
~/.config/claude-desktop/claude_desktop_config.json on Linux):
{
"mcpServers": {
"mcp-dependency-version": {
"command": "deno",
"args": [
"run",
"--allow-net",
"--allow-env",
"--allow-read",
"/path/to/mcp-dependency-version/main.ts"
]
}
}
}
Setup with Docker
The service is available as a Docker image using stdio transport.
Pull the image:
docker pull ghcr.io/tripletex/mcp-dependency-version:latest
Run directly:
docker run --rm -i ghcr.io/tripletex/mcp-dependency-version:latest
Claude Desktop configuration:
{
"mcpServers": {
"mcp-dependency-version": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/tripletex/mcp-dependency-version:latest"
]
}
}
}
Local Development
-
Clone the repository:
git clone https://github.com/tripletex/mcp-dependency-version.git cd mcp-dependency-version -
Run the server:
deno task startOr run it with Bun:
bun run main.ts
Configuration
The server supports custom repository configurations for each registry type. This allows you to use private registries, mirrors, or multiple repositories per registry.
Configuration File
Create a configuration file at ~/.config/mcp-dependency-version/config.json:
{
"repositories": {
"npm": {
"npmjs": {
"name": "npm",
"url": "https://registry.npmjs.org",
"default": true
},
"github": {
"name": "GitHub Packages",
"url": "https://npm.pkg.github.com",
"auth": {
"token": "ghp_xxxxxxxxxxxx"
}
}
},
"maven": {
"central": {
"name": "Maven Central",
"url": "https://repo1.maven.org/maven2",
"default": true
},
"atlassian": {
"name": "Atlassian Maven",
"url": "https://packages.atlassian.com/maven/public"
},
"jitpack": {
"name": "JitPack",
"url": "https://jitpack.io"
}
},
"pypi": {
"pypi": {
"name": "PyPI",
"url": "https://pypi.org/pypi",
"default": true
},
"private": {
"name": "Private PyPI",
"url": "https://pypi.example.com/simple",
"auth": {
"username": "user",
"password": "pass"
}
}
}
}
}
Environment Variables
You can override the config file path using the MCP_DEPENDENCY_VERSION_CONFIG
environment variable:
export MCP_DEPENDENCY_VERSION_CONFIG=/path/to/config.json
Alternatively, pass the entire configuration as inline JSON via
MCP_DEPENDENCY_VERSION_CONFIG_JSON. When set, it takes precedence over the
config file. This is convenient in containerized setups (e.g. an MCP gateway
starting the server with docker run) where injecting an environment variable
is easier than mounting a file:
docker run --rm -i \
-e MCP_DEPENDENCY_VERSION_CONFIG_JSON="$(cat config.json)" \
ghcr.io/tripletex/mcp-dependency-version:<tag>
If the variable contains invalid JSON, a warning is printed to stderr and the server falls back to the config file (then to the built-in defaults).
Authentication
The configuration supports two authentication methods:
Bearer Token:
{
"auth": {
"token": "your-token-here"
}
}
Basic Auth:
{
"auth": {
"username": "user",
"password": "pass"
}
}
Tokens are stored as plain text in the config file — environment variables are
not expanded inside config values. Restrict the file's permissions accordingly
(chmod 600).
GitHub authentication (github-actions and swift)
The github-actions and swift registries are backed by the GitHub API. For
these registries, repository entries are configured with the web URL of the
organization or repository — not the API endpoint — and the entry whose URL is
the longest prefix of the package's GitHub URL supplies the authentication. This
lets different organizations use different tokens, which is how you give the
server access to actions in private repositories:
{
"repositories": {
"github-actions": {
"tripletex": {
"name": "Tripletex (private)",
"url": "https://github.com/Tripletex",
"auth": { "token": "ghp_private_org_token" }
},
"github": {
"name": "GitHub public (authenticated)",
"url": "https://github.com/",
"default": true,
"auth": { "token": "ghp_public_token" }
}
}
}
}
With this configuration, a lookup of Tripletex/deploy-action uses the private
org token, while actions/checkout matches the bare https://github.com/ entry
and uses the public token (raising the GitHub API rate limit from 60 to 5,000
requests/hour). Omit the auth block on the default entry to keep public
lookups unauthenticated.
Matching rules:
- Longest URL prefix wins:
https://github.com/Tripletex/special-repobeatshttps://github.com/Tripletex, which beatshttps://github.com/. - Owner and repository comparison is case-insensitive, matching GitHub's behavior.
- Entries that do not match fall back to the
default: trueentry, then to the first configured entry. - The API base URL is derived from the entry's host:
github.comuseshttps://api.github.com, and any other host (GitHub Enterprise Server) useshttps://<host>/api/v3. Legacy entries that point directly athttps://api.github.comkeep working as default/fallback entries but are never selected by URL matching.
For GitHub Enterprise, set the default entry to your GHES host (either
https://ghe.example.com/ or the explicit https://ghe.example.com/api/v3).
Package names such as owner/repo carry no host, so unmatched lookups go to
whichever entry is the default.
A fine-grained personal access token with read-only contents and metadata
permissions on the relevant repositories is sufficient for version lookups.
Default Repositories
If no configuration file exists, the server uses the official public registries:
| Registry | Default URL |
|---|---|
| npm | https://registry.npmjs.org |
| maven | https://repo1.maven.org/maven2 |
| pypi | https://pypi.org/pypi |
| cargo | https://crates.io/api/v1/crates |
| go | https://proxy.golang.org |
| jsr | https://api.jsr.io |
| nuget | https://api.nuget.org/v3 |
| docker | https://hub.docker.com |
| rubygems | https://rubygems.org |
| packagist | https://repo.packagist.org |
| pub | https://pub.dev/api |
| swift | https://api.github.com |
| github-actions | https://api.github.com |
Tools
lookup_version
Look up the latest version of a package.
Parameters:
registry(required): Package registry (npm,maven,pypi,cargo,go,jsr,nuget,docker,rubygems,packagist,pub,swift,github-actions)package(required): Package nameincludePrerelease(optional): Include alpha/beta/rc versionsversionPrefix(optional): Filter to a semver version line and return the newest match (e.g.,"2."for 2.x). Mutually exclusive withversionReference.versionReference(optional): Resolve a floating, non-semver target to its current concrete pin -- a git branch/ref (github-actions:"main"), or a named dist-tag/channel (npm:"next"; docker:"latest"). Returns the resolved version and, where supported, a commit SHA /sha256:digest indigest, flaggedisMutable: true. Supported forgithub-actions,swift,npm, anddocker. Mutually exclusive withversionPrefix.currentDigest(optional): Reverse-resolve an existing digest pin to the version it corresponds to. Forgithub-actionsandswift, a commit SHA (full 40 characters or a prefix of at least 7); fordocker, asha256:digest. The response adds apinobject with the matching tags, the pinned version, and the update type relative to the latest version. Mutually exclusive withversionPrefixandversionReference.
Example:
{
"registry": "npm",
"package": "lodash"
}
Output:
{
"packageName": "lodash",
"registry": "npm",
"latestStable": "4.17.21",
"publishedAt": "2021-02-20T15:42:16.891Z"
}
Docker Output (includes digest for secure pinning):
{
"packageName": "nginx",
"registry": "docker",
"latestStable": "1.27.3",
"publishedAt": "2024-12-04T18:51:59.819Z",
"digest": "sha256:1948e0c46da16a3565a844aa65ab848e1546f85cf47e47d044a567906a3a497f",
"secureReference": "nginx@sha256:1948e0c46da16a3565a844aa65ab848e1546f85cf47e47d044a567906a3a497f",
"securityNotes": [
"WARNING: Docker tags are NOT immutable. A tag can be moved to point to a different image at any time.",
"Using the digest-pinned reference (image@sha256:...) provides protection against tag tampering.",
"Digest-pinned references ensure you always pull the exact same image, preventing supply chain attacks.",
"When updating, explicitly change the digest and verify the new image before deployment."
]
}
GitHub Actions Output (includes commit SHA for secure pinning):
{
"packageName": "actions/checkout",
"registry": "github-actions",
"latestStable": "4.2.0",
"publishedAt": "2024-10-01T12:00:00.000Z",
"digest": "b4ffde65f46336ab88eb53be808477a3936bae11",
"secureReference": "actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # v4.2.0",
"securityNotes": [
"GitHub Action tags are NOT immutable. Tags can be force-pushed to point to different commits.",
"The commit SHA for this version is returned in the 'digest' field.",
"Use commit SHA-pinned references (owner/repo@<digest>) for supply chain security.",
"Secure reference: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # v4.2.0"
]
}
Resolving a floating reference (versionReference):
Resolve a GitHub Actions branch to its current commit SHA for pinning:
{
"registry": "github-actions",
"package": "actions/checkout",
"versionReference": "main"
}
{
"packageName": "actions/checkout",
"registry": "github-actions",
"latestStable": "main",
"digest": "b4ffde65f46336ab88eb53be808477a3936bae11",
"secureReference": "actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # main",
"isMutable": true,
"resolvedReference": "main",
"securityNotes": [
"GitHub Action branches and tags are NOT immutable. Branches move and tags can be force-pushed to point to different commits.",
"You are tracking the mutable branch 'main'. Its current commit SHA is returned in the 'digest' field.",
"Pin to the commit SHA for supply chain security: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # main",
"Updating means re-resolving branch 'main' to its latest commit, not moving to a release."
]
}
Reverse pin lookup (currentDigest):
Identify which version an existing SHA pin corresponds to, and how far behind it is:
{
"registry": "github-actions",
"package": "actions/checkout",
"currentDigest": "b4ffde65f46336ab88eb53be808477a3936bae11"
}
{
"packageName": "actions/checkout",
"registry": "github-actions",
"latestStable": "7.0.0",
"digest": "8edcb1bdb4e267140fa742c62e395cd74f332709",
"secureReference": "actions/checkout@8edcb1bdb4e267140fa742c62e395cd74f332709 # v7.0.0",
"pin": {
"digest": "b4ffde65f46336ab88eb53be808477a3936bae11",
"matches": [
{ "reference": "v4.2.0", "version": "4.2.0" },
{ "reference": "v4", "version": "4.2.0" }
],
"pinnedVersion": "4.2.0",
"updateType": "major"
}
}
For Docker, one digest commonly maps to several tags (1.27.3, 1.27,
latest, ...); all matches are returned and per-architecture digest matches are
annotated in detail. When nothing matches -- an untagged commit, a
force-pushed tag's previous target, or a digest older than the fetched tag page
-- pin.matches is empty and pin.notes explains the possible causes.
list_versions
List all available versions of a package.
Parameters:
registry(required): Package registrypackage(required): Package namelimit(optional): Maximum versions to return (default: 20)
Example:
{
"registry": "pypi",
"package": "requests",
"limit": 5
}
Output:
{
"packageName": "requests",
"registry": "pypi",
"versions": [
{
"version": "2.31.0",
"publishedAt": "2023-05-22T15:12:44.000Z",
"isPrerelease": false,
"isDeprecated": false
}
],
"totalCount": 142,
"showing": 5
}
check_vulnerabilities
Check a package version for known security vulnerabilities.
Queries both OSV and NVD in parallel for comprehensive coverage. Results are deduplicated by CVE ID — when a vulnerability appears in both databases, NVD's CVSS v3.1 score is used as the authoritative severity rating.
Set the NVD_API_KEY environment variable for higher NVD rate limits (50 vs 5
requests per 30 seconds). Request a free key at
https://nvd.nist.gov/developers/request-an-api-key.
Parameters:
registry(required): Package registrypackage(required): Package nameversion(required): Version to checkseverityThreshold(optional): Minimum severity (LOW,MEDIUM,HIGH,CRITICAL)
Example:
{
"registry": "npm",
"package": "lodash",
"version": "4.17.20"
}
Output:
{
"packageName": "lodash",
"version": "4.17.20",
"registry": "npm",
"vulnerabilities": [
{
"id": "GHSA-29mw-wpgm-hmr9",
"summary": "Prototype Pollution in lodash",
"severity": "HIGH",
"cvss": 7.2,
"cveIds": ["CVE-2021-23337"],
"cweIds": ["CWE-94"],
"fixedVersions": ["4.17.21"],
"source": "osv+nvd"
}
],
"totalCount": 1,
"hasVulnerabilities": true,
"summary": {
"critical": 0,
"high": 1,
"medium": 0,
"low": 0
}
}
dependency-version MCP questions
What tools does dependency-version MCP provide?
It exposes 17 tools, including registry, package, includePrerelease, versionPrefix, versionReference.
How can I secure my Docker images?
You should use digest-pinned references instead of tags to ensure you pull the exact same image every time.
Does it support private registries?
Yes, you can configure custom repositories for each registry type to use private registries or mirrors via a configuration file.