Dependency Freshness Mcp
Query npm and PyPI for latest versions, deprecations, and dated breaking-change diffs so your agent upgrades dependencies with context.
Overview
dependency-freshness-mcp is a MCP server for the Build phase that reports npm and PyPI version freshness, deprecations, and dated breaking-change diffs for AI agents.
What is this MCP server?
- npm and PyPI freshness checks designed for AI agent consumption
- Surfaces latest published versions and deprecation signals
- Provides dated breaking-change diffs to plan safer upgrades
- Hosted streamable-http remote on Apify at version 0.0.2
- Complements local MCP skills without replacing your lockfile or CI
- Server version 0.0.2
- Remote MCP type streamable-http on Apify actor dependency-freshness-mcp
- Covers npm and PyPI registries
What problem does it solve?
Agents guess at package versions and miss deprecations, leading to broken upgrades and stale dependency stacks.
Who is it for?
Indie devs maintaining Node or Python apps who want MCP-backed dependency intelligence inside the coding agent.
Skip if: Repos with no npm or PyPI footprint or teams that only manage deps exclusively through locked enterprise mirroring.
What do I get? / Deliverables
Your agent pulls registry-accurate freshness and breaking-change timelines before it edits lockfiles or migration notes.
- Latest version and freshness snapshot for requested packages
- Deprecation notices when registries expose them
- Dated breaking-change diff context for upgrade planning
Recommended MCP Servers
Journey fit
Integrations is the canonical shelf because freshness checks happen while wiring packages and SDKs into the product codebase. Integrations covers npm and PyPI package decisions agents make when adding or bumping libraries during implementation.
How it compares
Registry freshness MCP over HTTP, not a local Renovate bot or monorepo build orchestrator.
Common Questions / FAQ
Who is dependency-freshness-mcp for?
dependency-freshness-mcp is for solo builders on npm or PyPI stacks who want their agent to check versions and breaking changes via MCP.
When should I use dependency-freshness-mcp?
Use it during integrations work, pre-release security passes, or operate iterations whenever you bump or audit JavaScript and Python dependencies.
How do I add dependency-freshness-mcp to my agent?
Register the Apify streamable-http remote URL from the server manifest in your MCP client, then invoke freshness tools for npm and PyPI package names.