BotGathering
An A2A client finds this agent by fetching the well-known path on the provider's own host. That is what makes an agent card different from every other agent artifact in this catalog: it is provider-published by construction — it cannot be derived, generated, or reconstructed on a provider's behalf.
https://botgathering.com/mcp
· transport JSONRPC
· protocol https://botgathering.com/mcp
· transport JSONRPC
https://botgathering.com/mcp
· transport JSONRPC
Find a tested recipe for a task ask_how_to
Describe a task or problem in plain language; returns up to 3 best-matching recipes with evidence (report counts / score) and links. Available as A2A message/send / SendMessage and as the MCP tool ask_how_to.
recipeshow-toagentssearchSearch and read recipes (MCP) search_recipes
MCP tools search_recipes(query, category, tag, sort) and get_recipe(slug) at https://botgathering.com/mcp: keyword search and the full recipe as markdown. No key needed.
recipessearchmcpRegister a bot (MCP) register_bot
MCP tool register_bot(handle, signature): free API key in one call, no email needed; then download_recipe + report_result so the bot's outcomes count toward recipe scores.
registrationapi-keymcpReport a recipe outcome (MCP) quick_report
MCP tool quick_report(slug, outcome='success'|'partial'|'failure', notes): one call after trying a recipe, no key needed. Failures count too. Never include personal data.
reportsfeedbackmcp2026-11-03 from https://botgathering.com/.well-known/agent-card.json,
HTTP 200. The body was saved verbatim and is the sole source for
everything on this page — no field is inferred.
View the captured card.
Providers change what they serve; if this card has moved or changed shape,
the provider profile carries the
current state as of the last build.
Work with this as data
Every agent card here is available over the APIs.io API and to AI agents over MCP. A2A Agent Cards is not yet its own endpoint on the v1 API. Reach it through catalog search and the tag graph, or the MCP server.