release-intel-mcpSAFE
Auditable release evidence from commits, pull requests, issues, and contributors between two Git refs, over MCP or CLI.
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
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/reledfbe82fc3e69OBSERVED · 2026-10-11Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.
claude mcp add release-intel-mcp --env GITHUB_TOKEN=${GITHUB_TOKEN} -- npx -y @barissozudogru/[email protected]Exposed tools (3)
3 read · 0 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
get_changes_between_refs | read | |
get_pull_requests_in_range | read | |
get_release_summary | read |
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | WARN |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- declared (3 observation(s))
- Shell
- none-observed
- Dependencies
- not all pinned
- Secrets in source
- none-found
Findings (2)
process.stderr.write(`release-intel-mcp v${VERSION} listening on http://0.0.0.0:${port}/mcp\n`);@modelcontextprotocol/sdk, express, zod, @types/express, @types/node, typescript
Gates applied: no_behavioural_pass.
dfbe82fc3e69full audit observations/trust-audit/mcp-server/barissozudogru__release-intel-mcp.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-11 | dfbe82fc3e69 | SAFE | B | 89 | first audit |
Questions
What is the release-intel-mcp MCP server?
Auditable release evidence from commits, pull requests, issues, and contributors between two Git refs, over MCP or CLI.
What tools does release-intel-mcp expose?
3 in total: 3 read-only, 0 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.
Is release-intel-mcp safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.
What credentials does release-intel-mcp need?
It reads GITHUB_TOKEN from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.
How does release-intel-mcp run?
It speaks stdio and streamable-http, so it runs as a local process your client starts. It is published on npm as @barissozudogru/release-intel-mcp at 0.7.2.
How current is this page?
The grade is for one exact copy of the source (dfbe82fc3e69), read on 2026-10-11. The repository is watched and re-audited when it changes.