NadBounty MCP Server

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

Local serverstdio

What is the NadBounty MCP Server?

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

Packages and local setup

The published npm package is nadbounty-mcp, version 0.2.0. Its declared MCP transport is stdio.

The package declares 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_KEY: 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_URL: 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..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 0.2.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related blockchain & web3 MCP servers for tools that cover the same kind of work.

Configuration

VariableDescriptionRequired
NAD_NETWORKWhich 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.Check documentation
NAD_PRIVATE_KEYHex 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.Check documentation
NAD_BOUNTY_ADAPTER_ADDRESSOptional BountyAdapter override. Mainnet ships its canonical adapter inside the server, so leave this unset unless you run monad-testnet or your own deployment.Check documentation
NAD_RPC_URLRPC 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.Check documentation
NAD_MAX_REWARD_USDCOptional, default 20. The largest reward post_bounty accepts for one bounty, in USDC.Check documentation
NAD_MAX_SPEND_USDCOptional, default 50. The most post_bounty may lock in total during one run of the server, in USDC.Check documentation