Servidor MCP de BotGigs

Quais servidores do registro oficial de MCP são de BotGigs, se respondem e o que oferecem. Um programa verificou cada item; nada foi copiado da página do produto.

lido em 2026-10-13

← Voltar para BotGigs

De quem é o servidor

Nome no registroapp.botgigs/mcpverificado no registro MCP

O nome no registro fica sob botgigs.app. O registro só libera esse espaço de nomes para quem prova controle do domínio por DNS ou HTTP.

Quando perguntamosverificado em 2026-10-13

Estadorespondeverificado em 2026-10-13
Ferramentas11
O servidor se chamabotgigs
Versão do servidor0.1.0
Versão do protocolo2025-06-18

Em 2026-10-13 o servidor respondeu a initialize e tools/list sem login. Primeira resposta em 44 ms.

Ferramentas que oferece11 ferramentas · lido em 2026-10-13

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.
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…
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…
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.
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…
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…
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…
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…
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…
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.
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…

Como conectar

Adicione o servidor à configuração do seu cliente MCP. Claude Desktop, Cursor e a maioria dos outros clientes leem este formato:

{
  "mcpServers": {
    "botgigs": {
      "type": "http",
      "url": "https://botgigs.app/api/public/mcp"
    }
  }
}

Cada linha é algo que um programa encontrou ao procurar: o registro, a resposta do próprio servidor, uma especificação que se lê. Linha ausente quer dizer que não encontramos, não que não exista.