Uptimemonitoring

com.uptimemonitoringPublished by uptimemonitoring.comOfficial publisherv1.0.2Updated Oct 27, 2026

Agent-native uptime monitoring. Create, inspect, and assert monitor health. Free 50-monitor tier.

VerifiedStreamable HTTPWeb executableCloud & InfrastructureSecurity & Monitoring

Overview

AI-generated overview

Remote MCP server for UptimeMonitoring that lets an assistant create, inspect and assert the health of uptime monitors.

What you can do
  • Create, list, test and delete uptime monitors
  • Inspect monitor status and assert whether a monitor is healthy
  • Manage monitors in natural language from MCP clients such as Claude Code or Cursor
  • Use the same monitors alongside cURL, Node.js, Python, GitHub Actions and webhook integrations
When to use it
Useful when you want an assistant to set up or check website and endpoint uptime monitors, or to verify monitor health as part of a deployment or debugging conversation, without leaving the chat.
Requirements
Remote streamable HTTP endpoint at api.uptimemonitoring.com. Authentication is required: OAuth 2.1 (recommended) or a Bearer API key sent in the Authorization header, generated in the UptimeMonitoring dashboard. Network access to the service.
Before you install
The API key is a secret sent in the Authorization header; keep it out of version control and never hardcode it. The server can create and delete monitors, so assistant actions change your monitoring configuration. Webhook signing secrets are also sensitive. A free tier covers 50 monitors.

Installation

In SourceWeft

  1. Open Uptimemonitoring in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.uptimemonitoring%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "uptimemonitoring": {
      "type": "http",
      "url": "https://api.uptimemonitoring.com/mcp"
    }
  }
}

README

UptimeMonitoring Examples

Copy-paste-runnable examples for every UptimeMonitoring integration.

Integrations

IntegrationPathDescription
cURLcurl/Create, list, test, and delete monitors from the command line
Node.jsnode/Same lifecycle using Node 20+ native fetch, no dependencies
Pythonpython/Same lifecycle using requests
GitHub Actionsgithub-actions/Post-deploy health gate with uptimemonitoring/assert-healthy
MCP — Claude Codemcp/claude-code/Manage monitors with natural language in Claude Code
MCP — Cursormcp/cursor/Manage monitors with natural language in Cursor
Webhookswebhooks/Push notifications when a monitor goes down, recovers, or flaps

Placeholder convention

All examples use placeholders — replace them with your own values before running:

PlaceholderReplace with
UPTIMEMONITORING_API_KEYYour API key — set as an environment variable, never hardcode it
umk_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxYour actual API key from Settings → API Keys
123Your monitor's numeric ID (visible in the dashboard URL)
whs_live_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxThe HMAC signing secret returned when you set a webhook

Never commit a real key to version control.

Coming in Phase 2

  • terraform/ — provision and manage monitors as infrastructure
  • kubernetes/ — liveness/readiness gate via assert-healthy in a pod lifecycle hook
  • pagerduty-integration/ — route monitor alerts to PagerDuty incidents

Source: README.md at commit 23dc481

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.2LatestSep 16, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts