Labsco
instana logo

UptimeMonitoring

from instana

Agent-native uptime monitoring by Monitive. Create, inspect, and assert monitor health in one sentence. Free 50-monitor tier.

🔥🔥🔥✓ VerifiedFreeAdvanced setup
#email#git#monitoring

Use UptimeMonitoring through MCP

What is MCP

Model Context Protocol (MCP) lets AI agents interact with external tools. UptimeMonitoring’s MCP server lets any compatible agent create, inspect, and manage monitors using natural language.

Available tools

Tool Description Read-only list_monitors List all monitors with current status Yes get_monitor Get monitor details + recent evidence Yes create_monitor Create a new monitor No update_monitor Update monitor configuration No delete_monitor Delete a monitor No (destructive) list_incidents Query incidents with filtering Yes assert_monitor_healthy Check if monitor is healthy (for deploy gates) Yes get_account_status Usage against caps Yes

Tool annotations

Tool title readOnlyHint destructiveHint idempotentHint openWorldHint list_monitors ”List Monitors” true false false true get_monitor ”Get Monitor” true false false true list_incidents ”List Incidents” true false false true assert_monitor_healthy ”Assert Monitor Healthy” true false false true get_account_status ”Get Account Status” true false false true create_monitor ”Create Monitor” false true false true update_monitor ”Update Monitor” false true false true delete_monitor ”Delete Monitor” false true true true

openWorldHint: true reflects that all tools make external API calls. idempotentHint: true is set only on delete_monitor — repeating the call after the monitor is gone produces the same result.

Auth model

The MCP endpoint accepts Bearer credentials: API keys, session tokens, and OAuth access tokens. Which credential you configure depends on the host.

OAuth-based connector hosts such as Claude.ai, Claude Desktop, and ChatGPT should use the OAuth flow when prompted. Config-file and API clients such as Claude Code, Cursor, and the OpenAI API can pass an OAuth access token or a custom Authorization header when the host supports custom headers.

OAuth 2.1 discovery endpoints are published at https://api.uptimemonitoring.com/.well-known/oauth-authorization-server (authorization server metadata) and https://api.uptimemonitoring.com/.well-known/oauth-protected-resource/mcp (protected resource metadata for the MCP endpoint).

For API-key setups, use the same key as the REST API:


Authorization: Bearer umk_live_...

Create a dedicated key labeled mcp for API-key based agent setups.

Example


User:

Create a monitor for https://example.com/healthz

and tell me whether it is healthy right now.

Agent:

I'll create the monitor and check its status.

Tool: create_monitor

Result: Monitor created (id: 1287, name: "example-healthz")

Tool: assert_monitor_healthy

Result: Healthy — EU, 200, ttfb 184ms

Discovery

UptimeMonitoring’s MCP server is listed in the Official MCP Registry under com.uptimemonitoring/mcp. MCP-aware tools that auto-discover servers from the registry can install it without any manual configuration; the registry entry carries the canonical transport, endpoint, and auth metadata.

Host compatibility

Manually maintained pre-release — open an issue if your host should be listed.

Host Transport Auth Status Claude.ai Remote MCP connector OAuth ✅ Claude Desktop Remote MCP connector OAuth ✅ Claude Code Remote MCP HTTP OAuth / Bearer header ✅ ChatGPT Custom MCP connector OAuth ✅ Cursor MCP config OAuth / Bearer header ✅ OpenAI API Responses MCP OAuth token / custom headers ✅

Last verified: 2026-05-26.

Listed in registries

  • ⏳ GitHub MCP Registry — submission pending 2026-05-19 (#26)

  • ⏳ Official MCP Registry — server.json shipped 2026-05-19 (#25), external submission PR pending

Support

Questions or issues with the MCP server? Email [email protected] .