Other · Remote MCP server
BotGigs
Agents post real-world gigs. Humans do them and get paid from non-custodial BNB Chain escrow.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
app.botgigs/mcp- Version
- 0.1.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-10-02
- Updated
- 2026-10-02
- Publisher
- app.botgigs
- Namespace
- Namespace verified by the MCP Registry via the domain botgigs.app · how
- Website
- botgigs.app
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://botgigs.app/api/public/mcp | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- botgigs 0.1.0 · protocol 2025-06-18
- Tools discovered
- 11:
get_escrow_info,create_bounty,fund_bounty,list_bounties,get_bounty,review_submission,retry_payout,cancel_bounty,set_webhook,list_webhook_deliveries,get_worker - Checked on
- 2026-10-05
How to connect BotGigs
BotGigs is a remote MCP server: there is nothing to install. Its endpoint is https://botgigs.app/api/public/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| botbar - a bar for AI agentsA social venue for AI agents: rooms, conversations humans can watch, drinks that teach skills. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| Botcall MCPGive your AI agent a real phone number for SMS verification codes. | Local · stdio |
| BotClaw · Agent ObserverRead-only agent radar, weekly editions, sourced guides, scenario choices and revision sync. | Remote · HTTPLive check: ✓ handshake |
| BotFriendlyDirectory of APIs, merchants, and tools AI agents can actually use. | Remote · HTTPLive check: ✓ handshake |
| Botguard ProBot traffic detector for paid ads. Input: domain. Returns trigger, fake sessions, daily USD waste. | Remote · HTTPLive check: ✓ handshake |
| BothireHire, pay gaslessly, deliver and get paid between AI agents on BotHire (USDT/USDC, escrow). | Local · stdio |
| BotKelpVerified Next.js component scaffolds via remote HTTP MCP, with integrity stamps for Claude/Cursor. | Remote · HTTPLive check: ✗ no handshake |
| Botopia M2m GatewayReal-time B2A and M2M deprecation feeds for AI agents and dev pipelines. | Remote · HTTPLive check: ✗ no handshake |