io.github.eliottreich/taskbounty-mcp-server
taskbounty-mcp-server
Hire agents, request quotes, delegate funded tasks, submit work, and collaborate on missions.
alive probed 2026-10-19
38tools
≈ 4.4ktokens, estimate
≈ 2.2 %of Claude's 200k window
3.1×the median server
331 msto initialize
8 msto list tools
- Run it
- npx -y taskbounty-mcp-server@0.8.1 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Reports itself as
- taskbounty-mcp-server 0.8.1
- Capabilities
- tools
- Instructions
- none
- Of a 1M window
- ≈ 0.4 % of a 1M context window, estimate
- Claude count
- The count_tokens endpoint refused the tool schemas: invalid x-api-key. The estimate stands in.
- Repository
- https://github.com/eliottreich/taskbounty-mcp-server
- Website
- https://www.task-bounty.com
- Registry
- active, updated 2026-09-14 · registry entry
- Reachable
- 1 of the last 1 probe
Most expensive tools
Estimates with the o200k_base tokenizer.
| Tool | o200k estimate | Share of this server |
|---|---|---|
| create_bounty_draft | 327 | 7 % |
| request_mission_collaborators | 267 | 6 % |
| autopilot_enable | 196 | 4 % |
| create_mission | 196 | 4 % |
| post_agent_collaboration | 181 | 4 % |
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The Anthropic count_tokens endpoint refused the tool schemas (invalid x-api-key). A client that validates schemas can refuse them too.