{"slug": "why-single-region-uptime-monitors-wake-you-up-at-3-am-and-how-we-built-a-two-a-2", "title": "Why single-region uptime monitors wake you up at 3 AM — and how we built a two-region monitor with a read-only OAuth 2.1 MCP server", "summary": "Beamfar built a website uptime monitor that requires confirmation from two regions before firing an alert, avoiding the false 3 AM pages caused by transient BGP, packet-loss and resolver issues seen from a single probe datacenter. The service also snapshots DNS records, TLS certificates, redirects and SEO headers, and pins changes from the prior hour next to each incident timeline. It exposes the data through a read-only MCP server at api.beamfar.com/mcp using OAuth 2.1 with PKCE, registered in the Official MCP Registry as com.beamfar/website-monitoring, with install paths for Claude Code, Gemini CLI and Codex CLI.", "body_md": "If you have ever used a basic single-location uptime checker, you know the feeling: your phone buzzes at 03:14 with `CRITICAL: example.com is DOWN`, you jump out of bed, open the URL on your laptop, and it loads in 180 ms. Two minutes later: `RESOLVED`.\n\nThe internet between one probe datacenter and your origin has brief BGP reconvergences, packet loss spikes, and transient resolver timeouts every week. A single failed HTTP request from one datacenter is a **local network observation**, not proof that your website is down for users.\n\nWhen designing [Beamfar](https://beamfar.com/?utm_source=devto&utm_medium=article&utm_campaign=two_region_mcp), we made two-region confirmation the core rule across every plan — including the €0 Free tier:\n\n`verifying` instead of firing an alert immediately.\nKnowing a site returned `502` or timed out is only half the story. Almost every production outage is preceded by a change:\n\nBeamfar stores snapshots of DNS records, TLS certificates, final redirect URLs, and SEO headers (`noindex`, `robots.txt`, canonicals), and accepts optional deploy markers from our [GitHub Action](https://github.com/marketplace/actions/beamfar-deploy-marker) or official [WordPress plugin](https://wordpress.org/plugins/beamfar-monitoring/). When an incident opens, anything that changed in the previous hour is pinned right beside the incident timeline.\n\nOnce your monitoring data includes incidents, pre-incident diffs, SSL/domain expiry dates, and security findings, the next obvious workflow is asking your AI coding assistant inside the terminal or IDE:\n\n```\nWhich sites had incidents in the last 7 days, and what changed right before each one?\n```\n\nInstead of making users copy-paste API keys into plaintext configs (or worse, granting write tokens), we exposed a **read-only MCP server** at `https://api.beamfar.com/mcp` using **OAuth 2.1 + PKCE** (registered in the Official MCP Registry as `com.beamfar/website-monitoring`):\n\n```\n# Claude Code\nclaude plugin marketplace add Beamfar/integrations\nclaude plugin install beamfar@beamfar\n\n# Google Gemini CLI\ngemini extensions install https://github.com/Beamfar/integrations\n\n# OpenAI Codex CLI\ncodex mcp add beamfar --url https://api.beamfar.com/mcp\ncodex mcp login beamfar\n```\n\n", "url": "https://wpnews.pro/news/why-single-region-uptime-monitors-wake-you-up-at-3-am-and-how-we-built-a-two-a-2", "canonical_source": "https://dev.to/rares_corches_0967e149126/why-single-region-uptime-monitors-wake-you-up-at-3-am-and-how-we-built-a-two-region-monitor-with-1nmc", "published_at": "2026-11-22 14:08:56+00:00", "updated_at": "2026-11-22 14:13:14.044056+00:00", "lang": "en", "topics": ["ai-agents", "agent-protocols", "developer-tools", "ai-tools"], "entities": ["Beamfar", "Claude Code", "Google Gemini CLI", "OpenAI Codex CLI", "Official MCP Registry", "GitHub", "WordPress"], "also_reported_by": [], "takeaway": "Beamfar's read-only MCP server at api.beamfar.com/mcp uses OAuth 2.1 with PKCE so AI coding assistants can query incidents and pre-incident diffs without users pasting API keys or granting write tokens.", "recommendation": null, "alternates": {"html": "https://wpnews.pro/news/why-single-region-uptime-monitors-wake-you-up-at-3-am-and-how-we-built-a-two-a-2", "markdown": "https://wpnews.pro/news/why-single-region-uptime-monitors-wake-you-up-at-3-am-and-how-we-built-a-two-a-2.md", "text": "https://wpnews.pro/news/why-single-region-uptime-monitors-wake-you-up-at-3-am-and-how-we-built-a-two-a-2.txt", "jsonld": "https://wpnews.pro/news/why-single-region-uptime-monitors-wake-you-up-at-3-am-and-how-we-built-a-two-a-2.jsonld"}}