Package maintenance status
Server Details
Is a package still maintained, deprecated or archived? npm, PyPI, Cargo, Go, Maven, NuGet, RubyGems.
- 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
Both tools return the same status/verdict/evidence; the only real differentiator is single-package vs. batch-of-10. This overlap means an agent could plausibly pick either for a one-package check, but the descriptions ('check up to 10 packages... in one call') make the intended split clear enough.
Both names are snake_case verb_noun forms starting with 'check_package(s)', so the family is obvious. The singular tool adds a 'maintenance' qualifier while the plural one does not, a minor asymmetry that could be read as implying different functionality.
Two tools is thin in absolute terms, but the domain (package maintenance lookup) is narrow and the batch tool absorbs the bulk-use case. Nothing feels gratuitous or missing at the tool-count level.
Single and batch lookup across seven ecosystems with rich evidence (last release, deprecation flag, archive status, Scorecard) covers the stated purpose well. Minor gaps: no way to force a cache refresh, and no explicit version-range or replacement-package lookup beyond whatever the deprecation message happens to name.
Available Tools
2 toolscheck_package_maintenanceCheck if a package is still maintainedARead-onlyIdempotentInspect
Is an open-source package still maintained, or is it deprecated, archived or abandoned? Use before adding, upgrading or auditing a dependency. Returns a status (active, slowing, stale, deprecated, archived, inactive, unknown, not_found), a one-sentence verdict, and the evidence: last release date and version, releases in the last 12 months, the registry deprecation flag and message (often names the replacement), the source repository, whether it is archived on GitHub and its last push, and the OpenSSF Scorecard "Maintained" score. Ecosystems: pypi, npm, cargo, go, maven (group:artifact), nuget, rubygems. Live data from deps.dev, PyPI and GitHub, cached 24 h.
Inputs: name (required), ecosystem (required).
check_packagesCheck a list of dependenciesARead-onlyIdempotentInspect
Check up to 10 packages from one ecosystem in one call, e.g. a project's dependency list, and get the same status, verdict and evidence for each. Flags deprecated, archived and stale dependencies.
Inputs: names (required), ecosystem (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Package versions, licences and known vulnerabilities for npm, PyPI, crates, Go, Maven, NuGet
Package alive? Verdict with evidence: deprecated, archived, stale or active; plus runtime EOL dates.
What breaks between versions, vulnerabilities, compatible versions, EOL dates: npm, PyPI, Rust, PHP.
Supply chain risk scoring for npm, PyPI, Cargo, and Go. 9 tools. Behavioral signals.
Related MCP Servers
- 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
- AlicenseAqualityDmaintenanceChecks whether software dependencies (npm packages, GitHub Actions, MCP servers, Docker images) are alive, dormant, abandoned, archived, or deleted using dated observations from lastseen.dev.4MIT
- AlicenseAqualityDmaintenancePackage intelligence for AI coding agents that checks npm and PyPI package health, deprecation, vulnerabilities, bundle size, and compares alternatives.5MIT
- AlicenseNot gradedqualityBmaintenanceEnables safety-ranked discovery of open-source components across npm, PyPI, crates.io, RubyGems, GitHub, and Hugging Face, with license, security, and health checks.1,348 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.