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/buildinternet/releasesWrote 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/buildinternet/releases/mcp-mcp)<a href="https://agentmods.dev/mcp/buildinternet/releases/mcp-mcp"><img src="https://agentmods.dev/badge/mcp/buildinternet/releases/mcp-mcp/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/buildinternet/releases/mcp-mcp"><img src="https://agentmods.dev/badge/mcp/buildinternet/releases/mcp-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
mcp 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
{
"mcp": {
"url": "https://agents.releases.sh/mcp",
"type": "streamable-http"
}
}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 Changed 5e2f40967754
- 1mo ago First seen · 6 lines scan A 173bfffbedc1
mcp is an MCP server published in the GitHub repository buildinternet/releases (9 stars, last pushed today), licensed Apache-2.0. 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
openaffiliate-mcp
Search and discover affiliate programs with agent-ready data and commission details. Runs locally from the openaffiliate-mcp npm package.
releases
MCP server "releases", hosted remotely at agents.releases.sh, as configured in buildinternet/releases-cli.
skyvern
AI-powered browser automation — navigate, click, fill forms, and extract data from any website. Remote server at api.skyvern.com.
next-devtools
Next.js development tools MCP server with stdio transport. Runs locally from the next-devtools-mcp npm package.
proximo-proxmox
The Proxmox MCP you can hand the keys: VE/PBS/PMG/PDM. Plan, prove, undo, diagnose. MCP/A2A/API. Runs locally from the proximo-proxmox Python package.
lean-explore
MCP server "lean-explore", hosted remotely at www.leanexplore.com, as configured in lean-explore/lean-explore.