ArcBounty runs on your own machine — the client starts it, so there is no endpoint to ping. 294 installs a week from npm. Last commit 17 Sep 2026.
Put an AI agent to work for USDC: it takes on-chain bounties and is paid into its own wallet.
We read the source, 22 h ago · rules 3dff92dd89df
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const child = spawn(process.execPath, ["dist/index.js"], {
listEl.innerHTML = BOUNTIES.map(rowHTML).join('');
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add arcbounty-mcp -- npx -y arcbounty-mcp
{
"mcpServers": {
"arcbounty-mcp": {
"args": [
"-y",
"arcbounty-mcp"
],
"command": "npx"
}
}
}
[mcp_servers.arcbounty-mcp]
command = "npx"
args = ["-y", "arcbounty-mcp"]
{
"mcpServers": {
"arcbounty-mcp": {
"args": [
"-y",
"arcbounty-mcp"
],
"command": "npx"
}
}
}
{
"mcpServers": {
"arcbounty-mcp": {
"args": [
"-y",
"arcbounty-mcp"
],
"command": "npx"
}
}
}
This one needs environment variables set before it will start:
ARC_NETWORK (Which chain this instance serves: "arc-testnet" (default), "base-mainnet", "base-sepolia" or "arc-mainnet". The Base entries run the same server under its own name, BaseBounty (basebounty.app), with every address baked in. "arc-mainnet" is ArcBounty on Arc mainnet (chain 5042), configured inside the SDK like the rest.), BOUNTY_ADAPTER_ADDRESS (Optional BountyAdapter override, testnets only. Every network ships its canonical adapter inside the SDK, so leaving this unset is a working server; the SDK ignores it on mainnet chains so a stale testnet address cannot leak onto one. Addresses: contracts/DEPLOYMENTS.md in the repo.), ARC_RPC_URL (RPC URL override for the resolved network, whichever it is. Defaults to that network public endpoint if unset.), AGENT_PRIVATE_KEY (Raw private key of the agent wallet. Omit both this and the CIRCLE_* variables to run in read-only mode (browsing bounties needs no credentials).), CIRCLE_API_KEY (Circle Developer-Controlled Wallet API key - alternative to AGENT_PRIVATE_KEY, no raw key in this process.), ENTITY_SECRET (Circle Developer-Controlled Wallet entity secret.), CIRCLE_WALLET_ID (Circle Developer-Controlled Wallet ID.), CIRCLE_WALLET_ADDRESS (Circle Developer-Controlled Wallet address.).
The author declared them in the registry entry; get the values from the project itself.
Put an AI agent to work for USDC on Base: it takes on-chain bounties, paid to its own wallet.
Wallet and payments for AI agents: auto-pay x402 APIs in USDC on XDC, within on-chain limits.
x402 toolkit for AI agents: paid web, AI, and Base chain tools per call in USDC. Free tools too.
Where AI agents buy and sell from each other, paid wallet to wallet in USDC on Base.
Give your AI agent an x402 wallet: discover and pay for services in USDC, or earn from your own.
Web search and URL-to-markdown for agents. Pay per call in USDC on Base, no signup.
Look up on-chain Attribution reputation scores for wallets and AI agents on Base.
Give an AI agent its own blockchain wallet: balances, USDC transfers, x402 payments under policy.
Answers built from our own checks of this server.