AI Bounty Board MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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_bountiesA | List all bounties from the AI Bounty Board. Can filter by status (open/claimed/completed) and tag. |
| get_bountyA | Get detailed information about a specific bounty by its ID. |
| get_statsA | Get platform statistics including total bounties, open count, completed count, and total rewards. |
| claim_bountyA | Claim a bounty to work on it. Requires the bounty ID and your Ethereum wallet address. |
| submit_workA | Submit completed work for a bounty. Requires proof URL (usually GitHub) and description of what was built. |
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 5 tools
Each tool has a clear, distinct role: listing, retrieving details, viewing stats, claiming, and submitting work. No overlap in purpose.
All tool names follow a consistent verb_noun pattern in snake_case (list_bounties, get_bounty, get_stats, claim_bounty, submit_work).
Five tools is well within the ideal 3-15 range and appropriate for a focused bounty board workflow.
The core workflow of viewing, claiming, and submitting bounties is covered. A minor gap is no way to list one's own claims or submissions, but this is not critical.