Uptime.com logoMCP server · Engineering and operations

Uptime.com MCP server

Uptime.com in any MCP client, through Memtro: Uptime.com does not publish this server. Memtro's Uptime.com connector reads Uptime.com through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

Uptime.com website and service monitoring: checks with their type, address, up or down state, interval, response time and tags, a check's uptime and response-time statistics, outages and alerts by check and date, status pages with their components and incidents, and SLA reports; when you ask, can pause or resume a check, ignore or un-ignore an alert, tag a check, create an HTTP check, delete a check, post or update a status page incident or maintenance notice (optionally notifying subscribers), delete an incident, set a component's status and cancel a maintenance window.

Reads

  • uptimecom_checksMonitoring checks: name, type (HTTP, DNS, SSL_CERT, HEARTBEAT…), address, up or down, paused, in maintenance, interval, last response time…
  • uptimecom_checkOne check in detail: address, type, state, interval, locations, expected status or text, thresholds, SLAs, notes, tags and contact groups.
  • uptimecom_check_statsA check's uptime and response-time statistics over a date range (default the last 7 days): totals for the period and the figures per day.
  • uptimecom_outagesOutages (a check down from enough locations to alert), newest first or oldest first, with when they started and resolved, duration…
  • uptimecom_alertsAlerts (each change of a check's state to down or back up), newest first or oldest first, with the locations and the error each saw.
  • uptimecom_status_pagesStatus pages with name, type (public, public SLA, internal), visibility, slug and public address; with status_page_id…
  • uptimecom_incidentsIncidents and maintenance windows on a status page, newest first, with state, start and end, affected components and the latest updates.
  • uptimecom_sla_reportsSLA reports: without report_id, the reports set up (name, checks and tags covered); with report_id…

Acts, when you ask

These change something in Uptime.com. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

  • uptimecom_pause_checkPauses an Uptime.com check: it stops monitoring and alerting until resumed.
  • uptimecom_resume_checkResumes a paused Uptime.com check, so it monitors and alerts its contacts again.
  • uptimecom_toggle_alert_ignoreFlips an Uptime.com alert between ignored and counted (ignored alerts are left out of uptime and SLA figures).
  • uptimecom_add_check_tagsAdds tags to an Uptime.com check (existing tags are kept).
  • uptimecom_create_http_checkCreates an HTTP(S) check in Uptime.com that requests the address every interval minutes and alerts the named contact groups when it fails…
  • uptimecom_delete_checkPermanently deletes an Uptime.com check with its history, statistics and alerts.
  • uptimecom_post_incidentPosts an incident or a scheduled maintenance notice on an Uptime.com status page, visible to everyone who can see the page (the public…
  • uptimecom_post_incident_updateAdds an update to a status page incident in Uptime.com, visible on the page; resolve_incident true also resolves it.
  • uptimecom_delete_incidentPermanently deletes an incident or maintenance notice from an Uptime.com status page, with its updates; it disappears from the page's history.
  • uptimecom_set_component_statusSets a status page component's status in Uptime.com (operational, degraded performance, partial or major outage, under maintenance)…
  • uptimecom_cancel_maintenanceCancels one scheduled maintenance occurrence in Uptime.com, so its checks are monitored and alert as normal during that window.

Connect it

First connect Uptime.com on Dashboard → Connections, then add Memtro to your client once. The Uptime.com tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Pi

One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Uptime.com connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

  • › Which checks went down this week, and for how long?
  • › What was the API check's uptime over the last 30 days?
  • › Which checks are paused right now?
  • › Which incidents are open on the public status page?
  • › Pause the staging check while we deploy.

Questions

Is this an official Uptime.com MCP server?
No. It is Memtro's MCP server with Memtro's Uptime.com connector behind it: the connector reads Uptime.com through its API with the credentials you connect on Dashboard → Connections, and Uptime.com publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?
Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in Uptime.com?
Only when you ask, and only what it has been granted: pause a check; resume a paused check; ignore or un-ignore an alert; add tags to a check; create an HTTP(S) check; delete a check; post a status page incident or maintenance notice; post an update to a status page incident; delete a status page incident; set a status page component's status; cancel a scheduled maintenance window. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
Which clients work?
Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Engineering and operations

Where agents remember your company

Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.

7-day free trial · card on file, nothing charged until it ends · cancel any time