UpgradeLens MCP Server

by mattpicone Your server? Claim it

answering

UpgradeLens is answering right now. Last checked 16 min ago. It exposes 4 tools. Last commit 9 Sep 2026.

npm/PyPI/Django dependency upgrades: security, runtime compatibility, migration, package ranking.

Uptime history 13 days of history

13 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

122 ms

Response time

average over 24h

Stars

last commit 9 Sep 2026

What changed 25

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

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 tools changed the parameters they ask for check_dependency_upgrade, find_safe_upgrade_target, plan_dependency_upgrade

31 Aug 3 tool descriptions were rewritten check_dependency_upgrade, find_safe_upgrade_target, plan_dependency_upgrade

31 Aug a tool changed version

30 Aug a tool changed version

29 Aug 3 tool descriptions were rewritten9 times that day check_dependency_upgrade, find_safe_upgrade_target, plan_dependency_upgrade

29 Aug 3 tools changed the parameters they ask for4 times that day check_dependency_upgrade, find_safe_upgrade_target, plan_dependency_upgrade

and 8 more, back to 29 August 2026

Nothing serious here today

Today is the operative word: we check UpgradeLens every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add upgradelens --transport http https://upgradelens.mattpicone.workers.dev/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "upgradelens": {
      "url": "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

{
  "mcpServers": {
    "upgradelens": {
      "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

URL	Transport	State	Latency	Checked
https://upgradelens.mattpicone.workers.dev/mcp	streamable-http	answering	148 ms	16 min ago

Alternatives to UpgradeLens

same job, measured the same way

npm MCP

by alisaitteke

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

24 installs/wk local only

Npmjs MCP

by yawlabs

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

123 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

Depwire

by atef-ataya

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

521 installs/wk local only

Dependency Vulnerability Tracker — package security advisories ($0.01/query)

by a2awire

Dependency vulns & malicious-package advisories. Register in-session — free testnet funds.

16 tools answering

SkillTotal

by skilltotal

Deterministic security scan of MCP servers, agent skills and npm/PyPI packages. Runs locally.

1 164 installs/wk local only

Correctover

by correctover

MCP runtime security. 22µs validation, 97% self-healing. Detects RCE, SSRF, credential hijacking.

local only

Node Runtime

by mcp-protocol

This package is intended for demonstration only. Maintained by JFrog Security.

23 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 92 of 92 checks got a reply (100.0%), average response time 122 ms. The bar chart above shows every period we have measured.

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 with the file path 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 122 ms on average, which is faster than 81% 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.

Is UpgradeLens open source?

Yes — it is published under the MIT licence, written in TypeScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.