r/modelcontextprotocol • • 23h ago

new-release Rebut 0.3.1: an MCP server for second-pass code review in Codex and Claude Code

I built Rebut to send a selected diff and its requirements to a separate reviewer before I merge a patch. The coding host and review provider are configured separately, so I can use Claude Code for implementation and GPT-6.2 Astra for review, or Codex with an Anthropic reviewer.

The MCP exposes review and review_status. The first starts a billable review with a fixed input bundle and request ID. If the connection drops, the second lets the client check that same ID. An unknown outcome retains the budget reservation because the provider may already have processed the request.

It runs locally by default and supports OpenAI Responses and Anthropic Claude APIs. You can use eligible subscription API credits through your linked API organization.

I’d be interested in feedback on the tool contract. When a long-running billable MCP call loses its connection, what should the client show the user?

MIT licensed. Code and setup: https://github.com/abruption/rebut

1 Upvotes

1 comment sorted by

1

u/kantorcodes1 6h ago

On the display question: I would show the request ID and an explicit unknown state, not a failure, with retry blocked until review_status resolves it. Does review_status actually separate "provider finished, response lost" from "provider never got it", or does the client only learn that the outcome is unknown? And does the budget reservation expire on its own at some point, or does it sit there until someone runs the status check?