# Release Intel (npm · @barissozudogru/release-intel-mcp)

Correlates commits, PRs, issues and contributors between two git refs for release notes.

- Trust score: 85/100 (high trust)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- npm · `@barissozudogru/release-intel-mcp`: 85/100 (this document), [markdown](https://verifymcp.io/servers/barissozudogru-release-intel/barissozudogru-release-intel-mcp.md), [page](https://verifymcp.io/servers/barissozudogru-release-intel/barissozudogru-release-intel-mcp)

## Channel facts

- Registry: `npm`
- Package: `@barissozudogru/release-intel-mcp`
- Version: `0.7.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-09-21.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 95 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 25 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 86/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 339 tokens (~113/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 90/100
  - Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add barissozudogru-release-intel -- npx -y @barissozudogru/release-intel-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "barissozudogru-release-intel": {
      "command": "npx",
      "args": [
        "-y",
        "@barissozudogru/release-intel-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "barissozudogru-release-intel": {
      "command": "npx",
      "args": [
        "-y",
        "@barissozudogru/release-intel-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add barissozudogru-release-intel -- npx -y @barissozudogru/release-intel-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "barissozudogru-release-intel": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@barissozudogru/release-intel-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add barissozudogru-release-intel --command npx --arg -y --arg @barissozudogru/release-intel-mcp
```

### Hermes

```yaml
mcp_servers:
  barissozudogru-release-intel:
    command: "npx"
    args: ["-y", "@barissozudogru/release-intel-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "barissozudogru-release-intel": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@barissozudogru/release-intel-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add barissozudogru-release-intel -t stdio -c npx -a -y @barissozudogru/release-intel-mcp
```

### Other

```json
{
  "mcpServers": {
    "barissozudogru-release-intel": {
      "command": "npx",
      "args": [
        "-y",
        "@barissozudogru/release-intel-mcp"
      ]
    }
  }
}
```

## 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-09-20 (score 85, −1)

- [functional] Stability: pass → 0.87

### 2026-09-19 (score 86, 0)

- [security] Stability: 0.97 → pass

### 2026-09-17 (score 86, +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.

### 2026-09-15 (score 85, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-07 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (3)

### `get_changes_between_refs` (~105 tokens)

Get Changes Between Refs

Get all commits between two git refs enriched with associated PR metadata, author information, and linked issues. Uses the GitHub compare API.

Input parameters:

- `base` (string, required): Base ref (tag, branch, or commit SHA), the older point
- `head` (string, required): Head ref (tag, branch, or commit SHA), the newer point
- `owner` (string, required): GitHub repository owner (user or organization)
- `repo` (string, required): GitHub repository name

### `get_pull_requests_in_range` (~125 tokens)

Get Pull Requests in Range

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.

Input parameters:

- `base` (string, required): Base ref (tag, branch, or commit SHA), the older point
- `head` (string, required): Head ref (tag, branch, or commit SHA), the newer point
- `owner` (string, required): GitHub repository owner (user or organization)
- `repo` (string, required): GitHub repository name

### `get_release_summary` (~109 tokens)

Get Release Summary

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.

Input parameters:

- `from_tag` (string, required): The previous release tag (base / older ref)
- `owner` (string, required): GitHub repository owner (user or organization)
- `repo` (string, required): GitHub repository name
- `to_tag` (string, required): The new release tag or HEAD (head / newer ref)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/barissozudogru-release-intel/barissozudogru-release-intel-mcp#diagnostics

## Score history

- 2026-09-21: 85
- 2026-09-20: 85
- 2026-09-19: 86
- 2026-09-18: 86
- 2026-09-17: 86
- 2026-09-16: 85
- 2026-09-15: 85
- 2026-09-14: 84
- 2026-09-13: 84
- 2026-09-12: 83
- 2026-09-11: 83
- 2026-09-10: 82
- 2026-09-09: 82
- 2026-09-08: 81
- 2026-09-07: 81
- 2026-09-06: 80
- 2026-09-05: 80
- 2026-09-04: 79
- 2026-09-03: 79
- 2026-09-02: 79
- 2026-09-01: 78
- 2026-08-31: 78
- 2026-08-30: 77
- 2026-08-29: 77
- 2026-08-28: 76
- 2026-08-27: 76
- 2026-08-26: 75
- 2026-08-25: 60
- 2026-08-24: 71
- 2026-08-23: 71

## Common questions

### 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 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 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 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 21 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 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.

## Links

- npm package: https://www.npmjs.com/package/@barissozudogru/release-intel-mcp
- Socket report: https://socket.dev/npm/package/@barissozudogru/release-intel-mcp
- Repository: https://github.com/barissozudogru/release-intel-mcp
- Website: https://petri-labs.org/tools/release-intel-mcp/
- Changelog RSS feed: https://verifymcp.io/servers/barissozudogru-release-intel/barissozudogru-release-intel-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/barissozudogru-release-intel/barissozudogru-release-intel-mcp.json
- HTML version of this page: https://verifymcp.io/servers/barissozudogru-release-intel/barissozudogru-release-intel-mcp