Repose MCP Server

by vncntknl Your server? Claim it

answering

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

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

Uptime history 50 days of history · worst day 92%

50 days agonow

100.0%

Uptime 24h

91 of 91 checks

—

Tools

hidden behind auth

515 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

Nothing serious here today

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add repose --transport http https://repose.sh/api/mcp

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

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

{
  "servers": {
    "repose": {
      "type": "http",
      "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

URL	Transport	State	Latency	Checked
https://repose.sh/api/mcp	streamable-http	sign-in	333 ms	11 min ago

Alternatives to Repose

same job, measured the same way

Drumbeats Io

by drumbeats-io

Manage Drumbeats cron, heartbeat and uptime monitors, report job runs and handle incidents.

141 installs/wk answering

Uptimy

by upti

Uptime monitoring from your assistant: see what's down, run incidents, set up monitors and reports.

answering

SutramX

by sutramx

SutramX uptime monitoring: monitors, check results, incidents, status pages and uptime/SLO reports.

56 installs/wk local only

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.

69 tools answering

Sitegoalie

by sitegoalie

Monitor and maintain client WordPress sites: updates, uptime, PHP errors, performance and reports.

answering

Suped DMARC

by suped-com

DMARC monitoring, SPF/DKIM diagnostics, reports, domains and MSP client management with Suped.

answering

Ink MCP

by ml

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

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: 100.0% 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 91 of 91 checks got a reply (100.0%), average response time 515 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 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 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 515 ms on average, which is faster than 23% 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.