io.github.jmshinhwa/pyproject-release-gate
NPM · @READYSTACK/PYPROJECT-RELEASE-GATE
19 date-aware checks on the [project] metadata that decides whether your next release uploads
Available components
Last scanned (21 hours ago)
Scores higher than 51% of npm servers
Category CI/CD and DevOps
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency26
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Licence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.Unverified
- Maintenance check failed: the publisher has marked this version as deprecated on the registry, telling users to stop installing it. See how to fix → Fail
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability57
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 157 tokens (~52/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 60% of tool parameters carry a description.Partial
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 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- License in Provenance & TransparencyLicence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 20 Nov 26 +1
- Stability: 0.97 → pass security
- 18 Nov 26 −1
- Stability: pass → 0.93 functional
- 12 Nov 26 +1
- Stability: 0.97 → pass security
- 11 Nov 26 −1
- Stability: pass → 0.97 functional
- 5 Nov 26 +1
- Stability: 0.97 → pass security
- 3 Nov 26 −1
- Stability: pass → 0.93 functional
- 28 Oct 26 +1
- Stability: 0.97 → pass security
- 27 Oct 26 −1
- Stability: pass → 0.97 functional
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 21 Nov 2026 · Analysed npm/@readystack/pyproject-release-gate@1.0.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
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_dir ~65
pyproject.toml Release Gate (PEP 639) - sweep a folder and return every finding (licence; the full run is free for 7 days)
| Name | Type | Req | Description |
|---|---|---|---|
| dir | string | yes | – |
| ext | string | – | optional extension filter, e.g. .html |
No output schema declared.
No examples provided.
check_file ~39
pyproject.toml Release Gate (PEP 639) - run all checks on one file by path (free)
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | – |
No output schema declared.
No examples provided.
check_text ~53
pyproject.toml Release Gate (PEP 639) - run all 19 checks on a text (free)
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | optional file name for context |
| text | string | yes | file contents |
No output schema declared.
No examples provided.
How do I install the io.github.jmshinhwa/pyproject-release-gate MCP server?
io.github.jmshinhwa/pyproject-release-gate runs locally as an npm package, launched with npx -y @readystack/pyproject-release-gate --mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
npm · @readystack/pyproject-release-gate
claude mcp add jmshinhwa-pyproject-release-gate -- npx -y @readystack/pyproject-release-gate --mcp
What is the io.github.jmshinhwa/pyproject-release-gate MCP server?
io.github.jmshinhwa/pyproject-release-gate is an MCP server listed in the public MCP registry as io.github.jmshinhwa/pyproject-release-gate. 19 date-aware checks on the [project] metadata that decides whether your next release uploads. This page covers its npm package (@readystack/pyproject-release-gate).
Is the io.github.jmshinhwa/pyproject-release-gate MCP server safe to use?
io.github.jmshinhwa/pyproject-release-gate scores 75 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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 io.github.jmshinhwa/pyproject-release-gate MCP server expose?
io.github.jmshinhwa/pyproject-release-gate exposes 3 tools: check_text, check_file, check_dir. Their descriptions and schemas cost roughly 157 tokens of context every time the server is loaded.
Is the io.github.jmshinhwa/pyproject-release-gate MCP server still maintained?
io.github.jmshinhwa/pyproject-release-gate is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the io.github.jmshinhwa/pyproject-release-gate MCP server?
VerifyMCP ran 15 checks on io.github.jmshinhwa/pyproject-release-gate, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.jmshinhwa/pyproject-release-gate: License. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.