Reviewmetric

io.github.vktr93Published by GitHub account vktr93v1.0.6Updated Oct 24, 2026

An MCP server connecting Claude to the Review Metric 15-agent scientific peer review pipeline.

VerifiedSTDIODesktop onlyKnowledge & MemoryAI & ML

Overview

AI-generated overview

Lets an assistant submit local .docx manuscripts to the Review Metric multi-agent peer review pipeline and return a quality score.

What you can do
This MCP server connects an assistant to the Review Metric scientific peer review service. It can read .docx manuscripts from the local machine and submit them to a 15-agent pipeline that analyzes methodological flaws, novelty, and literature alignment. Results include a 0-100 quality score intended to gauge readiness for journal submission.
When to use it
Useful for researchers, academics, and scientists who want an assistant to run a manuscript through an automated peer review panel without pasting long documents into chat. It fits pre-submission checks and early feedback on a draft.
Requirements
Runs locally as a PyPI package (reviewmetric-mcp) launched via uvx, so Python tooling is needed. Requires a Review Metric API key supplied through the REVIEWMETRIC_API_KEY environment variable, obtained from the Review Metric web dashboard. Desktop-only; network access to the Review Metric service is implied.
Before you install
The server reads local .docx manuscript files and sends their contents to a third-party service, so unpublished work leaves the machine. It requires the secret REVIEWMETRIC_API_KEY, which should be kept out of shared configuration files. The README claims zero data retention and that research is never used for AI training, but this is the provider's own statement and should be verified.

Installation

In SourceWeft

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

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

ReviewMetric MCP Server

Know what reviewers will say before you submit — from inside Claude.
Then fix the text in one go, and see where your work sits on the map of science.

ReviewMetric is a pre-submission review service for researchers. This MCP server lets Claude send a local .docx manuscript to ReviewMetric's panel of specialist AI referees, bring the report back into your chat, prepare the text fixes Claude can apply to your file, and explore the ReviewMetric Atlas: landmark discoveries, their Nobel Prizes and the frontiers research groups are pushing now.

What the panel checks

RefereeWhat it looks at
Novelty & positioningYour claims against the closest published, peer-reviewed work (retrieved from OpenAlex and ReviewMetric's vetted library), plus related papers you may have missed
Claims & evidenceWhether each main claim is supported by your results; numbers that disagree between abstract, results and tables
Methods & reproducibilityDesign, controls, statistics, and a field-appropriate reproducibility checklist
Citation integrityWhether cited papers support the sentences they are attached to; retracted, uncited or missing references
FiguresCaptions, legibility, units, and agreement with the text
ClarityTitle, abstract, structure, language, terminology
Handling editorReadiness recommendation, prioritised revisions and a referee-style report

Every issue points to a location in your manuscript. Scores come from fixed rubrics, not from a single AI guess.

Installation (Claude Desktop)

  1. Create an API key at https://www.reviewmetric.it.com/developers
  2. Add this to claude_desktop_config.json:
json
{  "mcpServers": {    "review-metric": {      "command": "uvx",      "args": ["reviewmetric-mcp"],      "env": { "REVIEWMETRIC_API_KEY": "rvk_live_..." }    }  }}
  1. Ask Claude: "Review my manuscript at /Users/me/papers/draft.docx with ReviewMetric."

Commands

Ask "What can ReviewMetric do?" (the help_me command) for the full list inside Claude.

CommandWhat it doesCost
help_meEverything ReviewMetric can do in Claude, with examplesFree
submit_manuscript(file_path)Sends the .docx to the referees; returns a Run ID1 RM token
check_analysis_status(run_id)Progress; when done, the report, its place on the Atlas and the text fixes availableFree
get_report_json(run_id)The complete report as JSONFree
list_my_reviews(limit)Your reviews with scores and Run IDsFree
get_text_fixes(run_id)Preview of the fixes that need no new experiment; the exact edits once preparedFree
prepare_text_fixes(run_id)Prepares the edits, which Claude can then apply to your manuscript1 RM token
search_atlas(query, field, limit)Finds discoveries and frontiers on the AtlasFree
list_frontiers()The frontiers, what they build on, who is pushing themFree
place_on_atlas(run_id)Where your manuscript sits, the landmarks it cites, the frontier aheadFree
atlas_whats_new()This week's additions to the AtlasFree
trace_path(from, to)The chain of discoveries linking two starsFree
unlock_atlas_sources(confirm)The paper and research group behind every star, for 30 days1 RM token
account_status()RM tokens left, Atlas access, pricesFree

Spending tokens. RM tokens are ReviewMetric's one currency (1 for $9, 3 for $25, 10 for $70; your first is free). Claude never unlocks the Atlas sources on its own: it tells you the cost and waits for your explicit yes in the chat.

A review usually takes about 5 minutes. If the file cannot be reviewed (unreadable, too short, not a manuscript), the RM token is returned automatically.

Try asking

  • "Review my manuscript at ~/papers/draft.docx and tell me what to fix first."
  • "Prepare the text fixes of my last review and apply them to the draft."
  • "Where does my manuscript sit on the Atlas, and which frontier is ahead of it?"
  • "Who is pushing room-temperature superconductivity right now?"
  • "Trace the path from the double helix to AlphaFold."

Data

Manuscripts are processed by ReviewMetric's API and the AI providers it uses under their paid API terms (no training on your data). See the ReviewMetric website for the current data-retention policy.

Source: README.md at commit b7167c6

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.6LatestSep 16, 2026

Score

50% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts