mcpbeat Sign in

Repose MCP Server

answering

Repose is answering right now. Last checked 2 min ago.

Uptime monitoring that doesn't cry wolf: manage monitors, read incidents, record deploys.

Uptime history 54 hours of history · worst hour 25%
54 hours agonow
96.7%
Uptime 24h
88 of 91 checks
Tools
hidden behind auth
471 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Repose does not always answer

Over the last week it answered 94.1% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

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 2 min ago.

run in your terminal
claude mcp add repose --transport http https://repose.sh/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "repose": {
      "url": "https://repose.sh/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.repose]
url = "https://repose.sh/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "repose": {
      "url": "https://repose.sh/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "repose": {
      "url": "https://repose.sh/api/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://repose.sh/api/mcp streamable-http sign-in 305 ms 2 min ago

Alternatives to Repose

same job, measured the same way
YoPingMe uptime monitoring
by yoping

Website uptime monitoring: live status, uptime reports, incidents, response times, failed checks

answering
Hyperping
by hyperping

Uptime, API and server monitoring with outages, reporting, on-call and status pages.

26 tools answering
Ink MCP
by ml

Deploy and manage applications, databases, domains, and git repos

answering
PlatformIO
by powerdragonfire

PlatformIO for AI agents: build, flash, serial monitor, tests, crash decoding, size reports.

local only
Carrierscore
by carrierscore

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

8 tools answering
Ironscales
by wyre-ai

MCP server for Ironscales phishing incident management — incidents, mailboxes, and reporting.

local only
Ironscales
by wyre-technology

MCP server for Ironscales phishing incident management — incidents, mailboxes, and reporting.

local only
PingZen Uptime Monitoring
by pingzen

Uptime monitoring with 127 tools across 23 protocols. Tag filtering + Code Mode.

answering

Repose — questions

Answers built from our own checks of this server.

Why is there no tool list for Repose?
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: 96.7% of checks in the last 24 hours got a reply.
Is Repose working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 88 of 91 checks got a reply (96.7%), average response time 471 ms. The bar chart above shows every period we have measured.
How do I connect Repose?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path 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 Repose?
No API key is involved. Repose 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 Repose?
It answers our handshake in 471 ms on average, which is faster than 33% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.