packagetrackdev
Reads text-format bun.lock to analyze Bun-managed npm dependencies; the binary bun.lockb format is not supported.
Supports Composer lock files as the input for Packagist dependency analysis and release-note reporting.
Reads gradle.lockfile as part of Maven-ecosystem dependency analysis.
Reads npm lock files such as package-lock.json and npm-shrinkwrap.json, plus package.json fallback, to report outdated or withdrawn npm dependencies and release notes between versions.
Reads packages.lock.json to report NuGet dependency versions that are behind or have been withdrawn.
Reads composer.lock to report Packagist/PHP dependency versions that are behind or withdrawn.
Reads pnpm-lock.yaml to analyze pnpm-managed npm dependencies for outdated or withdrawn package versions.
Reads poetry.lock to analyze Poetry-managed PyPI dependencies for outdated or withdrawn versions.
Reads Python lock and manifest files such as uv.lock, Pipfile.lock, requirements.txt, and poetry.lock to report PyPI dependency status.
Reads Yarn lock files, including classic and Berry formats, to analyze dependency versions that are behind or withdrawn.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
packagetrackdev
Command-line client for PackageTrack. Reads the lock file in a project and reports which dependencies are behind, which installed versions have been withdrawn, and what the release notes in between say.
Supported lock files:
Ecosystem | Files |
npm |
|
PyPI |
|
crates.io |
|
Packagist |
|
pub.dev |
|
NuGet |
|
Maven |
|
Go |
|
Falls back to package.json, requirements.txt or pom.xml when there is
no lock file; these give direct dependencies only, with versions only where
the file states them. The binary bun.lockb is not read: run
bun install --save-text-lockfile to write bun.lock.
Install
macOS and Linux:
curl -fsSL https://packagetrack.dev/install.sh | shWindows (PowerShell):
irm https://packagetrack.dev/install.ps1 | iexInstalls uv if needed, then this package and
packagetrackdev-mcp
as uv tools, each checked against its published SHA256 first. No root or
administrator rights required. To reinstall or update, run the same command
again. The checked wheels stay in ~/.packagetrack/wheels: uv records the
file it installed from, and uv tool upgrade --all reads it again.
Limits: the checksum covers this package's own wheel. Its dependencies are
downloaded by uv from PyPI and rest on PyPI's own checks, not on ours.
Where scripts are blocked, or to install only the CLI, follow
the steps by hand: download the
file, check its SHA256 yourself, install it with uv.
Requires Python 3.11+.
Related MCP server: driftwatch-mcp
Updates
packagetrackdev updateDownloads the newest release from https://packagetrack.dev, checks its
SHA256, starts it once in a separate process, and unpacks it under
~/.packagetrack/cli/<version>/. The next command runs it, and
packagetrackdev --version shows both, for example 0.4.0 (active: 0.4.1).
Nothing uv installed is changed. Once a day after a command, one line on
stderr says when a newer release exists; PACKAGETRACK_NO_AUTO_UPDATE=1
turns that line off.
Coming from 0.2.x up to 0.3.1: those releases have no update. Run the
install command above once; after that, packagetrackdev update is enough.
The newest release on this computer always runs, and there is no way back
to an older one. If a release here is newer than the one the site serves
(for example after the site went back to an earlier release), update
changes nothing and says so. packagetrackdev update --follow-server then
installs the release the site serves, with the same checks, and only after
that removes the newer folders.
A release that needs a newer Python or newer packages than this installation
has is not taken: update asks you to run the install command again (exit
code 3).
Limits:
The checksum covers this package's own wheel. Its dependencies come from PyPI through
uv.Releases are not signed. The checksum comes from the same site as the wheel, so it catches a broken download, not a compromised site.
Releases on this computer are trusted as far as your user account is. On macOS and Linux, a release folder that another user owns or can write to is skipped; on Windows the profile's permissions are relied on.
Uninstall
uv tool uninstall packagetrackdev packagetrackdev-mcpThen delete ~/.packagetrack/wheels (%USERPROFILE%\.packagetrack\wheels
on Windows), the checked wheels uv installed from. Uninstall first: while a
tool is installed, uv tool upgrade --all reads its wheel there. The rest of
~/.packagetrack holds your settings and API key (config.toml), the
releases update unpacked (cli) and the server's own updates (mcp).
Deleting cli removes every release update installed, and the copy uv
installed runs again. Delete the whole folder to remove everything.
For a coding agent, also remove the entry: claude mcp remove packagetrackdev.
Usage
packagetrackdev check # report on the current directory, no account needed
packagetrackdev push --name my-app # upload the dependency set to your dashboard
packagetrackdev login --api-key pkgt_...Common options:
Option | Description |
| Directory to read. Default: current directory. |
| Read only one ecosystem: |
| PackageTrack server. Default: |
| Print the request payload and send nothing. |
|
|
push needs an API key, from packagetrackdev login, the
PACKAGETRACK_API_KEY environment variable, or --api-key.
What is sent
Package names and versions, and for push, which package required which.
No source code, file paths or repository name. --dry-run prints the exact
payload.
Coding agents
The archive is also available to Claude Code, Cursor and other MCP clients through packagetrackdev-mcp:
claude mcp add -s user packagetrackdev -- packagetrackdev-mcpDevelopment
uv sync
uv run pytestLicense
MIT
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Real-time package and vulnerability data (Python, npm, Cargo, Go, and more) for AI coding agents.
Package intelligence for AI agents across npm, PyPI, crates.io and deps.dev. No API keys.
Package intelligence for AI agents across npm, PyPI, crates.io and deps.dev. No API keys.
Release notes and changelogs from across the web, indexed for agents. Also via CLI and REST API.
Related MCP Servers
- AlicenseAqualityBmaintenanceProvides software supply-chain intelligence for AI agents, enabling them to query package metadata, versions, downloads, dependencies, and health signals for npm, PyPI, and crates.io packages without API keys.666 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to identify exactly what broke between two dependency versions, with citations for every claim, and to verify package existence to catch typosquatting, all without requiring an API key.MIT
- AlicenseNot gradedqualityCmaintenanceEnables checking whether software packages are deprecated, archived, stale, active, or unknown with supporting evidence, auditing dependency manifests, and looking up runtime support and end-of-life dates.MIT
- AlicenseAqualityCmaintenanceEnables coding agents to query package release histories, version lists, and change summaries across PyPI, npm, crates.io, Packagist, NuGet, pub.dev, Go, and Maven Central to inform dependency upgrades and detect withdrawn versions.5MIT