mcpbeat Sign in

Rush MCP Server

answering

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

Hand Rush a task: an agent does the work in its own cloud sandbox and returns a PR, report or files.

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

Nothing serious here today

Today is the operative word: we check Rush 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 1 min ago.

run in your terminal
claude mcp add rush --transport http https://api.prix.dev/mcp
Settings → Connectors → Add custom connector, then paste this address
https://api.prix.dev/mcp
~/.codex/config.toml
[mcp_servers.rush]
url = "https://api.prix.dev/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "rush": {
      "url": "https://api.prix.dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "rush": {
      "type": "http",
      "url": "https://api.prix.dev/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://api.prix.dev/mcp streamable-http sign-in 636 ms 1 min ago

Alternatives to Rush

same job, measured the same way
S
Sandboxer
by sandboxer

Cloud Linux VMs for your agent: run code, Docker, files and HTTPS previews in a Sandboxer microVM.

local only
LatticeRun
by latticerun

Let your AI agents claim a task, work inside it and report back on your LatticeRun task tree.

answering
Unplain
by unplain

Your assistant writes the ebook or report; Unplain designs it and returns a publish-ready PDF.

answering
Prumo
by tomd4vs

Checks the context files a coding agent reads against the git index, and reports what drifted.

42 installs/wk local only
AgentSpace
by com-agentspace

Give your agent a persistent workspace: files, a code sandbox and a public URL to publish to.

answering
A
Awesome Report
by ks0430

Turn an agent's findings into a clean web page: tables, charts, diagrams, one shareable link.

answering
Malwagon
by malwagon

Submit files and URLs to a malware sandbox, poll scans, fetch reports, hashes and IOCs.

5 tools answering
I
Inventor Studio
by heavens-lava

Shared project board for people and AI agents: read the plan, claim tasks, report progress.

285 installs/wk local only

Rush — questions

Answers built from our own checks of this server.

Why is there no tool list for Rush?
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 Rush 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 983 ms. The bar chart above shows every period we have measured.
How do I connect Rush?
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 Rush?
No API key is involved. Rush 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 Rush?
It answers our handshake in 983 ms on average, which is faster than 6% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.