mcpbeat Sign in

Cascade Scout MCP Server

answering

Cascade Scout is answering right now. Last checked 6 min ago.

Shared team record of decisions, changes and handoffs that every coding agent reads and writes.

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

Nothing serious here today

Today is the operative word: we check Cascade Scout 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 6 min ago.

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

Alternatives to Cascade Scout

same job, measured the same way
Joxo
by joxo

One shared project for a team's coding agents: decisions, a task board and handoffs.

answering
WitWiki
by witwiki

A shared team wiki your coding agents read and write — across every repo and every MCP client.

answering
Bilg
by bilgai

Shared memory for coding agents and their teams: docs, epics, tasks and decisions over MCP.

answering
Proof
by toremlabs

Govern your AI coding agent: frame the work, review the changes, keep a signed decision record.

57 installs/wk local only
LotsNotes
by lotsnotes

Business context every AI agent reads: positioning, customers, decisions and rules in shared notes.

answering
CogSession
by premanand8800

Session memory for AI coding agents: records decisions and dead ends, flags what went stale.

49 installs/wk local only
Elen
by learningnodes

Records coding-agent decisions with their limits and marks old ones superseded. Local SQLite.

73 installs/wk local only
Hunch
by davesheffer

Shared records for AI agents: engineering decisions, bug history, rules, and work state through MCP.

1 677 installs/wk local only

Cascade Scout — questions

Answers built from our own checks of this server.

Why is there no tool list for Cascade Scout?
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 Cascade Scout working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 28 of 28 checks got a reply (100.0%), average response time 312 ms. The bar chart above shows every period we have measured.
How do I connect Cascade Scout?
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 Cascade Scout?
No API key is involved. Cascade Scout 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 Cascade Scout?
It answers our handshake in 312 ms on average, which is faster than 46% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.