# unripe (pypi · unripe)

Check how long ago a package version was published before an agent adds it, in 20 ecosystems.

- Trust score: 60/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- pypi · `unripe`: 60/100 (this document), [markdown](https://verifymcp.io/servers/glumly-unripe/unripe.md), [page](https://verifymcp.io/servers/glumly-unripe/unripe)

## Channel facts

- Registry: `pypi`
- Package: `unripe`
- Version: `0.10.2`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 50/100
  - Malware scan not yet available for this package.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 74/100
  - Repository check failed: the declared repository URL redirects; it must resolve directly.
  - Cryptographically verified build provenance (signed, bound to glumly/unripe).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 10 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 707 tokens (~235/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the unripe MCP server?

unripe runs locally as a PyPI package, launched with uvx unripe. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add glumly-unripe -- uvx unripe
```

### Cursor

```json
{
  "mcpServers": {
    "glumly-unripe": {
      "command": "uvx",
      "args": [
        "unripe"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "glumly-unripe": {
      "command": "uvx",
      "args": [
        "unripe"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add glumly-unripe -- uvx unripe
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "glumly-unripe": {
      "type": "local",
      "command": [
        "uvx",
        "unripe"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add glumly-unripe --command uvx --arg unripe
```

### Hermes

```yaml
mcp_servers:
  glumly-unripe:
    command: "uvx"
    args: ["unripe"]
```

### Netclaw

```json
{
  "McpServers": {
    "glumly-unripe": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "unripe"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add glumly-unripe -t stdio -c uvx -a unripe
```

### Other

```json
{
  "mcpServers": {
    "glumly-unripe": {
      "command": "uvx",
      "args": [
        "unripe"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 60, −15)

- [security regression] Malware scan: pass → unverified

### 2026-11-03 (score 75, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-31 (score 60, −15)

- [security regression] Malware scan: pass → unverified

### 2026-10-30 (score 75, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-28 (score 60, −5)

- [security regression] Source repository: pass → fail

### 2026-10-25 (score 65)

First indexed and scored.

## MCP tools (3)

### `check_package` (~276 tokens)

Check a package version's age

Say when a package version was published and whether it is old enough under the project's minimum age. Leave version out to list recent releases and get the newest version that is old enough: use that version when adding or upgrading a dependency. A version that is too new comes with the newest older version that passes.

Input parameters:

- `ecosystem` (string, required): The registry: npm (also pnpm, yarn, bun), pypi, cargo, go, composer, rubygems, nuget, maven (group:artifact), jsr, pub (Dart and Flutter), cocoapods, swift (owner/repo on GitHub), terraform (namespac…
- `min_age` (string): Override the minimum age, like 72h, 3d or 1w. Leave out to use the project's policy.
- `name` (string, required): The package name, exactly as the registry knows it, like left-pad, @types/node or requests.
- `version` (string): The exact version. Leave out to list recent releases.

### `check_lockfiles` (~221 tokens)

Check lockfiles for versions that are too new

Check every lockfile under a directory (package-lock.json, pnpm-lock.yaml, yarn.lock, bun.lock, deno.lock, uv.lock, poetry.lock, requirements.txt, Cargo.lock, go.mod, composer.lock, Gemfile.lock, packages.lock.json, gradle.lockfile, pubspec.lock, Podfile.lock, Package.resolved, .terraform.lock.hcl, conan.lock, renv.lock, mix.lock, flake.lock, MODULE.bazel.lock, vcpkg.json and more) and report every locked version that is younger than the minimum age or whose age is unknown. Set since to a git ref, like origin/main, to check only what changed since then.

Input parameters:

- `min_age` (string): Override the minimum age, like 72h, 3d or 1w. Leave out to use the project's policy.
- `path` (string): A directory or lockfile. Defaults to the current directory.
- `since` (string): Only check versions added since this git ref, like origin/main or HEAD.

### `cooldown_settings` (~89 tokens)

Show cooldown settings

Show the unripe policy for a directory, the minimum release age settings its package managers and update bots already have (npm, pnpm, yarn, bun, uv, Poetry, Deno, Cargo, Bundler, Dependabot, Renovate), where they disagree, and the lines that would add the missing ones.

Input parameters:

- `path` (string): The project directory. Defaults to the current directory.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/glumly-unripe/unripe#diagnostics

## Score history

- 2026-11-05: 60
- 2026-11-04: 75
- 2026-11-03: 75
- 2026-11-02: 60
- 2026-11-01: 60
- 2026-10-31: 60
- 2026-10-30: 75
- 2026-10-29: 60
- 2026-10-28: 60
- 2026-10-27: 65
- 2026-10-26: 65
- 2026-10-25: 65

## Common questions

### What is the unripe MCP server?

unripe is an MCP server listed in the public MCP registry as io.github.glumly/unripe. Check how long ago a package version was published before an agent adds it, in 20 ecosystems. This page covers its PyPI package (unripe).

### Is the unripe MCP server safe to use?

unripe scores 60 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the unripe MCP server expose?

unripe exposes 3 tools: check_package, check_lockfiles, cooldown_settings. Their descriptions and schemas cost roughly 586 tokens of context every time the server is loaded.

### Is the unripe MCP server still maintained?

unripe is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the unripe MCP server under?

unripe declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- PyPI project: https://pypi.org/project/unripe/
- Socket report: https://socket.dev/pypi/package/unripe
- Changelog RSS feed: https://verifymcp.io/servers/glumly-unripe/unripe.xml
- Changelog JSON feed: https://verifymcp.io/servers/glumly-unripe/unripe.json
- HTML version of this page: https://verifymcp.io/servers/glumly-unripe/unripe