quick-monitor-setup

Quick monitor setup (no account, email-only)

No MCP preflight needed. Unlike the other UptimeRobot skills, this one does NOT use the uptimerobot:* MCP tools and does NOT require the user to authenticate. It is the path for when the user has no UptimeRobot account or API key. If the user IS already connected via the MCP server, prefer create-http-monitor instead.

Use this when a user says something like "monitor my site and email me if it goes down" but has no UptimeRobot account or API key. You (the agent) do steps 1-4; the site owner does step 5 from their inbox. The result is the standard free plan: 50 monitors, 5-minute checks, free forever, no credit card.

The only thing the owner must provide is the email where down and up alerts go. Use an inbox they actually check.

Base URL

https://api.uptimerobot.com

Step 1: Request a proof-of-work challenge

GET /agentic/agent-monitor/challenge?email=<owner-email>&url=<site>

• url: the website to monitor. A bare domain works (www.example.com); https:// is assumed if you omit the scheme, so example.com is treated as https://example.com. Give an explicit http:// only if you specifically need plain HTTP.
• Returns: { "nonce": "<hex>", "timestamp": <ms>, "difficulty": <bits>, "signature": "<hex>" }.
• Read difficulty from the response. Never hardcode it.

Step 2: Solve the proof of work

Find a counter such that SHA-256("<nonce>|<counter>") has at least difficulty leading zero bits (pipe-separated, no spaces).

import hashlib
counter = 0
while True:
    h = hashlib.sha256(f"{nonce}|{counter}".encode()).digest()
    zeros = 0
    for b in h:
        if b == 0:
            zeros += 8
        else:
            zeros += 8 - b.bit_length()
            break
    if zeros >= difficulty:
        break
    counter += 1

Step 3: Submit the monitor request

POST /agentic/agent-monitor
Content-Type: application/json

{
  "email": "<owner-email>",
  "url": "<same url you sent in step 1>",
  "nonce": "<from challenge>",
  "timestamp": <from challenge>,
  "counter": <your solution>,
  "signature": "<from challenge>"
}