Mmcp.market

ReviewGuard MCP server

by eclipsesource.com·com.eclipsesource/review-guard·v0.3.0

Safety boundary for agent written GitHub PR reviews: pending and invisible, submitting is opt-in

A85/100grade A
What users say
No reviews yet
Be the first
Safety scan
A85/100

full report

Adoption
Growing

4 stars40 downloads/wk

Reviews

Write one

Nobody has reviewed ReviewGuard yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

ReviewGuard tools (7, 3 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • add_review_comments

    Add one or more comments to the authenticated user's pending review. Creates the pending review if it does not already exist. The review is NOT submitted.

  • delete_pending_reviewwrite action

    Delete the authenticated user's pending (draft) review. This removes the review and all its draft comments permanently.

  • get_pr_review_context

    Get the pull request author/message plus all submitted PR discussion context: review summaries, inline review threads with resolved state and reactions, and general PR comments.

  • list_pending_review

    List the authenticated user's current pending (draft) review on a pull request, including all current pending review comments. Returns null if there is no pending review.

  • modify_review_commentwrite action

    Update or delete one comment from the authenticated user's pending review. This cannot modify submitted review comments.

  • resolve_review_thread

    Resolve one of YOUR OWN review threads that is now addressed (e.g. a prior

  • submitwrite action

    Submit the authenticated user's pending review, turning the draft comments into a real, posted review.

Public scan report

scanner v0.1.9 · 2026-09-23 · same rubric, same numbers if you re-run it

no findings
  • Code scan8 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 5 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10
Overall 85/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

What the publisher says

From the ReviewGuard repository's README, as published. We do not edit it. Read it on GitHub

ReviewGuard MCP

MCP server (review-guard-mcp) that lets AI agents work on GitHub PR reviews behind a safety boundary. The server holds the write-enabled GitHub token and exposes only review operations, so the agent never sees the token. What those operations are allowed to do is fixed at server start, not negotiable by the agent.

Why

A write-enabled GitHub token is needed to create review comments, but giving that token directly to an agent risks accidental or prompt-injected actions: submitting approvals, requesting changes, closing other people's review threads, or touching unrelated repositories. This server sits in between and narrows the token down to exactly the review capabilities you opt into.

Modes

The server supports two modes of use:

Pending mode (default)

The agent reads PR discussion context and builds a pending (draft) review. Nothing it writes is visible to anyone else until a human opens the PR, inspects the draft comments, and submits the review themselves. Submission is structurally unreachable: the submit tool is not even registered, and the underlying client refuses every submit action.

Use this when an agent assists a human reviewer, for example in IDE setups (Claude Code, Codex, Theia) where the agent drafts inline comments and the human stays the reviewer of record.

Submit mode (opt-in, --allow-submit)

Started with --allow-submit, the server additionally registers a submit tool so the agent can post the review itself. Guardrails stay in place:

  • The allowed review actions are restricted to the set you list (for example comment-only, with no approvals).
  • Every submitted review starts with a fixed, server-configured disclaimer the agent cannot change or remove.
  • Optionally, --allow-resolve lets the agent resolve its own review threads (never anyone else's), and --repo/--pr pin the server to a single pull request.

Use this for unattended, autonomous review bots, for example a watcher that reviews every PR where a review is requested from the bot account and posts a real (comment-only) review.

Installation

Requires Node.js >= 22.

Install globally (makes review-guard-mcp available in PATH):

npm install -g @eclipsesource/review-guard-mcp

Or pin to a specific version:

npm install -g @eclipsesource/review-guard-mcp@<version>

The server is also listed in the MCP Registry as com.eclipsesource/review-guard, so clients that browse the registry can find and install it from there. The entry is metadata only, there is no hosted instance to connect to: it describes the npm package above, which your client installs and runs locally in the default pending mode.

From source

Requires npm >= 12 and a Node version supported by it (see CONTRIBUTING.md):

git clone https://github.com/eclipsesource/review-guard.git
cd review-guard
npm ci
npm run build
npm link          # creates a global symlink to the binary

Tools

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Install directly

Runs npx -y @eclipsesource/review-guard-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add review-guard -- npx -y @eclipsesource/review-guard-mcp
Add to Cursor

ReviewGuard: common questions

Is ReviewGuard MCP server safe?
Yes, by our scan: it is graded A (85/100). Read the ReviewGuard safety report
How do I install ReviewGuard?
It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
Does ReviewGuard need an API key?
Yes. The registry entry asks for GITHUB_TOKEN.
Is ReviewGuard maintained?
The last commit was 6 days ago (2026-09-18). The latest release is v0.3.0.
What can I use instead of ReviewGuard?
Servers from other publishers that do the same job: GitHub MCP server, uploads.sh MCP server and Agent Harnesses MCP server. Compare all ReviewGuard alternatives.

Alternatives to ReviewGuard

Same job from other publishers: the closest match first, then the best rated.

All ReviewGuard alternatives →
  • GitHub
    Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
    A
  • uploads.sh
    Host files from coding agents; stage on a branch and attach to GitHub PRs.
    A
  • Agent Harnesses
    Agent-harness picks, decision guides, and setup templates; live GitHub/HN discovery.
    A
  • Graphql Enhanced
    GraphQL gateway for LLMs. Handles huge GitHub GraphQL & @neo4j/graphql schemas without crashing
    A
  • theabbie
    Live info about theabbie (Abhishek Chaudhary) from theabbie.github.io/about.json
    A

More from eclipsesource.com →