Reviso MCP Server

by reviso-si Your server? Claim it

answering

Reviso is answering right now. Last checked 1 min ago.

Publish agent output for human review; collect comments; agents read them back in-session.

Uptime history 6 days of history

6 days agonow

100.0%

Uptime 24h

92 of 92 checks

—

Tools

hidden behind auth

374 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

Nothing serious here today

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

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add reviso --transport http https://reviso.work/mcp

Settings → Connectors → Add custom connector, then paste this address

https://reviso.work/mcp

~/.codex/config.toml

[mcp_servers.reviso]
url = "https://reviso.work/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "reviso": {
      "url": "https://reviso.work/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "reviso": {
      "type": "http",
      "url": "https://reviso.work/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

URL	Transport	State	Latency	Checked
https://reviso.work/mcp	streamable-http	sign-in	315 ms	1 min ago

Alternatives to Reviso

same job, measured the same way

Derive

by derive

Publish agent output to permanent versioned URLs, read review comments back, and revise.

answering

Shareout

by shareout

Publish HTML pages, collect review comments, and revise at the same link.

answering

mdreview

by ranawaqas-ai

Human-in-the-loop document review: an agent pushes a draft, a person comments, the agent revises.

answering

Melt Peer Review

by meltstudio

Send AI-made document changes for human review, then read the decisions back.

answering

Instadash

by instadash

Live data grids for AI agents. Push structured data; humans review, agents read back via MCP.

answering

Pump Up

by pumpup

Human-in-the-loop control panel for AI agents: start runs, review them, answer their requests.

answering

Taste

by humantaste

Expert review for AI agents. On-chain proof of human review.

20 tools answering

Super Artifacts

by super-artifacts

Publish live pages from any agent, collect what visitors submit, and read it back.

answering

Reviso — questions

Answers built from our own checks of this server.

Why is there no tool list for Reviso?

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 Reviso working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 374 ms. The bar chart above shows every period we have measured.

How do I connect Reviso?

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 Reviso?

No API key is involved. Reviso 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 Reviso?

It answers our handshake in 374 ms on average, which is faster than 35% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.