mcpbeat Sign in

Qu Review MCP Server

answering

Qu Review is answering right now. Last checked 9 min ago.

Independent second opinion on any AI answer: inaccuracies, gaps, and a scored report card.

Uptime history 25 days of history
25 days agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
210 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Qu Review every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

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

run in your terminal
claude mcp add review --transport http https://app.qureview.ai/mcp
Settings → Connectors → Add custom connector, then paste this address
https://app.qureview.ai/mcp
~/.codex/config.toml
[mcp_servers.review]
url = "https://app.qureview.ai/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "review": {
      "url": "https://app.qureview.ai/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "review": {
      "type": "http",
      "url": "https://app.qureview.ai/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://app.qureview.ai/mcp streamable-http sign-in 195 ms 9 min ago

Alternatives to Qu Review

same job, measured the same way
VulX Watch
by vulx

Independent security review for AI-built apps. Watch a GitHub repo. Never a patch.

answering
Ask Gemini
by lykhoyda

Bridge Claude with Gemini CLI for AI-to-AI collaboration, code review, and second opinions

1 223 installs/wk local only
Ask Codex
by lykhoyda

Bridge Claude with OpenAI Codex CLI for AI-to-AI collaboration, code review, and second opinions

128 installs/wk local only
Celmis
by constantinemakoid

Self-hosted code intelligence: cross-repo Q&A, dependency audits and PR review, over MCP

local only
Kebivo
by ocnai

Self-hosted inbox for questions your AI agents couldn't answer. Report knowledge gaps over MCP.

local only
Carrierscore
by carrierscore

FMCSA motor-carrier risk scores, monitoring, and carrier-selection evidence reports for AI agents.

8 tools answering
Revup
by revup

Create, customize, preview and report on promotions in your Revup account.

answering
Wizeb AI-Native Index
by wizeb

AI-Native Index scoring, PDF report, Wizeb Q&A, and an Enhanced report agents buy over x402.

10 tools answering

Qu Review — questions

Answers built from our own checks of this server.

Why is there no tool list for Qu Review?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Qu Review 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 210 ms. The bar chart above shows every period we have measured.
How do I connect Qu Review?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Qu Review?
No API key is involved. Qu Review answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Qu Review?
It answers our handshake in 210 ms on average, which is faster than 68% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.