{"slug": "show-hn-an-uptime-monitor-with-an-mcp-server-create-monitors-by-asking-claude", "title": "Show HN: An uptime monitor with an MCP server, create monitors by asking Claude", "summary": "Monitive launched an API-first uptime monitoring service with an MCP server that lets developers and AI agents create monitors via curl, Claude prompts, or GitHub Actions. The platform offers 50 free monitors, evidence-rich incident data, and multiple alert channels including webhooks, browser push, RSS, and MCP pull.", "body_md": "By Monitive · 16 years in monitoring · 50 monitors free · GitHub login · no email · no card\n\n# API-first uptime monitoring for deploy pipelines, developers, and AI agents.\n\nCreate monitors with a curl call, an MCP prompt, or a GitHub Action.\n\n```\nclaude mcp add --transport http uptimemonitoring \\\n  https://api.uptimemonitoring.com/mcp\n```\n\nHave an API key? Add `--header \"Authorization: Bearer umk_live_...\"`\n\nto authorize via key.\n\n## Use the surface you already work in.\n\nSame backend. Same monitor state. Different ways to drive it.\n\nCreate and manage monitors from scripts, apps, or CI.\n\n```\ncurl -X POST https://api.uptimemonitoring.com/api/v1/monitors \\\n  -H \"Authorization: Bearer $UPTIMEMONITORING_API_KEY\" \\\n  -H \"Content-Type: application/json\" \\\n  -d '{\n    \"name\": \"api-prod\",\n    \"url\": \"https://api.example.com/healthz\",\n    \"type\": \"http\"\n  }'\n```\n\n## Built for your workflow\n\nPick the surface that fits how you ship.\n\n#### Fail deploys when your site is down\n\nUse a GitHub Action to assert your deploy is reachable from 22 probe locations before traffic switches over.\n\n#### Let your Claude agent monitor its own deployments\n\nAdd the UptimeMonitoring MCP server to Claude Code so your agent can create monitors, check status, and react to failures.\n\n#### Uptime monitoring from inside Cursor\n\nConfigure UptimeMonitoring as an MCP server in Cursor and manage monitors from the agent panel.\n\n#### Monitor any API with 50 free checks\n\nCreate monitors via the REST API with a single POST request — no dashboard required.\n\n## What happens when something breaks\n\nWe do not flip red on the first blip.\n\n### Create\n\nYou create a monitor through the API, MCP, or GitHub Action.\n\n### Test immediately\n\nWe run an immediate test check so typos and unreachable targets fail fast.\n\n### Check on schedule\n\nChecks are spread across the minute to keep load stable.\n\n### Re-check failures\n\nInfrastructure-class failures are confirmed from two additional regions before we flip state.\n\n### Deliver evidence\n\nWe store the incident with evidence and send it where you want it: webhook, browser push, RSS, or MCP pull.\n\n## Evidence, not just red dots\n\nSee what happened before the incident: DNS, TLS, timeout, 5xx, region, and timing breakdowns.\n\n- Last 20 checks included\n- Timing breakdowns per check\n- Region-aware evidence\n- Designed for debugging, not dashboards\n\n```\n{\n  \"id\": 194,\n  \"type\": \"down\",\n  \"monitor_id\": 1287,\n  \"started_at\": \"2026-04-18T05:38:52Z\",\n  \"resolved_at\": \"2026-04-18T05:45:44Z\",\n  \"evidence\": [\n    {\n      \"region\": \"US-W\",\n      \"timestamp\": \"2026-04-18T05:37:41Z\",\n      \"status_code\": 200,\n      \"dns_ms\": 6.8,\n      \"tls_ms\": 298,\n      \"connect_ms\": 149,\n      \"ttfb_ms\": 203\n    },\n    {\n      \"region\": \"US-W\",\n      \"timestamp\": \"2026-04-18T05:38:42Z\",\n      \"error_class\": \"dns\"\n    }\n  ]\n}\n```\n\n## Webhooks for systems. Push for humans. MCP for agents.\n\nNo inbox spam. No deliverability headaches. You choose the channel.\n\n#### Webhooks\n\nFor Slack, Twilio, Discord, ntfy, GitHub Actions, or your own router.\n\n```\nPUT /api/v1/monitors/1287/webhook\n{ \"url\": \"https://hooks.co/inc\" }\n```\n\n#### Browser push\n\nOne-click opt-in from the dashboard. Fastest human fallback.\n\n```\nEnable notifications\nChrome on macOS · Active\n```\n\n#### RSS / incident feed\n\nSubscribe from Slack, readers, or automation tools.\n\n```\nhttps://api.uptimemonitoring.com\n  /feed/{token}/rss\n```\n\n#### MCP pull\n\nAsk your agent for monitor state and recent incidents directly.\n\n```\nTool: list_incidents\nFilter: last 24h, status: open\nResult: 1 incident, myapp-healthz\n```\n\nBrowser push and email get muted by Do Not Disturb — exactly when an outage matters. Wire a webhook to Pushover (bypasses DND on iOS and Android) or ntfy for phone alerts the moment something breaks.\n\n[Reliable alerts guide →](/guides/reliable-alerts)\n\n## Validate the things that actually break\n\n#### HTTP / HTTPS\n\nStatus codes, body match, timing evidence\n\n#### Timing evidence\n\nDNS, connect, TLS, TTFB, download\n\n## Copy a working example\n\nStart from a real recipe, not a blank page.\n\n## Free plan\n\nEnough for real projects. Simple enough to remember.\n\n- Up to 50 monitors\n- Up to 100 during extended free tier (early users)\n- 60-second minimum interval\n- 22 global probe locations\n- 1 webhook per monitor\n- 10 API keys per account\n- 30-day incident retention\n- Full MCP access\n- Browser push + RSS incident feed\n- No email required\n- No credit card required\n\nPaid plans will add 30-second intervals, longer retention, and response-time threshold alerts.\n\n## Built by Monitive\n\nUptimeMonitoring.com is the API-first, headless sibling to Monitive Pro.\n\nMonitive has been operating monitoring infrastructure for 16 years. UptimeMonitoring.com takes that operational experience and applies it to a different job: deploy gates, API workflows, AI-agent tooling, and developer-first monitoring without email or dashboard sprawl.\n\n- 16 years in monitoring\n- 22 probe locations\n- Cross-region confirmation on failures\n- GitHub OAuth + API keys\n- Minimal data collection: GitHub identity only\n\n```\nAPI / MCP / GitHub Action\n          │\n          ▼\n   Go dispatcher + evidence\n          │\n          ▼\n   22-probe network\n          │\n          ▼\n webhooks / push / RSS / incidents\n```\n\n## FAQ\n\n## Is it really free?\n\nYes. Free plan: up to 50 monitors. Early users can go up to 100 during the extended free tier while paid plans are being finalized.\n\n## Do I need an email address?\n\nNo. Signup uses GitHub OAuth. Email is optional only if you want future pricing updates.\n\n## How do alerts work without email?\n\nWebhooks, browser push, RSS feeds, and MCP queries.\n\n## How do you avoid false positives?\n\nInfrastructure-class failures are re-checked across regions before state changes.\n\n## Can I monitor private IPs or internal services?\n\nNo. Private and reserved targets are blocked.", "url": "https://wpnews.pro/news/show-hn-an-uptime-monitor-with-an-mcp-server-create-monitors-by-asking-claude", "canonical_source": "https://uptimemonitoring.com/", "published_at": "2026-07-15 12:31:34+00:00", "updated_at": "2026-07-15 12:48:18.019500+00:00", "lang": "en", "topics": ["developer-tools", "ai-agents", "ai-tools"], "entities": ["Monitive", "Claude", "GitHub", "Cursor", "Slack", "Twilio", "Discord", "Pushover"], "alternates": {"html": "https://wpnews.pro/news/show-hn-an-uptime-monitor-with-an-mcp-server-create-monitors-by-asking-claude", "markdown": "https://wpnews.pro/news/show-hn-an-uptime-monitor-with-an-mcp-server-create-monitors-by-asking-claude.md", "text": "https://wpnews.pro/news/show-hn-an-uptime-monitor-with-an-mcp-server-create-monitors-by-asking-claude.txt", "jsonld": "https://wpnews.pro/news/show-hn-an-uptime-monitor-with-an-mcp-server-create-monitors-by-asking-claude.jsonld"}}