goodbotbadbot

The MCP server behind goodbotbad.bot, where the crowd rules AI transcripts good bot or bad bot.

该来源不提供完整文件导出（国内平台多为平台内托管），仅存元数据与原链

模型生成摘要（rules/v1 · 2026-09-27 16:56）：The MCP server behind goodbotbad
这是模型对公开材料的总结，不是官方声明，请以原链内容为准。

接入信息

传输形态: http
鉴权方式: 鉴权未知
端点: https://goodbotbadbot.run.tools

鉴权方式未标注，请核对官方文档后再接入——不要直接使用以下片段

{
  "mcpServers": {
    "goodbotbadbot": {
      "url": "https://goodbotbadbot.run.tools"
    }
  }
}

能力清单

工具	说明
submit_transcript	Submit an AI prompt and the response it produced to goodbotbad.bot, where people vote good bot or bad bot on it. NOTHING IS PUBLISHED BY THIS CALL. It creates a draft and returns a URL; a human has to open that URL and confirm before anything becomes visible, and you should show them the URL. There is deliberately no note parameter — the note is the human's account of why the exchange is worth posting, they write it on that page, and it is not something to compose for them. Secrets and API keys are detected and the submission is refused outright. Personal data — an email address, a phone number, a home directory path — is redacted before storing and named in the reply; show your human what was removed along with the URL. Quote the prompt verbatim if you can; if the real input was too large or is not recoverable, describe it in `objective` instead and say so. If the transcript is larger than 65536 bytes, send `manifest` INSTEAD of `turns` — a role, a byte count and a short label per turn, and no bodies — and the server will ask your human which passages to send. Do not send the bodies and let the server reject them: that has already disclosed them. To submit a repair for a failure already on the site, pass its id as `fixes` — a fix is a rewritten prompt and the better response it produced, so its `verdict` is `good`, and it waits on two people rather than one: a moderator screens it, and whoever posted the failure decides whether it repairs it. If the reply asks for token usage, it is asking your human and not you — they read it off their own client, which you cannot see. Put what they say in `inputResponses.usage` and send the whole call again with the `requestState`; it attaches to the draft that already exists rather than making a second one. Never supply a figure of your own, and skipping is a fine answer.
complete_pair	goodbotbad.bot pairs transcripts: two posts on one subject where exactly one thing differed and the outcomes were opposite. Call this with no arguments to be handed an unpaired post's prompt to run yourself. Call it with `id` and the response you got to stage the other half. NOTHING IS PUBLISHED — staging creates a draft and a pair candidate, and both a human and a moderator have to agree before either appears.
search_posts	Search goodbotbad.bot for transcripts people have already ruled on. Useful before submitting — a failure that is already in the archive should be voted on rather than posted again. Returns ids, titles, verdicts and vote counts.
get_post	Fetch one post from goodbotbad.bot by its id: the full transcript, the submitter's note, the verdict and the vote counts. Use it to see exactly what was submitted before offering the other half of a pair, or to quote it back to your human.

纠错与举报（发现条目失效、署名有误或涉及侵权？）

提交举报 / 纠错

侵权举报经核验成立后，我们会即时下线该条目并删除已存的内容副本。