Release Intel
NPM · @BARISSOZUDOGRU/RELEASE-INTEL-MCP
Correlates commits, PRs, issues and contributors between two git refs for release notes.
Available components
Last scanned (9 hours ago)
Scores higher than 90% of npm servers
Category Version Control
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
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- 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
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 70 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability86
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 339 tokens (~113/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 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
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.
- 31 Oct 26 0
- Stability: 0.97 → pass security
- 30 Oct 26 0
- Stability: pass → 0.97 functional
- 24 Oct 26 0
- Stability: 0.97 → pass security
- 22 Oct 26 0
- Stability: pass → 0.93 functional
- 18 Oct 26 +7
- Known CVEs: unverified → pass ▲ security
- 17 Oct 26 −7
- Known CVEs: pass → unverified ▼ security
- 16 Oct 26 0
- Stability: 0.97 → pass security
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
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 npm/@barissozudogru/release-intel-mcp@0.7.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 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| 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 →
get_changes_between_refs Get Changes Between Refs ~105
Get all commits between two git refs enriched with associated PR metadata, author information, and linked issues. Uses the GitHub compare API.
| Name | Type | Req | Description |
|---|---|---|---|
| base | string | yes | Base ref (tag, branch, or commit SHA), the older point |
| head | string | yes | Head ref (tag, branch, or commit SHA), the newer point |
| owner | string | yes | GitHub repository owner (user or organization) |
| repo | string | yes | GitHub repository name |
No output schema declared.
No examples provided.
get_pull_requests_in_range Get Pull Requests in Range ~125
Get all merged pull requests between two refs with full metadata including labels, linked issues, review counts, and files changed. PRs are categorized by label into: breaking, feature, fix, docs, chore, dependencies, other.
| Name | Type | Req | Description |
|---|---|---|---|
| base | string | yes | Base ref (tag, branch, or commit SHA), the older point |
| head | string | yes | Head ref (tag, branch, or commit SHA), the newer point |
| owner | string | yes | GitHub repository owner (user or organization) |
| repo | string | yes | GitHub repository name |
No output schema declared.
No examples provided.
get_release_summary Get Release Summary ~109
Generate a structured release context object ready for AI synthesis into release notes. Combines commit data, PR metadata, linked issues, contributor list, and aggregate statistics for the range between two tags.
| Name | Type | Req | Description |
|---|---|---|---|
| from_tag | string | yes | The previous release tag (base / older ref) |
| owner | string | yes | GitHub repository owner (user or organization) |
| repo | string | yes | GitHub repository name |
| to_tag | string | yes | The new release tag or HEAD (head / newer ref) |
No output schema declared.
No examples provided.
How do I install the Release Intel MCP server?
Release Intel runs locally as an npm package, launched with npx -y @barissozudogru/release-intel-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 · @barissozudogru/release-intel-mcp
claude mcp add barissozudogru-release-intel -- npx -y @barissozudogru/release-intel-mcp
What is the Release Intel MCP server?
Release Intel is an MCP server listed in the public MCP registry as io.github.barissozudogru/release-intel. Correlates commits, PRs, issues and contributors between two git refs for release notes. This page covers its npm package (@barissozudogru/release-intel-mcp).
Is the Release Intel MCP server safe to use?
Release Intel scores 86 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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 Release Intel MCP server expose?
Release Intel exposes 3 tools: get_changes_between_refs, get_pull_requests_in_range, get_release_summary. Their descriptions and schemas cost roughly 339 tokens of context every time the server is loaded.
Is the Release Intel MCP server still maintained?
Release Intel 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 Release Intel MCP server under?
Release Intel declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.