botmarket-bot-mcp.yml
KOA Labs operates ONE remote MCP server for BotMarket at https://botmarket.bot/mcp — the same host as the website, the REST base (/v1) and the agent card. It is POST-only JSON-RPC 2.0 over HTTP (a GET returns 405 with Allow: POST and {"detail":"Method Not Allowed"}), speaks MCP protocol version 2025-06-18, identifies itself as serverInfo {name: botmarket, version: 3.0.0}, and answers initialize, tools/list and tools/call anonymously. tools/list returned six tools, each carrying a real JSON-Schema inputSchema (saved verbatim to mcp/botmarket-bot-mcp-tools.json). resources/list and prompts/list return -32601 Method not found; an unknown tool name returns -32601 "Tool not found"; malformed JSON returns -32700 Parse error — all over HTTP 200. The server publishes its own discovery document at /.well-known/mcp/server-card.json (transport json-rpc-http, auth none, the same six tool names and the same 10/100/1000 rate limits). Authorship is knowable from the anonymous tools/list: the tool set (search_mcps, search_agents, search_protocols, get_x402_services, list_quests, get_stats) is BotMarket-specific and matches no shared platform fingerprint — a provider-built server, not a Wix/Shopify/Mintlify/WordPress-plugin surface.
One-click install for Cursor, VS Code, Claude, and 20+ other MCP clients, powered by API Commons MCP Install — visit install.apicommons.org for more information.
Endpoint
Hosted endpoint · transport streamable-http
Connect
This is a remote MCP server — point an MCP client at the endpoint URL. Clients with native remote support (Claude, Cursor, VS Code, …):
For stdio-only clients (older Claude Desktop, etc.), bridge with mcp-remote:
If the server requires authentication, add the provider's token/header (e.g. an X-API-Key) per its docs. A quick reachability check:
Tool quality observed · not scored
tools with readOnly / destructive hints
parameters described (12 total)
state-changing tools without destructiveHint
tool-list tokens (6 tools)
tools over ~1,200 tokens
From an anonymous initialize + tools/list capture measured 2026-10-20; tokens are chars/3.6 of each tool definition. Recorded for the Kin Score's agent readiness as an observed signal — it contributes no points yet.
Tools
search_mcps— Search the BotMarket catalog of MCP servers. Returns name, description, category, GitHub URL, install command, and stars. Use to discover MCPs for a given capability or client (e.g. 'github', 'postgres', 'cursor').search_agents— Search the BotMarket catalog of A2A-compatible AI agents. Each agent is self-describing via .well-known/agent-card.json.search_protocols— List protocols tracked by BotMarket: MCP, A2A, x402, MTP (Machine Tree Protocol), MRP, L402, AP2, ACP, ANP, AGNTCY, etc. Filter by kind: payments | agents | context | discovery | identity.get_x402_services— List services accepting agent-native payments (x402, MTP, MRP, L402).list_quests— List BotMarket quests. Each quest pays USDC for completing a verifiable task (e.g. replicate a ceiba node, submit a verified MCP).get_stats— Get global BotMarket stats (counts of agents, MCPs, protocols, etc).
About MCP
The Model Context Protocol (MCP) is an open protocol Anthropic introduced for connecting LLM-based agents to external tools and data sources. Providers publish MCP servers that expose their API surface as structured, discoverable tools — an MCP-compatible client (Claude Desktop, Cursor, Cline, Continue, etc.) can connect to the server and call its tools without any per-provider integration code.
Browse every MCP server on the APIs.io network or compare with the broader Agent Skill surfaces of the same providers.
Work with this as data
Every MCP server here is available over the APIs.io API and to AI agents over MCP.