Abandonment checks for WordPress, npm and PyPI packages, priced per call.
Scored across 2 tools
package_check performs the core abandonment assessment while package_sources exposes registry endpoints and scoring rules. The two tools have clearly distinct purposes with no overlap, so an agent can easily select the right one.
Both tools follow the same consistent snake_case package_<noun> pattern (package_check, package_sources). The convention is predictable and readable.
With only two tools, the surface is on the thin side even for a narrow micro-service. The set is focused and each tool earns its place, but it sits at the borderline of minimal scope.
The core lifecycle (assess a package, inspect sources/scoring rules) is covered for the stated purpose. Minor gaps exist, such as no batch checking of multiple packages at once, but agents can work around this with repeated calls.
Check whether a WordPress.org plugin, npm package or PyPI project is abandoned. Costs $0.02 per call via x402. Returns status (active, stale, abandoned, deprecated or closed), a 0-100 abandonment-risk score, months since the last update, the latest release, and the signals behind the score. Signals, not a verdict: check the project before deciding.
Inputs: name (required), ecosystem (required).
List the registry endpoints this service reads, the scoring rules and the cache policy. Free.
Inputs: no named parameters.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Pay-per-call x402 npm and PyPI package metadata, versions, search, download counts.
Verify claims, monitor pages, catch changes & scan deps for CVEs. 200 free calls/hr, $0.01/call.
Check an npm or Python package, or a package.json, for vulnerabilities and upkeep.
Package intelligence for AI agents across npm, PyPI, crates.io and deps.dev. No API keys.
Add one secure layer between your agents and this server.