review-mcp
Multi-model code review: a panel of models + detectors return a pass/fail verdict. Paid via x402.
Should I use this
Quality & Safety
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"review-mcp": {
"url": "https://review-mcp-production.up.railway.app/mcp"
}
}
}Remote endpoints
https://review-mcp-production.up.railway.app/mcpstreamable-httpWhat it can do
Tool inventory
Tools (1)
🟡review_code(payload, language, context, depth)
Adversarial multi-model code review. Submit a diff, a module, or a spec+implementation and get back a structured pass/fail verdict with each issue's type, severity, location, explanation, and suggested fix. Why call this instead of reviewing your own output: a single model shares its blind spots with itself. This routes your code through a panel of *different* models plus a set of deterministic detectors, catching what self-review misses — path/contract violations, module incoherence (dangling imports, broken cross-references), syntax and call-arity regressions in a diff's post-image, and 'prose instead of tool calls' (output that describes an action rather than emitting it). The panel adds semantic judgment on top and never overrides a deterministic finding. Call it before shipping or merging, as a second opinion on a risky change, or as a gate in an autonomous build loop. Choose depth='fast' (one model, low latency) or 'deep' (full panel, higher recall). Deep review audits files of any size in milestone chunks so every panel model contributes; the price (shown in the 402) and the payment window scale with file size. Per-call limit ~1,600 lines — larger inputs return 413, so split by file/module and call once per file. Paid per call via x402 (USDC on Base); the price is announced in the 402 response before any charge.
Input Schema
{
"type": "object",
"properties": {
"payload": {
"type": "string",
"description": "a unified diff, a complete module/file, or a spec plus its implementation (include enough context lines for diffs)."
},
"language": {
"type": "string",
"description": "primary language of the payload (e.g. \"typescript\", \"python\")."
},
"context": {
"type": "string",
"description": "optional spec/intent, related interfaces, constraints, or what the change should do."
},
"depth": {
"type": "string",
"enum": [
"fast",
"deep"
],
"description": "\"fast\" = single-model, low latency; \"deep\" = full panel, higher recall (default \"deep\")."
}
},
"required": [
"payload",
"language"
],
"additionalProperties": false,
"$schema": "http://json-schema.org/draft-07/schema#"
}Community
Evidence