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/Sofiia7/ARCWrote 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/sofiia7/arc/arcbounty-mcp)<a href="https://agentmods.dev/mcp/sofiia7/arc/arcbounty-mcp"><img src="https://agentmods.dev/badge/mcp/sofiia7/arc/arcbounty-mcp.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
arcbounty-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 7d 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
{
"arcbounty-mcp": {
"command": "npx",
"args": [
"-y",
"arcbounty-mcp"
],
"env": {
"ARC_NETWORK": "arc-testnet",
"BOUNTY_ADAPTER_ADDRESS": "",
"ARC_RPC_URL": "",
"AGENT_PRIVATE_KEY": "",
"CIRCLE_API_KEY": "",
"ENTITY_SECRET": "",
"CIRCLE_WALLET_ID": "",
"CIRCLE_WALLET_ADDRESS": ""
}
}
}What else server.json configures
This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.
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.
- 7d ago First seen · 19 lines scan A 306209243a4e
arcbounty-mcp is an MCP server published in the GitHub repository Sofiia7/ARC (0 stars, last pushed 4d 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
mcp-moonpay
MCP server for MoonPay — fiat-to-crypto on/off-ramp, 100+ assets; Pix for Brazil onramp. Runs locally from the @codespar/mcp-moonpay npm package. Needs 6 environment variables to run.
mcp-coinbase-cdp
MCP server for Coinbase Developer Platform (CDP) — Trading, Wallets, Payments under one CDP key. Runs locally from the @codespar/mcp-coinbase-cdp npm package. Needs 2 environment variables to run.
mcp-foxbit
MCP server for Foxbit — Brazilian crypto exchange, trading, orderbook, institutional. Runs locally from the @codespar/mcp-foxbit npm package. Needs 2 environment variables to run.
mcp-transak
MCP server for Transak — fiat-to-crypto on/off-ramp across 170 countries (Partner API). Runs locally from the @codespar/mcp-transak npm package. Needs 3 environment variables to run.
mcp-unblockpay
MCP server for UnblockPay — fiat-to-stablecoin onramp/offramp, wallets, transfers. Runs locally from the @codespar/mcp-unblockpay npm package. Needs 2 environment variables to run.
mcp-bitso
MCP server for Bitso — Latin American crypto exchange, trading, funding, withdrawals. Runs locally from the @codespar/mcp-bitso npm package. Needs 1 environment variable to run.