mcpbeat

Review MCP Server

io.github.HectorGuerilla/review-mcp
answering

Review MCP is answering right now. Last checked 14 min ago. It exposes 1 tools.

Multi-model code review: a panel of models + detectors return a pass/fail verdict. Paid via x402.

Uptime history 42 hours of history
42 hours agonow
100.0%
Uptime 24h
91 of 91 checks
1
Tools
read from the server
345 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 14 min ago.

run in your terminal
claude mcp add review-mcp --transport http https://review-mcp-production.up.railway.app/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "review-mcp": {
      "url": "https://review-mcp-production.up.railway.app/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.review-mcp]
url = "https://review-mcp-production.up.railway.app/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "review-mcp": {
      "url": "https://review-mcp-production.up.railway.app/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "review-mcp": {
      "url": "https://review-mcp-production.up.railway.app/mcp"
    }
  }
}

Available tools 1

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

review
review_code
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.

Endpoints

URLTransportStateLatencyChecked
https://review-mcp-production.up.railway.app/mcp streamable-http answering 333 ms 14 min ago

Review MCP — questions

Answers built from our own checks of this server.

What can Review MCP do?
It exposes 1 tools, read directly from the server on our last check. Among them: review_code. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Review MCP working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 345 ms. The bar chart above shows every period we have measured.
How do I connect Review MCP?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Review MCP need an API key?
No. Review MCP completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 1 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Review MCP?
It answers our handshake in 345 ms on average, which is faster than 41% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.