mcpbeat Sign in

UpgradeLens MCP Server

by mattpicone Your server? Claim it
answering

UpgradeLens is answering right now. Last checked 8 min ago. It exposes 4 tools.

npm/PyPI package dependency upgrade reviews: security, runtime compatibility, cited migration.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 73 days of history · worst day 93%
73 days agonow
100.0%
Uptime 24h
91 of 91 checks
4
Tools
read from the server
127 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 31

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 29 August 2026. No other catalogue keeps this.

14 Oct a tool changed version
12 Oct a tool changed version2 times that day
1 Oct a tool changed version
16 Sep a tool changed version
11 Sep a tool changed version
9 Sep a tool changed version
6 Sep a tool changed version2 times that day
6 Sep a tool appeared review_dependency_upgrade
31 Aug 3 tool descriptions were rewritten check_dependency_upgrade, find_safe_upgrade_target, plan_dependency_upgrade
31 Aug 3 tools changed the parameters they ask for check_dependency_upgrade, find_safe_upgrade_target, plan_dependency_upgrade
and 17 more, back to 29 August 2026

This one has been quiet for a while

Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

run in your terminal
claude mcp add upgradelens --transport http https://upgradelens.mattpicone.workers.dev/mcp
Settings → Connectors → Add custom connector, then paste this address
https://upgradelens.mattpicone.workers.dev/mcp
~/.codex/config.toml
[mcp_servers.upgradelens]
url = "https://upgradelens.mattpicone.workers.dev/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "upgradelens": {
      "url": "https://upgradelens.mattpicone.workers.dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "upgradelens": {
      "type": "http",
      "url": "https://upgradelens.mattpicone.workers.dev/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

dependency
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 instead for ordered migration work. Do not use to choose a target, install a new package, search general docs, or analyze another ecosystem. Read-only and safe to retry.
plan
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 a package, or provide a general tutorial. Read-only and safe to retry.
review
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 installs, unknown versions, general documentation, or other ecosystems. Read-only and safe to retry.
safe
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 authorization to edit files. Read-only and safe to retry.

Endpoints

URLTransportStateLatencyChecked
https://upgradelens.mattpicone.workers.dev/mcp streamable-http answering 85 ms 8 min ago

Alternatives to UpgradeLens

same job, measured the same way
npm Registry MCP Server
by yawlabs

npm registry MCP server — package intelligence, security audits, dependency analysis

217 installs/wk local only
npm MCP
by alisaitteke

MCP server for npm package management, security analysis, and compatibility checking

56 installs/wk local only
MCP Magento Audit
by michalper

MCP server for auditing Magento projects: update compatibility, module quality, dependency security

268 installs/wk local only
Nekzus npm Sentinel MCP
by smithery

Provide AI-powered real-time analysis and intelligence on NPM packages, including security, depend…

answering
Vulnrable
by vulnrable

Security grades for MCP servers and npm/PyPI packages, ranked by CISA KEV and EPSS.

answering
OSV Dependency Vulnerability Check
by fairquery

Check npm, PyPI, Go and Maven packages or lockfiles against OSV.dev: CVEs, CVSS, fixed versions.

answering
Dependency Vulnerability Check (OSV)
by brunckel

Known vulnerabilities and fixed versions for npm, PyPI, Go, Maven packages from OSV.dev via Apify.

answering
Depwire
by atef-ataya

Dependency graph + 24 MCP tools. Impact analysis, simulation, security, agent coordination

639 installs/wk local only

UpgradeLens — questions

Answers built from our own checks of this server.

What can UpgradeLens do?
It exposes 4 tools, read directly from the server on our last check. Among them: check_dependency_upgrade, find_safe_upgrade_target, plan_dependency_upgrade, review_dependency_upgrade. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is UpgradeLens working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 127 ms. The bar chart above shows every period we have measured.
Is UpgradeLens still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect UpgradeLens?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does UpgradeLens need an API key?
No. UpgradeLens completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is UpgradeLens?
It answers our handshake in 127 ms on average, which is faster than 87% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.