Review Mcp

io.github.HectorGuerillaPublished by GitHub account HectorGuerillav0.1.0Updated Oct 28, 2026

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

The publisher's own server: Review Expert

VerifiedStreamable HTTPWeb executableDeveloper ToolsAI & ML

Overview

AI-generated overview

Remote MCP server that runs an adversarial multi-model code review on a diff, module, or spec plus implementation and returns a structured pass/fail verdict.

What you can do
  • Submit code for review: send a diff, a module, or a spec together with its implementation to a panel of models and detectors.
  • Get a structured verdict: receive a pass/fail result with each issue's type, severity, location, explanation, and suggested fix.
  • Cross-check your own output: the review is framed as adversarial and multi-model so a single model's blind spots are not the only check.
When to use it
Useful when an assistant writes or changes code and you want an independent, structured review before accepting it, especially for diffs or spec-versus-implementation checks where a second opinion matters.
Requirements
A remote streamable HTTP endpoint; no local package, environment variables, or headers are declared. The service is paid via x402, so a payment-capable client or wallet setup is implied.
Before you install
The service is described as paid via x402, so calls may cost money and require a payment-capable client. Code, diffs, and specs you submit are sent to a third-party hosted service and to multiple models; avoid sending secrets or proprietary code you cannot share.

Installation

In SourceWeft

  1. Open Review Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.HectorGuerilla%2Freview-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "review": {
      "type": "http",
      "url": "https://review-mcp-production.up.railway.app/mcp"
    }
  }
}

Tools

1

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.

Parametersdepthcontextpayloadrequiredlanguagerequired

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Review integrations