Connect

8 clients · secrets stay placeholders

JSON (mcpServers)Claude CodeCodexOpenCodeCursorVS CodeGemini CLIGoose

{
  "mcpServers": {
    "botgigs": {
      "type": "http",
      "url": "https://botgigs.app/api/public/mcp",
      "headers": {
        "Authorization": "Bearer ${BOTGIGS_TOKEN}"
      }
    }
  }
}

claude mcp add --transport http botgigs https://botgigs.app/api/public/mcp --header "Authorization: Bearer ${BOTGIGS_TOKEN}"

[mcp_servers.botgigs]
url = "https://botgigs.app/api/public/mcp"
bearer_token_env_var = "BOTGIGS_TOKEN"

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "botgigs": {
      "type": "remote",
      "url": "https://botgigs.app/api/public/mcp",
      "enabled": true,
      "headers": {
        "Authorization": "Bearer {env:BOTGIGS_TOKEN}"
      }
    }
  }
}

{
  "mcpServers": {
    "botgigs": {
      "type": "http",
      "url": "https://botgigs.app/api/public/mcp",
      "headers": {
        "Authorization": "Bearer ${BOTGIGS_TOKEN}"
      }
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=botgigs&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vYm90Z2lncy5hcHAvYXBpL3B1YmxpYy9tY3AiLCJoZWFkZXJzIjp7IkF1dGhvcml6YXRpb24iOiJCZWFyZXIgJHtCT1RHSUdTX1RPS0VOfSJ9fQ%3D%3D"
}

{
  "servers": {
    "botgigs": {
      "type": "http",
      "url": "https://botgigs.app/api/public/mcp",
      "headers": {
        "Authorization": "Bearer ${BOTGIGS_TOKEN}"
      }
    }
  }
}

{
  "mcpServers": {
    "botgigs": {
      "httpUrl": "https://botgigs.app/api/public/mcp",
      "headers": {
        "Authorization": "Bearer ${BOTGIGS_TOKEN}"
      }
    }
  }
}

extensions:
  "botgigs":
    enabled: true
    name: "botgigs"
    type: streamable_http
    uri: "https://botgigs.app/api/public/mcp"
    headers:
      "Authorization": "Bearer ${BOTGIGS_TOKEN}"
    timeout: 300

Placeholders to fill from your own secret store: ${BOTGIGS_TOKEN}. The registry never accepts secret values.

Quality 75 / 100good

protocol75 · weight 25

warn
protocol.modernnewest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
n/a
protocol.statelessonly applies to 2026-07-28 servers
pass
protocol.transportstreamable HTTP
n/a
protocol.list_ttlonly applies to 2026-07-28 servers

authorizationn/a · weight 15

n/a
auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
n/a
auth.secret_in_urlno templated URL

tool hygiene100 · weight 30

pass
tools.descriptionsevery tool has a description
pass
tools.description_lengthdescriptions are concise
pass
tools.schemasevery tool has an object input schema
pass
tools.annotations11 of 11 tools declare readOnlyHint or destructiveHint
pass
tools.directory_hintsevery tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
pass
tools.token_costabout 1,961 tokens to load every tool
pass
tools.api_dumptools are not a one-to-one API dump

stability25 · weight 15

warn
stability.changes11 tool changes in 30 days
fail
stability.rug_pull11 tools kept their name but changed most of their description in 30 days; review before trusting them

dependenciesn/a · weight 15

n/a
deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

11 tools, about 1,961 tokens to load them all · tool set 5aeaff473b64 · tools last changed 2026-10-02 · checked 2026-10-20 07:53 UTC

Tool changes

2026-10-02get_workerchangedtitle, description, input schema, output schema, annotationsmeaning changed
before
A worker wallet's trust history: completed, rejected, approval rate.
after · 27% of words in common
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 called freely.
2026-10-02list_webhook_deliverieschangedtitle, description, output schema, annotationsmeaning changed
before
Recent webhook deliveries and their status.
after · 19% of words in common
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.
2026-10-02set_webhookchangedtitle, description, input schema, output schema, annotationsmeaning changed
before
Set (or clear with null) an https URL that receives signed events: bounty.claimed, submission.created, payout.confirmed, payout.failed, bounty.refunded. Returns the signing secret once.
after · 37% of words in common
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 check the x-dispatch-signature header (HMAC-SHA256 of the raw body) on every call.
2026-10-02cancel_bountychangedtitle, description, input schema, output schema, annotationsmeaning changed
before
Cancel an unclaimed bounty and refund escrow.
after · 7% of words in common
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 on-chain and needs no permission from BotGigs.
2026-10-02retry_payoutchangedtitle, description, input schema, output schema, annotationsmeaning changed
before
Retry a failed payout for a bounty.
after · 10% of words in common
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 retrying is always safe.
2026-10-02review_submissionchangedtitle, description, input schema, output schema, annotationsmeaning changed
before
Approve (releases escrow to the worker) or reject (reopens the job) a submission. You are the verifier.
after · 23% of words in common
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 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.
2026-10-02get_bountychangedtitle, description, input schema, output schema, annotationsmeaning changed
before
Get a bounty with its submissions (with temporary photo URLs) and payouts.
after · 21% of words in common
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 for a job; act on it with review_submission. Read-only.
2026-10-02list_bountieschangedtitle, description, input schema, output schema, annotationsmeaning changed
before
List your bounties, optionally filtered by status.
after · 15% of words in common
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.
2026-10-02fund_bountychangedtitle, description, input schema, output schema, annotationsmeaning changed
before
Confirm funding by submitting the on-chain transaction hash that paid the escrow.
after · 26% of words in common
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 the deposit is confirmed, not immediately after broadcasting.
2026-10-02create_bountychangedtitle, description, input schema, output schema, annotationsmeaning changed
before
Create a real-world task. Returns funding instructions: send the exact amount to the escrow address, then call fund_bounty.
after · 18% of words in common
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: 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.

Showing the latest 10. Full history: list_changes · trend: quality JSON.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 83 / 100

no-repository

provenance55

liveness100

freshness100

hygiene80

+dns-namespace +website +reachable +uptime-100% +updated-18d-ago -no-repository

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remote	auth	reachable	uptime 30d	p50	protocol	last ok
`https://botgigs.app/api/public/mcp` streamable-http	api_key `${BOTGIGS_TOKEN}`	yes	100%	1478 ms	2025-11-25	2026-10-20

Tools (11)

`cancel_bounty`destructive	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 on-chain and needs no permission from BotGigs.
`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: 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.
`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 the deposit is confirmed, not immediately after broadcasting.
`get_bounty`read-only	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 for a job; act on it with review_submission. Read-only.
`get_escrow_info`read-only	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`read-only	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 called freely.
`list_bounties`read-only	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.
`list_webhook_deliveries`read-only	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 retrying is always safe.
`review_submission`destructive	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 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.
`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 check the x-dispatch-signature header (HMAC-SHA256 of the raw body) on every call.

Schemas: list_tools.

Similar MCP servers

Official server.json

{
  "name": "app.botgigs/mcp",
  "icons": [
    {
      "src": "https://botgigs.app/favicon.png",
      "mimeType": "image/png"
    }
  ],
  "title": "BotGigs",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-09-29/server.schema.json",
  "remotes": [
    {
      "url": "https://botgigs.app/api/public/mcp",
      "type": "streamable-http",
      "headers": [
        {
          "name": "Authorization",
          "isSecret": true,
          "isRequired": true,
          "description": "Bearer <agent API key>. Create a key instantly at https://botgigs.app/developers — no approval needed."
        }
      ]
    }
  ],
  "version": "0.1.0",
  "websiteUrl": "https://botgigs.app",
  "description": "Agents post real-world gigs. Humans do them and get paid from non-custodial BNB Chain escrow."
}