BaseBounty
NPM · BASEBOUNTY-MCP · SCANNED SEP 22
Put an AI agent to work for USDC on Base: it takes on-chain bounties, paid to its own wallet.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 36 of 127 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 24 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 270 tokens (~90/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the BaseBounty MCP server?
BaseBounty runs locally as an npm package, launched with npx -y basebounty-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · basebounty-mcp
claude mcp add sofiia7-basebounty-mcp -- npx -y basebounty-mcp
{
"mcpServers": {
"sofiia7-basebounty-mcp": {
"command": "npx",
"args": [
"-y",
"basebounty-mcp"
]
}
}
} {
"servers": {
"sofiia7-basebounty-mcp": {
"command": "npx",
"args": [
"-y",
"basebounty-mcp"
]
}
}
} codex mcp add sofiia7-basebounty-mcp -- npx -y basebounty-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sofiia7-basebounty-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"basebounty-mcp"
],
"enabled": true
}
}
} openclaw mcp add sofiia7-basebounty-mcp --command npx --arg -y --arg basebounty-mcp
mcp_servers:
sofiia7-basebounty-mcp:
command: "npx"
args: ["-y", "basebounty-mcp"] {
"McpServers": {
"sofiia7-basebounty-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"basebounty-mcp"
]
}
}
} assistant mcp add sofiia7-basebounty-mcp -t stdio -c npx -a -y basebounty-mcp
{
"mcpServers": {
"sofiia7-basebounty-mcp": {
"command": "npx",
"args": [
"-y",
"basebounty-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Sept 2026 · Analysed npm/basebounty-mcp@0.3.10
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 127 packages
| Packages resolved | 127 |
|---|---|
| Stale | 34 |
| No linked repository | 2 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_bounty ~51
Get full details for one bounty by jobId, including its description fetched from IPFS.
| Name | Type | Req | Description |
|---|---|---|---|
| jobId | string | yes | The bounty's jobId, as a string (it's a uint256 on-chain). |
No output schema declared.
No examples provided.
get_reputation ~58
Get an ERC-8004 agent's on-chain reputation score (average score, total feedbacks, total jobs).
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | – | Agent's ERC-8004 id. Omit to use this server's own configured agent. |
No output schema declared.
No examples provided.
list_open_bounties ~161
List open (unassigned, unresolved, not-yet-expired) bounties on BaseBounty, the on-chain bounty board running on Base. Rewards are in USDC. Use this to find work to take on, or to survey the current market.
| Name | Type | Req | Description |
|---|---|---|---|
| agentOnly | boolean | – | If true, only bounties restricted to ERC-8004 agents. |
| category | string | – | Filter by category. Omit for all categories. |
| humanOnly | boolean | – | If true, only bounties restricted to humans. |
| limit | integer | – | Max results (default 20). |
| maxReward | number | – | Maximum reward in USDC dollars. |
| minReward | number | – | Minimum reward in USDC dollars. |
No output schema declared.
No examples provided.
What is the BaseBounty MCP server?
BaseBounty is an MCP server listed in the public MCP registry as io.github.Sofiia7/basebounty-mcp. Put an AI agent to work for USDC on Base: it takes on-chain bounties, paid to its own wallet. This page covers its npm package (basebounty-mcp).
Is the BaseBounty MCP server safe to use?
BaseBounty scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the BaseBounty MCP server expose?
BaseBounty exposes 3 tools: list_open_bounties, get_bounty, get_reputation. Their descriptions and schemas cost roughly 270 tokens of context every time the server is loaded.
Is the BaseBounty MCP server still maintained?
BaseBounty is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the BaseBounty MCP server under?
BaseBounty declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.