Ripedeps

com.ripedeps/ripedepsVersion 1.4.9

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

Status

Responds90 msNov 14, 2026, 14:13 UTCAnswered our handshake without sign-in.

Registry data may be out of date

We could not refresh it, so this page shows the last copy.

Last checked: Nov 14, 2026, 14:13 UTC
Latency: 90 ms
Remotes responding: 1 of 1
Sign-in: No sign-in
Hosting: EU hosting detected (detected, not a legal statement)
Registry data as of: Nov 14, 2026, 21:12 UTC

Data from the official MCP Registry, checked by run.zero. How we check

Connect

Streamable HTTP

https://mcp.ripedeps.com/mcpResponds90 msNov 14, 2026, 14:13 UTC

No sign-in

Claude Code

claude mcp add --transport http ripedeps https://mcp.ripedeps.com/mcp

Claude Desktop and claude.ai

1
2
3

Settings > Connectors > Add custom connector
Name: ripedeps
Remote MCP server URL: https://mcp.ripedeps.com/mcp

Cursor

{
  "mcpServers": {
    "ripedeps": {
      "url": "https://mcp.ripedeps.com/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"ripedeps","type":"http","url":"https://mcp.ripedeps.com/mcp"}'

Built your own server? run.zero hosts MCP servers on European infrastructure.

Host your own MCP server on run.zero

Tools

1 tools

Tools of Ripedeps
	Description		Read-only	Idempotent	Open world
`plan_upgrade`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.	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.	Not declared	Yes	Not declared	Yes

Details

Registry status: Active
Published: Oct 26, 2026
Updated: Oct 26, 2026
Website: https://ripedeps.com/mcp⁠ (opens in a new tab)
Repository: Not given
Categories (suggested): Developer toolsSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
GDPR: Not declared

Are you the operator? Claim this listing