概要
What is Dependency Freshness Checker?
Dependency Freshness Checker is an MCP server that tells AI coding agents whether an npm or PyPI package is outdated. It returns the latest version, release dates, deprecation status, how many versions behind you are, and a dated breaking-change diff. It reads only public registry APIs and GitHub releases, uses Pay-Per-Event pricing, and is designed for pay-as-you-go agent use.
How to use Dependency Freshness Checker?
Pass a list of packages with ecosystem, name, and optional currentVersion to the MCP tool check_dependency_freshness(packages). Three ways to reach it: via Apify's hosted MCP server at https://mcp.apify.com, as its own MCP server at the Actor's /mcp endpoint, or locally via stdio with a compiled entrypoint.
Key features of Dependency Freshness Checker
- Citations-first output with source URLs and access dates
- Supports both npm and PyPI ecosystems
- Detects deprecation status for any package or assumed version
- Counts how many versions behind your agent is
- Generates a dated "what changed since your version" change summary
- Pay-Per-Event pricing at $0.005 per package checked
Use cases of Dependency Freshness Checker
- AI coding agents checking dependency freshness before generating code
- Automated dependency audit during CI/CD pipelines
- Batch checking multiple npm/PyPI packages for maintenance reports
FAQ from Dependency Freshness Checker
Does it scrape websites?
No. It reads only public registry APIs and GitHub releases — no scraping, no terms-of-service risk.
Which ecosystems are supported?
npm and PyPI today.
Do I need a GitHub token?
No — it is optional and only raises the GitHub rate limit for heavier batches.
Can an agent call it directly?
Yes — that is the point. Use the check_dependency_freshness MCP tool via hosted or self-hosted MCP endpoint.
