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/sosadly/blockbench-mcpInstalling this writes the configuration, not the program: `node` runs a file from the repository, so clone it first and make the path in the command match where you put it.
Wrote 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/sosadly/blockbench-mcp/blockbench)<a href="https://agentmods.dev/mcp/sosadly/blockbench-mcp/blockbench"><img src="https://agentmods.dev/badge/mcp/sosadly/blockbench-mcp/blockbench/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/sosadly/blockbench-mcp/blockbench"><img src="https://agentmods.dev/badge/mcp/sosadly/blockbench-mcp/blockbench.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
blockbench 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 2mo 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
{
"blockbench": {
"command": "node",
"args": [
"D:/projects/blockbench-mcp/dist/index.js"
],
"env": {
"BLOCKBENCH_MCP_PORT": "8787"
}
}
}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.
- 2mo ago First seen · 11 lines scan A daabd24ce8d7
blockbench is an MCP server published in the GitHub repository sosadly/blockbench-mcp (61 stars, last pushed 8d 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-08-31.
Other mcp servers, from other repositories
grok
MCP server "grok" as configured in stdevMac/grok-in-codex. Runs ./mcp/server.mjs with node.
chisel-mcp
MCP server "chisel-mcp" as configured in EYamanS/chisel. Runs locally from the chisel-mcp npm package.
mcp-test
MCP server "mcp-test" as configured in foobara/mcp-connector. Launched with examples/simple-mcp-server-example.
win-cli-mcp-server
MCP server "win-cli-mcp-server" as configured in mhprol/win-cli-mcp-server. Runs locally from the @mhprol/win-cli-mcp-server npm package.
elysia-mcp-starter
MCP server "elysia-mcp-starter" as configured in kerlos/elysia-mcp-starter. Runs locally from the elysia-mcp-starter npm package.
carbon-calculator-production
MCP server "carbon-calculator-production", hosted remotely at mcp-carbon-calculator.mcp-carbon-calculator.workers.dev, as configured in prdai/mcp-carbon-calculator. Needs 2 environment variables to run.