Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/barissozudogru/release-intel-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/barissozudogru/release-intel-mcp/release-intel)<a href="https://agentmods.dev/mcp/barissozudogru/release-intel-mcp/release-intel"><img src="https://agentmods.dev/badge/mcp/barissozudogru/release-intel-mcp/release-intel/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/barissozudogru/release-intel-mcp/release-intel"><img src="https://agentmods.dev/badge/mcp/barissozudogru/release-intel-mcp/release-intel.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
release-intel scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"release-intel": {
"command": "npx",
"args": [
"-y",
"@barissozudogru/release-intel-mcp"
],
"env": {
"GITHUB_TOKEN": ""
}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 12 lines scan A 8e4c046afad5
release-intel is an MCP server published in the GitHub repository barissozudogru/release-intel-mcp (2 stars, last pushed today), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other mcp servers, from other repositories
mcp-github-pm
MCP server for GitHub project management — create issues, auto-label, track milestones, generate changelogs from Claude. Runs locally from the mcp-github-pm npm package.
obsidian-github-mcp
A permissioned MCP gateway for agent proposals to a Git-backed Obsidian vault. Runs locally from the @sarutobi-sasuke/obsidian-github-mcp npm package. Needs 9 environment variables to run.
gitlog-mcp
Give AI agents superpowers over git history — changelogs, commit analysis, blame, and release notes via MCP. Runs locally from the gitlog-mcp Python package.
mcp-git-issue-priority
MCP server for GitHub issue prioritization and workflow management. Runs locally from the mcp-git-issue-priority npm package.
changelog-mcp
MCP server "changelog-mcp" as configured in smartsys/changelog-mcp. Runs locally from the changelog-mcp Python package.
releases
MCP server "releases", hosted remotely at agents.releases.sh, as configured in buildinternet/releases-cli.