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/dcd887/mc-modpack-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/dcd887/mc-modpack-mcp/mc-modpack)<a href="https://agentmods.dev/mcp/dcd887/mc-modpack-mcp/mc-modpack"><img src="https://agentmods.dev/badge/mcp/dcd887/mc-modpack-mcp/mc-modpack/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/dcd887/mc-modpack-mcp/mc-modpack"><img src="https://agentmods.dev/badge/mcp/dcd887/mc-modpack-mcp/mc-modpack.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket warn
Grade A, and why
mc-modpack 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 3d 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
{
"mc-modpack": {
"command": "npx",
"args": [
"-y",
"mc-modpack-mcp"
],
"env": {}
}
}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.
- 3d ago First seen · 10 lines scan A d1ab00ddc542
mc-modpack is an MCP server published in the GitHub repository dcd887/mc-modpack-mcp (0 stars, last pushed 3d ago), 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-10-23.
Other mcp servers, from other repositories
mc-pack-builder
MCP server for Minecraft modpack building. Create pack.json, search mods, resolve dependencies, and manage pack structure. Runs locally from the mc-pack-builder-mcp npm package.
mine_mcp
MCP server "minemcp" as configured in rodcordeiro/minecraftmcp. Runs ${MINE_MCP_ROOT}/dist/index.js with node. Needs 1 environment variable to run.
sentry
Lets the agent search and read Sentry issues, errors and traces, and act on them. Runs locally from the @sentry/mcp-server npm package. Needs 1 environment variable to run.
resilireplay
Inject deterministic MCP failures, verify bounded recovery, and generate executable regression tests. Runs locally from the resilireplay npm package.
minecraft
MCP server "minecraft", hosted remotely at minecraft-mcp.mcjj.workers.dev, as configured in dcd887/minecraft-mcp-server.
modrinth
MCP server for searching Modrinth and publishing Minecraft mods (create projects, upload versions) via the Modrinth API. Runs locally from the @justinscott12/modrinth-mcp npm package. Needs 1 environment variable to run.