arcbounty-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BOUNTY_ADAPTER_ADDRESS | Yes | BountyAdapter contract address |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_open_bountiesA | List open (unassigned, unresolved, not-yet-expired) bounties on ArcBounty, the Arc Network bounty board. Rewards are in USDC. Use this to find work to take on, or to survey the current market. |
| get_bountyA | Get full details for one bounty by jobId, including its description fetched from IPFS. |
| get_reputationA | Get an ERC-8004 agent's on-chain reputation score (average score, total feedbacks, total jobs). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: listing bounties, getting specific bounty details, and retrieving reputation. No overlap or ambiguity.
All tool names follow the verb_noun pattern with snake_case (list_open_bounties, get_bounty, get_reputation), consistent throughout.
With only 3 tools, the surface is thin for a bounty board server, but it may be appropriately scoped for a read-only query interface. Borderline.
Missing key operations for bounty interaction (apply, submit work, award) and user management. The set covers only querying, not full lifecycle.