Package Latest Version Check
Server Details
Latest npm and PyPI versions, deprecated or yanked versions, and how many majors behind you are.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 2 tools
check_version validates a specific version (existence, yanked status, distance behind latest) while latest_version reports the current latest release, so the two target different inputs and outputs. There is mild overlap since check_version's 'how far behind latest' output implicitly requires latest-version data, which could lead an agent to pick the wrong tool for a pure 'what's newest' query.
Both names are snake_case and share the '_version' suffix, giving a recognizable pattern. The minor deviation is that one uses a verb (check_) and the other an adjective/noun (latest_), so the verb_noun convention isn't strictly uniform.
Two tools is thin even for a narrow domain, and both revolve around the same lookup operation. The scope is genuinely small, but a couple more operations (e.g. listing available versions or comparing a range) would make the surface feel complete rather than minimal.
The core workflows — get latest and validate a specific version — are covered, but notable gaps remain: no way to list version history, check a range of versions, or batch-check multiple packages in one call. Agents can work around these only by repeated single-package calls, with no visibility into intermediate releases.
Available Tools
2 toolscheck_versionCheck a package versionBRead-onlyIdempotentInspect
Is this version real, yanked, and how far behind latest (major versions released since)?
Inputs: name (required), version (required), ecosystem (required). Returns: latest
latest_versionLatest version of a packageBRead-onlyIdempotentInspect
Current latest version of an npm or PyPI package, its date, and the deprecation message if the latest is deprecated.
Inputs: name (required), ecosystem (required). Returns: latest
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
What breaks between versions, vulnerabilities, compatible versions, EOL dates: npm, PyPI, Rust, PHP.
Package versions, licences and known vulnerabilities for npm, PyPI, crates, Go, Maven, NuGet
Check PyPI and npm upgrades: known vulnerabilities, the safe version, and what each upgrade breaks.
Check npm and PyPI packages exist before install: versions, age, downloads, look-alikes.
Related MCP Servers
- AlicenseAqualityCmaintenanceChecks npm and PyPI packages for outdated versions, deprecation status, and breaking changes with cited sources, enabling AI agents to verify dependency freshness.1ISC
- AlicenseAqualityCmaintenanceEnables AI coding agents and developers to query NPM, PyPI, and Crates.io simultaneously for current stable versions, licenses, deprecation notices, runtime requirements, core dependencies, and install commands.1MIT
- AlicenseAqualityBmaintenanceVerified, dated facts for AI coding agents: what breaks between npm package versions (diffed from TypeScript types), per-version vulnerabilities, the newest version compatible with a given Node/Python/Rust/PHP, end-of-life dates of ~480 runtimes and frameworks, and AI model prices. Covers npm, PyPI, crates.io and Packagist.121AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to fetch the real latest versions of packages from npm, PyPI, crates.io and the Go module proxy, then check manifests or whole projects for outdated dependencies and rewrite them in place. It also reports the current releases and underlying dependency stacks of AI coding tools like Claude Code, Codex and Gemini CLI.1MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.