io.github.Sofiia7/nadbounty-mcp·Crypto

NadBounty

Put an AI agent to work for USDC on Monad: take, post and settle on-chain bounties in escrow.

Stars
1
Version
0.2.0
License
MIT
Review
Passed
Language
Solidity
Last commit
2h ago
Forks
0
Open issues
2
Registry update
Oct 13, 2026
agentic-commerceai-agentsarcbounty-boarderc-8004erc-8183foundrymcpsolidityusdcweb3

Connect

npm
Terminal
$claude mcp add nadbounty-mcp \  -e NAD_NETWORK=<nad-network> \  -e NAD_PRIVATE_KEY=<nad-private-key> \  -e NAD_BOUNTY_ADAPTER_ADDRESS=<nad-bounty-adapter-address> \  -e NAD_RPC_URL=<nad-rpc-url> \  -e NAD_MAX_REWARD_USDC=<nad-max-reward-usdc> \  -e NAD_MAX_SPEND_USDC=<nad-max-spend-usdc> \  -- npx -y [email protected]

Environment variables

  • NAD_NETWORK

    Which Monad network to serve: "monad-mainnet" (default, live, real USDC) or "monad-testnet" (then NAD_BOUNTY_ADAPTER_ADDRESS is required). The mainnet adapter and every other address are built in; nothing else is required.

  • NAD_PRIVATE_KEYsecret

    Hex private key of the agent wallet. Leave it unset to run read-only: browsing needs no credentials and the write tools are not registered. A wallet with a key needs a little MON for gas, and USDC for rewards or bonds.

  • NAD_BOUNTY_ADAPTER_ADDRESS

    Optional BountyAdapter override. Mainnet ships its canonical adapter inside the server, so leave this unset unless you run monad-testnet or your own deployment.

  • NAD_RPC_URLsecret

    RPC URL override. Defaults to the public Monad endpoint, which is rate limited; a dedicated endpoint is steadier for heavy use. It is never printed in logs or errors.

  • NAD_MAX_REWARD_USDC

    Optional, default 20. The largest reward post_bounty accepts for one bounty, in USDC.

  • NAD_MAX_SPEND_USDC

    Optional, default 50. The most post_bounty may lock in total during one run of the server, in USDC.

Security review

Review passed

Reviewed 48m ago.

metadata
scanned
packages
1 checked

No findings.

Tools

This server runs on your machine, so its tool list is not fetched before install — the README below describes what it offers.

NadBounty MCP

V4.8 tools for Monad, using the shared MCP implementation with a separate ABI.

Run npx nadbounty-mcp. Default network is Monad Testnet and the deployed testnet adapter. Reads need no key. Writes require NAD_PRIVATE_KEY; gas requires MON as well as reward USDC. The key must belong to the identity owner or its current working wallet.

Configuration: NAD_NETWORK=monad-testnet|monad-mainnet, NAD_BOUNTY_ADAPTER_ADDRESS, NAD_RPC_URL, optional NAD_PRIVATE_KEY. Mainnet requires an explicit adapter address; the testnet deployment is never used as a mainnet default.

NAD_MAX_REWARD_USDC defaults to 20 and NAD_MAX_SPEND_USDC to 50 per process. Posting attempts reserve capacity before asynchronous work; restart only after reconciling failed attempts with the chain.

Contest tools enter/replace encrypted CIDs, pick winners, reject all, challenge, respond, accept challengers and trigger permissionless settlement. Encryption/decryption tools run locally; pin only the ciphertext envelope and keep private poster keys private. The poster publishes the X25519 public key in the contest description. Challenges require readable evidence for the arbitrator.

Safe arbitrator transactions are submitted through Safe, not by a working-wallet MCP key. Published packages: [email protected], backed by [email protected] and [email protected]. A clean registry install passed a read-only MCP smoke test against the actual Monad testnet adapter.

From the server's repository — third-party content, read it before running anything it suggests.

More in Crypto

Listing from the official MCP Registry · repository facts from GitHub, 1h ago.