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/BlockRunAI/blockrun-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/plugins/blockrunai/blockrun-mcp/blockrun-upgrade)<a href="https://agentmods.dev/plugins/blockrunai/blockrun-mcp/blockrun-upgrade"><img src="https://agentmods.dev/badge/plugins/blockrunai/blockrun-mcp/blockrun-upgrade.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
blockrun-upgrade 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 4d 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
{
"name": "blockrun-upgrade",
"source": "./skills/blockrun-upgrade",
"description": "Use when the server prints 'Update available', when asked to upgrade, pin or roll back @blockrun/mcp, when a fix should be in the new version but the client still runs the old one, or when refreshing skills copied into a project."
}What ships with it
1 file beside marketplace.json#blockrun-upgrade in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 5 lines scan A ba38ecb70513
blockrun-upgrade is a plugin published in the GitHub repository BlockRunAI/blockrun-mcp (393 stars, last pushed today), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-09-03.
Other plugins, from other repositories
onesource
38 tools for live blockchain queries and REST API documentation, via x402 micropayments.
hyper-mcp
A fast, secure MCP server that extends its capabilities through WebAssembly plugins.
livetennisapi
Real-time and historical tennis data for Claude — live scores, match state (server, break-point, retirement/walkover), players, rankings, fixtures, head-to-head and the 1968-2022 results archive across ATP, WTA, Challenger, ITF and juniors. Connects to the Live Tennis API (free tier available, no card); collects no…
declaude
Rewrites Claude-English into plain English: sycophantic openers, hedging filler and padded phrasing out, facts, code blocks, names and numbers untouched. Runs an open-weights model on dedicated GPUs, so text never reaches a commercial AI provider.
onchainai
Discover, vet, and install crypto MCP/CLI/SDK/API/x402/AI-agent tools via the OnchainAI directory. Free discovery on /mcp; optional premium x402 tools.
artificial-analysis
Get LLM model pricing, speed metrics, and benchmark scores from Artificial Analysis.