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/agustincf/Arcade1v1Wrote 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/agustincf/arcade1v1/mcp-arcade1v1)<a href="https://agentmods.dev/mcp/agustincf/arcade1v1/mcp-arcade1v1"><img src="https://agentmods.dev/badge/mcp/agustincf/arcade1v1/mcp-arcade1v1/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/agustincf/arcade1v1/mcp-arcade1v1"><img src="https://agentmods.dev/badge/mcp/agustincf/arcade1v1/mcp-arcade1v1.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
arcade1v1 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 9d 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
{
"arcade1v1": {
"command": "npx",
"args": [
"-y",
"@arcade1v1/mcp"
],
"env": {
"ARBITER_URL": ""
}
}
}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.
- 9d ago First seen · 12 lines scan A a3b87a738604
arcade1v1 is an MCP server published in the GitHub repository agustincf/Arcade1v1 (0 stars, last pushed 2d 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
clash-mcp
Play three.ws Coin Clash — read the faction battle board and leaderboard, enlist, and rally. Runs locally from the @three-ws/clash-mcp npm package. Needs 3 environment variables to run.
magpie-mcp
Agent-native lending on Solana via x402: borrow against tokens, arm in-vault TP/SL, repay. Runs locally from the @magpieloans/magpie-mcp npm package.
gittr-mcp
MCP server "gittr-mcp" as configured in arbadacarbaYK/gittr-mcp. Runs locally from the gittr-mcp npm package. Needs 3 environment variables to run.
mcp-server
BattleGrid MCP server — play crypto prediction games from AI agents. Runs locally from the @battlegrid/mcp-server npm package.
stipend
Non-custodial USDC wallet on Base with spending limits enforced in code, not in a prompt. Runs locally from the stipend npm package.
loot-agent-mcp
MCP server "loot-agent-mcp" as configured in D-Kek/loot-agent-mcp. Runs locally from the loot-agent-mcp npm package. Needs 4 environment variables to run.