MCP.Market

Release Intel MCP server

by barissozudogru·io.github.barissozudogru/release-intel·v0.7.2·2 stars
No reviews yet

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

B83/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B83/100

full report

Adoption
Growing

2 stars79 downloads/wk

Reviews

Write one

Nobody has reviewed Release Intel yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Release Intel tools (3)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

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

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

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

Public scan report

scanner v0.1.10 · 2026-10-31 · same rubric, same numbers if you re-run it

no findings
  • Code scan7 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 1 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 83/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Release Intel compares

Against every graded Developer tools MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
83/100
higher than 65% of 1,119 Developer tools servers
Tools
3
the typical Developer tools server has 7
Tools that change things
0%
typical: 5%. Fewer write tools means less an agent can break
GitHub stars
2
more than 65% of 856 Developer tools servers
Downloads a week
79
more than 51% of 442 Developer tools servers with a package

What its tools let an agent do: 3 read

Install Release Intel in Claude Code, Cursor or VS Code

Runs npx -y @barissozudogru/release-intel-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add release-intel -- npx -y @barissozudogru/release-intel-mcp
Add to Cursor

What the publisher says

From the Release Intel repository's README, as published. We do not edit it. Read it on GitHub

release-intel-mcp

Build release context from repository evidence instead of a blank prompt. The server compares two Git refs and correlates commits, merged pull requests, linked issues, labels, changed files, and contributors into a structured release record.

Tool page · npm · Listed in the official MCP Registry

Start in one minute

Create a fine-grained GitHub token with read-only access to the repositories you want to inspect. Repository contents and pull requests are sufficient for the current tools. No write permission is needed.

{
  "mcpServers": {
    "release-intel": {
      "command": "npx",
      "args": ["-y", "@barissozudogru/release-intel-mcp"],
      "env": {
        "GITHUB_TOKEN": "your_read_only_token"
      }
    }
  }
}

Then ask the client for a bounded range:

Use release-intel to build release evidence for owner/repository
from v1.4.0 to v1.5.0. Separate merged PRs from direct commits
and preserve links to the repository record.

The token stays in the local server process and is sent only to the GitHub API.

Proof on this repository

A verified run against the stable range v0.5.1...8a2f350 returned:

Repository:        barissozudogru/release-intel-mcp
Commits:           14
Merged PRs:        1
Files changed:     12
Lines added:       286
Lines deleted:     135
Contributors:      1

The response also includes commit SHAs, messages, authors, pull request categories, linked issues, and warnings when GitHub truncates or fails part of the evidence lookup.

If this saves you time, consider starring the repository. It helps other developers find it.

Tools

The categorization uses labels and conventional title signals. Repository labels, issue links, and pull request hygiene directly affect the result. The server provides evidence and structure; the final release narrative still needs review.

Release report command

The package includes a terminal command that produces Markdown by default:

GITHUB_TOKEN=your_read_only_token \
  npx --yes --package @barissozudogru/release-intel-mcp \
  release-intel-report owner/repository v1.4.0 v1.5.0

Use --json when another tool will consume the report:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Release Intel: common questions

Is Release Intel MCP server safe?
Mostly: it is graded B (83/100). Read the Release Intel safety report
How do I install Release Intel?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Release Intel need an API key?
Yes. The registry entry asks for GITHUB_TOKEN.
Is Release Intel maintained?
The last commit was 7 days ago (2026-10-30). The latest release is v0.7.2.
What can I use instead of Release Intel?
Servers from other publishers that do the same job: GitLab MCP Server, GitHub MCP server and Gk CLI MCP server. Compare all Release Intel alternatives.
How does Release Intel compare with other Developer tools MCP servers?
safety score 83/100 (higher than 65% of 1,119 Developer tools servers); tools 3 (the typical Developer tools server has 7); tools that change things 0% (typical: 5%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Release Intel

Same job from other publishers: the closest match first, then the best rated.

All Release Intel alternatives →
  • GitLab MCP Server
    GitLab MCP server for projects, merge requests, issues, pipelines, wiki, releases, and more.
    B
  • GitHub
    Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
    A
  • Gk CLI
    The GitKraken MCP Server for managing repos, PRs, issues across GitHub, GitLab, Bitbucket and more.
    B
  • Git
    Comprehensive Git MCP server enabling native git tools including clone, commit, worktree, & more.
    A
  • SoloMD
    Read and search a folder of Markdown notes: search, backlinks, tags, tasks, outlines, git history.
    B

More from barissozudogru →