release-gate-mcp
NPM · RELEASE-GATE-MCP · SCANNED SEP 20
Release intelligence for AI agents. Detects breaking changes and recommends semver.
Available components
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 Security98
- 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
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 270 tokens (~90/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 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 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 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.
How do I install the release-gate-mcp server?
release-gate-mcp runs locally as an npm package, launched with npx -y release-gate-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · release-gate-mcp
claude mcp add abduljabbarbxr-release-gate-mcp -- npx -y release-gate-mcp
{
"mcpServers": {
"abduljabbarbxr-release-gate-mcp": {
"command": "npx",
"args": [
"-y",
"release-gate-mcp"
]
}
}
} {
"servers": {
"abduljabbarbxr-release-gate-mcp": {
"command": "npx",
"args": [
"-y",
"release-gate-mcp"
]
}
}
} codex mcp add abduljabbarbxr-release-gate-mcp -- npx -y release-gate-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"abduljabbarbxr-release-gate-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"release-gate-mcp"
],
"enabled": true
}
}
} openclaw mcp add abduljabbarbxr-release-gate-mcp --command npx --arg -y --arg release-gate-mcp
mcp_servers:
abduljabbarbxr-release-gate-mcp:
command: "npx"
args: ["-y", "release-gate-mcp"] {
"McpServers": {
"abduljabbarbxr-release-gate-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"release-gate-mcp"
]
}
}
} assistant mcp add abduljabbarbxr-release-gate-mcp -t stdio -c npx -a -y release-gate-mcp
{
"mcpServers": {
"abduljabbarbxr-release-gate-mcp": {
"command": "npx",
"args": [
"-y",
"release-gate-mcp"
]
}
}
} 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.
- 16 Sept 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 20 Sept 2026 · Analysed npm/release-gate-mcp@0.1.3
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 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| 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 →
release.analyze ~99
Analyze the changes in a repository since a reference. Classifies commits, detects breaking changes from messages and removed exports, and recommends the next semver bump.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Start ref, for example a tag or commit. Defaults to the last tag, or the first commit if no tags exist. |
| path | string | – | Repository root. Defaults to the current directory. |
| to | string | – | End ref. Defaults to HEAD. |
No output schema declared.
No examples provided.
release.bump ~92
Recommend the next semantic version for the repository given its current version and the analyzed changes.
| Name | Type | Req | Description |
|---|---|---|---|
| bump | string | – | Override the bump type instead of detecting it |
| from | string | – | Start ref. Defaults to the last tag, or the first commit if no tags exist. |
| path | string | – | Repository root. Defaults to the current directory. |
| to | string | – | End ref. Defaults to HEAD. |
No output schema declared.
No examples provided.
release.notes ~79
Generate release notes from the commits since a reference. Groups commits by type and flags breaking changes.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Start ref. Defaults to the last tag, or the first commit if no tags exist. |
| path | string | – | Repository root. Defaults to the current directory. |
| to | string | – | End ref. Defaults to HEAD. |
No output schema declared.
No examples provided.
What is the release-gate-mcp server?
release-gate-mcp is listed in the public MCP registry as io.github.AbduljabbarBXR/release-gate-mcp. Release intelligence for AI agents. Detects breaking changes and recommends semver. This page covers its npm package (release-gate-mcp).
Is the release-gate-mcp server safe to use?
release-gate-mcp scores 65 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 release-gate-mcp server expose?
release-gate-mcp exposes 3 tools: release.analyze, release.notes, release.bump. Their descriptions and schemas cost roughly 270 tokens of context every time the server is loaded.
Is the release-gate-mcp server still maintained?
release-gate-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 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 release-gate-mcp server under?
release-gate-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.