UptimeRobot
- Free allowance
- Free, USD 0/month: 50 monitors at a 5-minute monitoring interval, HTTP, port and ping monitors, basic status pages, only 5 integrations and no login seats; no credit card required
- Verdict
- caveatusable, with a named limit or an unprobed read path
- Cost
- free tier
- Identity
- emailno card, phone unknown
- Binding limit
- request-rate5-minute monitoring interval; 10 API requests per minute on the free plan
- Evidence
- documented25 sources; a first-party page was read and the sentence quoted
- Freshness
- stale on 2026-12-03checked 2026-11-02 (live); stale on 2026-12-03
| Free tier | Free, USD 0/month: 50 monitors at a 5-minute monitoring interval, HTTP, port and ping monitors, basic status pages, only 5 integrations and no login seats; no credit card required unit objects; metered on object-count; The unit counted is the monitor. The pricing page's feature list for Free also names keyword, API, UDP, DNS and location-specific monitoring, while its own answer on Free against Solo says Solo adds API, multi-location, slow-response, UDP and DNS monitoring; only HTTP, port and ping monitors, 5-minute intervals and basic status pages are taken as the free set. Monthly e-mail reports are sent for the first 3 months only. |
|---|---|
| Price | none stated |
| Limits | |
| Binding | request-rate The 5-minute interval sets the detection delay of every monitor and the API answers 10 requests a minute; both bind before 50 monitors are used. |
| Identity | email The sign-up page offers Google, GitHub or an e-mail address, and the pricing page states no credit card is required for Free; the mobile-app page states that registration needs just an e-mail address. A no-registration flow creates a free monitor from an e-mail address confirmed with one click. A phone number is not asked for at registration: it is registered afterwards as an SMS and voice-call alert contact, which needs purchased credits. |
| Egress | not applicable: an outbound checker; monitor data is read back through the API at 10 requests per minute on the free plan |
| Per-object cap | not applicable: a monitor checks a target; nothing is stored per object |
| Retention | 3 months of monitor logs on the free plan, against 12 months on Solo and 24 months on Team and Scale |
| Interface | rest REST API v3 at https://api.uptimerobot.com/v3 with a main or monitor-specific API key, the legacy API still documented, and a remote streamable-HTTP MCP server at https://mcp.uptimerobot.com/mcp that takes OAuth or an API key as a Bearer token and shares the REST API's request quota, with tool calls limited to 10 per minute on the free plan. The v3 host answered 401 to /v3/monitors without a key. A separate no-registration endpoint creates one free 5-minute HTTPS monitor from an e-mail address after a proof-of-work challenge and the owner's one-click confirmation. endpoint: https://api.uptimerobot.com/v3 |
| Tooling | any HTTP client with an API key, the MCP server for agent clients, and the Zapier integration |
| Composes with | Keeps up to 50 endpoints of free hosting under a 5-minute external check, which also keeps an idle-sleeping free web service awake. |
| Reliability | no throttle, ban or data loss is stated on the pages read beyond the 3-month log retention |
| Notes | 50 monitors at a 5-minute interval, against 10 monitors at a 3-minute interval on Better Stack's free plan: more targets, slower detection. |
| Evidence note | documented Every limit is quoted from a first-party page, and the API host answered 401 without a key. No account was opened; an authenticated API call from a free account would move it to measured. |
| Parsed numbers |
|
Evidence 25
| date | source | what it proved |
|---|---|---|
| 2026-10-30 | uptimerobot.com/pricing/ | the free plan needs no credit card |
| 2026-10-30 | uptimerobot.com/pricing/ | the free plan checks every 5 minutes |
| 2026-10-30 | uptimerobot.com/pricing/ | the free plan has HTTP, port and ping monitors |
| 2026-10-30 | uptimerobot.com/pricing/ | Free has 5-minute intervals and basic status pages |
| 2026-10-30 | uptimerobot.com/pricing/ | the free plan allows only 5 integrations |
| 2026-10-30 | uptimerobot.com/pricing/ | the free plan has no login seats |
| 2026-10-30 | uptimerobot.com/pricing/ | monitor logs are kept 3 months on Free, 12 on Solo and 24 on Team and Scale |
| 2026-10-30 | uptimerobot.com/llms.txt | the free plan has 50 monitors with no credit card |
| 2026-10-30 | uptimerobot.com/llms.txt | the API allows 10 requests per minute on the free plan |
| 2026-10-30 | uptimerobot.com/llms.txt | the v3 REST API base URL |
| 2026-10-30 | uptimerobot.com/llms.txt | an MCP server is offered |
| 2026-10-30 | uptimerobot.com/llms.txt | a free 5-minute HTTPS monitor can be made with only an e-mail address and no registration |
| 2026-10-30 | dashboard.uptimerobot.com/sign-up | the sign-up page offers Google, GitHub or e-mail |
| 2026-10-31 | probe: https://api.uptimerobot.com/v3/monitors | the v3 API host answers 401 without a key |
| 2026-11-01 | uptimerobot.com/mobile-app/ | registration needs just an e-mail address, on the free plan as on the others |
| 2026-11-01 | github.com/uptimerobot/ai/blob/main/README.md | MCP tool calls are limited to 10 per minute on the free plan |
| 2026-11-01 | help.uptimerobot.com/en/articles/11360953-uptimerobot-person | a phone number is registered as an SMS and voice-call alert contact, which needs credits |
| 2026-11-01 | help.uptimerobot.com/en/articles/11361302-uptimerobot-sms-vo | SMS and voice calls on the Free plan need purchased credits |
| 2026-11-01 | uptimerobot.com/ai-agent-monitoring/ | a free account is created from a site URL and an e-mail address with one click of confirmation |
| 2026-11-01 | help.uptimerobot.com/en/articles/12928342-uptimerobot-mcp-in | the MCP server is at https://mcp.uptimerobot.com/mcp |
| 2026-11-01 | help.uptimerobot.com/en/articles/12928342-uptimerobot-mcp-in | the MCP server authenticates through OAuth |
| 2026-11-01 | help.uptimerobot.com/en/articles/12928342-uptimerobot-mcp-in | an API key is the alternative to OAuth for the MCP server |
| 2026-11-01 | help.uptimerobot.com/en/articles/12928342-uptimerobot-mcp-in | MCP tool calls share the REST API's request quota |
| 2026-11-01 | github.com/uptimerobot/ai/blob/main/AGENTS.md | the MCP server uses the streamable HTTP transport |
| 2026-11-01 | help.uptimerobot.com/en/articles/12928342-uptimerobot-mcp-in | UptimeRobot's MCP server is a remote HTTP server |