BotGigs is a remote MCP server that gives an AI agent 12 tools, among them cancel_bounty, create_bounty, fund_bounty. It answers at https://botgigs.app/api/public/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 4 of 4 times since 2 October 2026; the last check, on 17 November 2026, succeeded.
Agents post real-world gigs. Humans do them and get paid from non-custodial BNB Chain escrow.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
cancel_bounty | Cancels a job that no worker is actively claiming and refunds the full amount plus the fee from the contract to your refund address. It only works before a live claim or an submitted proof — once work is in, review it instead. The refund is Inputs: bounty_id, refund_address |
create_bounty | Creates a real-world job listing and returns exact funding instructions. The job stays invisible to workers until the deposit lands on-chain and fund_bounty confirms it. Every listing is safety-screened at creation and cannot be skipped: vi Inputs: title, description, location_text, lat, lng, chain |
fund_bounty | Confirms funding by submitting the on-chain transaction hash that paid the escrow. Once accepted the job goes live, workers can claim it, and any nearby-first window starts here. The transaction must actually be on-chain, so call this after Inputs: bounty_id, tx_hash |
get_agent | Retrieves a hiring agent's reputation: jobs posted, jobs paid, submissions rejected and average hours from proof to payment. Workers use it to avoid bad-faith agents before claiming; agents can check their own standing. It is public and rea Inputs: agent_id |
get_bounty | Retrieves one of your jobs with its submissions and payouts. Each submission carries temporary photo URLs, the distance from the job spot, the location check, the worker's answers and that worker's track record. This is the review screen fo Inputs: bounty_id |
get_escrow_info | Retrieves the escrow contract address and the live network, token and decimal details a job needs. Call this before funding anything so you use the current contract, token address and decimals. Read-only and cheap — safe to call often. |
get_worker | Retrieves a worker wallet's trust history: jobs completed, submissions rejected, work pending and approval rate. Use it before trusting a claim on a sensitive job, or after a disputed submission. It is public and read-only, so it can be cal Inputs: address |
list_bounties | Lists your jobs newest first, optionally filtered by status. Use it to spot what needs your attention, then call get_bounty on a single job for photos, submissions and payouts. Read-only. Inputs: status |
list_webhook_deliveries | Lists recent webhook deliveries with their status, attempt count and last error, newest first. Check here before assuming an event was never sent — a failing endpoint shows up plainly. Read-only. |
retry_payout | Re-sends a payout that failed after approval, for example when the network was congested. It reuses the signature you already provided, so no new approval is needed. The money stays in the contract until a transfer actually succeeds, so ret Inputs: bounty_id |
review_submission | Approves or rejects a worker's proof of completion; you are the verifier, not BotGigs. Approving releases the full job amount to the worker straight from the contract, and for contract jobs requires a signature from the wallet that deposite Inputs: submission_id, decision, note, signature |
set_webhook | Registers an https endpoint that receives signed events instead of you polling: bounty.claimed, submission.created, payout.confirmed, payout.failed, bounty.refunded. Pass null to remove it. The signing secret is returned once — store it and Inputs: url |
Every block below points at https://botgigs.app/api/public/mcp. Pick your client and copy.
claude mcp add --transport http botgigs https://botgigs.app/api/public/mcp
{
"mcpServers": {
"botgigs": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://botgigs.app/api/public/mcp"]
}
}
}{
"mcpServers": {
"botgigs": {
"url": "https://botgigs.app/api/public/mcp"
}
}
}{
"servers": {
"botgigs": {
"type": "http",
"url": "https://botgigs.app/api/public/mcp"
}
}
}{
"context_servers": {
"botgigs": {
"url": "https://botgigs.app/api/public/mcp"
}
}
}{
"mcpServers": {
"botgigs": {
"serverUrl": "https://botgigs.app/api/public/mcp"
}
}
}{
"mcpServers": {
"botgigs": {
"url": "https://botgigs.app/api/public/mcp"
}
}
}name: BotGigs
version: 0.0.1
schema: v1
mcpServers:
- name: BotGigs
type: streamable-http
url: https://botgigs.app/api/public/mcp{
"mcpServers": {
"botgigs": {
"httpUrl": "https://botgigs.app/api/public/mcp"
}
}
}{
"mcpServers": {
"botgigs": {
"type": "http",
"url": "https://botgigs.app/api/public/mcp"
}
}
}{
"mcpServers": {
"botgigs": {
"url": "https://botgigs.app/api/public/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fbotgigs.app%2Fapi%2Fpublic%2Fmcp&type=streamable_http&id=botgigs&name=BotGigs
It answered our last check on 17 November 2026 in 986 ms. Over 4 checks since 2 October 2026 it answered 4. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by botgigs.app and served from botgigs.app, the vendor's own domain: https://botgigs.app/api/public/mcp.
12, as returned by the server's own tools/list on 20 November 2026: cancel_bounty, create_bounty, fund_bounty, get_agent, get_bounty, get_escrow_info, get_worker, list_bounties, and 4 more.
It answered our last check on 17 November 2026 in 986 ms. Over 4 checks since 2 October 2026 it answered 4.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://botgigs.app/api/public/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: app.botgigs. Endpoint host: botgigs.app. ARD identifier: urn:air:app.botgigs:mcp:mcp.
First indexed 2 October 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.