UpgradeLens
by upgradelens.mattpicone.workers.dev in Developer tools
npm/PyPI/Django dependency upgrades: security, runtime compatibility, migration, package ranking.
https://upgradelens.mattpicone.workers.dev/mcp
Last 30 days
- Uptime
- 100%
- Response time
- 288 ms typical, 288 ms slowest 5%
- Last check
- 4 h ago
- Next check
- in 2 h
How to call it
Add it to any MCP client that supports remote servers.
{
"mcpServers": {
"upgradelens": {
"type": "http",
"url": "https://upgradelens.mattpicone.workers.dev/mcp"
}
}
}4 tools
- review_dependency_upgrade
Use when an agent reviews a Dependabot, Renovate, npm, or PyPI version change before merge. One cited result combines security delta, runtime compatibility, breaking changes, go/no-go risk, and ordered migration actions for exact current and target versions. Do not use for new in
- check_dependency_upgrade
Use when a coding agent needs a cited go/no-go risk decision without steps before changing an existing npm or PyPI dependency between two exact versions. Returns action_allowed, vulnerability delta, compatibility, EOL, and breaking-change evidence. Use plan_dependency_upgrade ins
- find_safe_upgrade_target
Use only when an existing npm or PyPI dependency has an exact current version but no chosen target. Ranks candidates; candidates are not declared safe and require check_dependency_upgrade or plan_dependency_upgrade. Do not use when a target is stated, for a new install, or as aut
- plan_dependency_upgrade
Use when a coding agent needs a migration checklist, refactor actions, ordered review actions, changelog links, or test steps for exact current and target npm/PyPI versions. Use check_dependency_upgrade instead for a go/no-go without steps. Do not use to choose a target, install
Security scan
- No findings. We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 4 h ago | Passed | 200 | 288 ms |