unripe
PYPI · UNRIPE
Check how long ago a package version was published before an agent adds it, in 20 ecosystems.
Available components
Last scanned (6 hours ago)
Scores higher than 57% of PyPI servers
Category Developer Tools
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. How we score → Why this is hard to score →
Supply Chain Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency74
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Cryptographically verified build provenance (signed, bound to glumly/unripe). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 10 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 30 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 28 Oct 26 −5
- Source repository: pass → fail ▼ security
- 25 Oct 26 65
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed pypi/unripe@0.10.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | glumly/unripe |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/glumly/unripe/.github/workflows/release.yml@refs/tags/v0.10.2 |
| Rekor log index | 3463050394 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:3f4fbda5fa562aba13d29a3820ea91d1609bf7df59ed406dd2b4c9759d4b07f4 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_lockfiles Check lockfiles for versions that are too new ~221
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
check_package Check a package version's age ~276
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | yes | 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 | yes | 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. |
No output schema declared.
No examples provided.
cooldown_settings Show cooldown settings ~89
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.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | The project directory. Defaults to the current directory. |
No output schema declared.
No examples provided.
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.
pypi · unripe
claude mcp add glumly-unripe -- uvx unripe
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.