Skip to main content
Glama

Server Details

Deterministic package.json upgrade plans: age gate, aligned peers, reasons per change. No AI.

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A4.5/5.0

Scored across 1 tool

Disambiguation5/5

There is only one tool, so there is nothing to confuse it with. Its purpose (produce a deterministic version-upgrade plan for a package.json) is stated unambiguously.

Naming Consistency5/5

A single snake_case verb_noun name, plan_upgrade, which clearly describes the action and object. No naming conflicts are possible with only one tool.

Tool Count2/5

One tool for the whole surface is thin: the workflow the description itself recommends (re-run with maxBump minor then major, optionally with focus) is left entirely to the agent, with no companion tools to validate a file, apply a plan, or inspect current versions. The single tool is well-scoped but the set does not earn a broader surface.

Completeness3/5

Planning is covered thoroughly (input by text or URL, diff output, per-package reasons, focus and minAgeDays controls), but the lifecycle stops at planning: no tool applies the patch, re-validates the resulting package.json, or checks a lockfile. The unified diff is workable around this, but it is a real gap for a dependency-upgrade domain.

Available Tools

1 tool
plan_upgradePlan package.json upgradesA
Read-only
Inspect

Recommends version upgrades for a package.json: the newest versions that are old enough and within the allowed step size, kept aligned with each other (peer dependencies and the first-level dependencies of the packages). Deterministic, no AI. Returns the new package.json, a unified diff (apply with patch -p1) and a per-package table with the reasons. Every package has an explanation sentence and notes lists other changes to the file (the ripedeps entry): relay them to the user as the rationale for each change.

Send the file as packageJson (text) or as packageJsonUrl (https URL of a raw file), exactly one of them.

Recommended: minAgeDays 7 (versions younger than 7 days are not proposed). The default is 0, or the ripedeps entry of the file. maxBump defaults to minor. Use focus to restrict the upgrade to some packages (and their direct neighbours).

Try more than one level: a plan only suggests and writes nothing, so calling again is cheap. Start with minor; if a package is held with a level-limit reason (a newer major exists), call again with maxBump "major" (optionally with focus) and compare. A held result is a reasoned decision for that one package, not a ban on the level: its reason names what blocks it (a peer or dependency constraint). Apply a larger step only when the user approves it.

Privacy: We do not keep your package.json: every upload is processed from scratch and discarded, nothing about its content or your IP address is remembered. Only anonymous statistics (file size, number of dependencies, number of changes) are counted.

Inputs: focus, maxBump, minAgeDays, packageJson, +2 more. Returns: diff, meta, notes, packages, +2 more

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables AI coding agents to ground dependency setup, compatibility checks, and major-version migration advice in a project's real runtime, lockfiles, and config files. It parses local project state and npm registry metadata deterministically, then returns tag-pinned install commands, breaking changes, and upgrade steps rather than generic documentation.
      5
      53 npm
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables AI coding agents to learn, from locally read lockfiles, what changes between the dependency version installed and a target version, which of the user's files that upgrade touches, and which vulnerabilities it resolves. It also performs OSV-matched vulnerability scans, ranks upgrade plans, and stores decision memory, running entirely on the user's machine with no account or API keys.
      11
      528 npm
      Apache 2.0
    • A
      license
      B
      quality
      D
      maintenance
      Enables AI agents to safely upgrade JavaScript and TypeScript projects through dependency analysis, upgrade path detection, breaking change identification, codemod application, and PR summary generation.
      14
      15 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to verify, compare, and safely upgrade npm packages by scoring packages from public signals and sandboxed co-installation, detecting breaking API surface changes, and rewriting code that upgrades break.
      63 npm
      8
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources