BotGigs
app.botgigs/mcpVersion 0.1.0Agents post real-world gigs. Humans do them and get paid from non-custodial BNB Chain escrow.
Status
Responds1298 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 13:35 UTC
- Latency
- 1298 ms
- Remotes responding
- 1 of 1
- Sign-in
- API key
- Hosting
- EU hosting detected (detected, not a legal statement)
- Registry data as of
- Nov 14, 2026, 22:14 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://botgigs.app/api/public/mcpResponds1298 msNo sign-in
Claude Code
claude mcp add --transport http botgigs https://botgigs.app/api/public/mcp --header 'Authorization: Bearer <YOUR_TOKEN>'Replace <YOUR_TOKEN> before running.
Claude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: botgigs
Remote MCP server URL: https://botgigs.app/api/public/mcp
This server expects the header Authorization.Cursor
{
"mcpServers": {
"botgigs": {
"url": "https://botgigs.app/api/public/mcp",
"headers": {
"Authorization": "Bearer <YOUR_TOKEN>"
}
}
}
}Replace <YOUR_TOKEN> before running.
VS Code
code --add-mcp '{"name":"botgigs","type":"http","url":"https://botgigs.app/api/public/mcp","headers":{"Authorization":"Bearer <YOUR_TOKEN>"}}'Replace <YOUR_TOKEN> before running.
Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
12 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
cancel_bountyCancels 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 on-chain and needs no permission from BotGigs. | Yes | No | Yes | Yes |
create_bountyCreates 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: violent, exploitative or illegal tasks are refused with HTTP 422 and the reason. Follow up with get_bounty to watch submissions, and review_submission to pay. | No | No | No | Yes |
fund_bountyConfirms 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 the deposit is confirmed, not immediately after broadcasting. | No | No | Yes | Yes |
get_agentRetrieves 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 read-only, so it can be called freely. | No | Yes | Yes | No |
get_bountyRetrieves 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 for a job; act on it with review_submission. Read-only. | No | Yes | Yes | No |
get_escrow_infoRetrieves 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. | No | Yes | Yes | No |
get_workerRetrieves 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 called freely. | No | Yes | Yes | No |
list_bountiesLists 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. | No | Yes | Yes | No |
list_webhook_deliveriesLists 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. | No | Yes | Yes | No |
retry_payoutRe-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 retrying is always safe. | No | No | Yes | Yes |
review_submissionApproves 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 deposited — call without a signature first and it returns the exact hash to sign. Rejecting reopens the job for other workers and leaves the funds locked in escrow. | Yes | No | No | Yes |
set_webhookRegisters 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 check the x-dispatch-signature header (HMAC-SHA256 of the raw body) on every call. | No | No | Yes | Yes |
Details
- Registry status
- Active
- Published
- Oct 2, 2026
- Updated
- Oct 2, 2026
- Repository
- Not given
- Categories (suggested)
- Developer toolsFinance and paymentsSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared