
Ripedeps MCP server
Which MCP servers are Ripedeps's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-29
- Registry namecom.ripedeps/ripedepsverified in the MCP registry
The registry name sits under ripedeps.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-29
- Tools1
- Server calls itselfripedeps
- Server version1.4.9
- Protocol version2025-06-18
On 2026-10-29 the server answered initialize and tools/list without a sign-in. First answer in 645 ms.
- Whether its tools do the product's job has not been judged yet.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP score100 of 100answers 100 · definitions 100 · context 100 · connects 100
- Answered100% of days7 of 7 daily checks
- Median first answer664 ms
- Space in an agent's context≈ 638 tokensthe definitions of all its tools (1), which an agent carries on every turn
- Tool definitionsA · 100 of 100
- Typed results1 of 1 toolsdeclared outputSchema: results come typed, read once
- Every tool passes all six checks.
What an agent can do with it
- not sure · Upgrade npm packages to versions old enough to trust
- not sure · Hold back brand-new npm releases for a set number of days
- not sure · Review a diff and reasons before applying dependency upgrades
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
plan_upgradeRecommends 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…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"ripedeps": {
"type": "http",
"url": "https://mcp.ripedeps.com/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http ripedeps https://mcp.ripedeps.com/mcpclaude.ai, ChatGPT and other clients: add https://mcp.ripedeps.com/mcp as a custom connector in the settings.
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.