{"slug": "third-party-service-monitoring-is-now-in-the-api-mcp-and-cli", "title": "Third party service monitoring is now in the API, MCP and CLI.", "summary": "UptimeRobot added third party service monitoring to its API, MCP server and CLI, letting teams track outages at more than 6,000 cloud and SaaS providers from code, AI assistants or the terminal. The MCP server gains 10 new tools for third party services, and the API and CLI each get their own endpoints and commands to search providers, start or stop tracking them, filter incidents, check status and see who was alerted. UptimeRobot said the tracked providers do not count against a plan's monitors, and cited an AWS incident where it sent an alert 10 minutes before AWS acknowledged the issue.", "body_md": "We’re happy to announce that you can set up Third party service monitoring from the UptimeRobot API, MCP server and CLI too, and get alerted when a service your product depends on has an outage.\n\nAdd a provider from your deploy pipeline, ask your AI assistant whether Stripe had an incident last night, or check a provider’s status from your terminal.\n\n## What is Third party service monitoring?\n\nMost products depend on services they don’t run. Payments go through Stripe, files sit in AWS, and password reset emails go out through an email provider. When one of them has an incident, part of your product breaks with it.\n\n[Third party service monitoring](https://uptimerobot.com/third-party-monitoring/) has tracked those providers for you and alerted you when one of them has a problem.\n\nThird party service monitoring follows the status of more than 6,000 cloud and SaaS providers.\n\nYou choose the providers your product depends on and the components you actually use, and UptimeRobot alerts you through the notification channels you already have, like Slack, Microsoft Teams, PagerDuty, email or SMS, when their status changes.\n\nBesides official status updates, it also tracks reports from people using the service, which can give you an earlier signal. For example, during one AWS incident, we sent an alert 10 minutes before AWS acknowledged the issue.\n\nThese tracked providers don’t count against your monitors as each plan has a separate allowance for them: more on that below or [see all plans](https://uptimerobot.com/pricing/).\n\n## What can you do from the API, MCP and CLI?\n\nThe MCP server has 10 new tools for third party services, and the API and CLI have their own endpoints and commands for them. With any of the three, you can:\n\n- Search more than 6,000 providers and see which ones you already track.\n- Start tracking a provider, either all of it or only the components your product uses.\n- Decide which incidents reach you: all of them or only major ones, and whether you get follow-up updates on an incident you already know about.\n- Check a provider’s current status and go through its incident history, with the provider’s own updates word for word.\n- See who on your team was alerted about an incident, on which channel, and whether the alert got through.\n- Stop tracking a provider your product no longer uses.\n\n## API, MCP or CLI: which one is for you?\n\nAll three work with the same account and the same tracked providers.\n\n### API to keep your providers in sync with your code\n\nIf you manage monitoring as code, third party services can live there too. When a deploy adds a new integration, the same pipeline can add the provider to UptimeRobot, with the components you use and the alert contacts you want. When you remove the integration later, remove the provider as well and free up the slot for something else.\n\nThe endpoints and their fields are documented in the [UptimeRobot API reference](https://uptimerobot.com/api/v3/).\n\n### MCP to ask your AI assistant\n\nConnect the [UptimeRobot MCP server](https://uptimerobot.com/mcp/) to Claude, ChatGPT or another MCP client, and you can manage third party services just by asking. For example:\n\n- “Track Stripe, but only the API and webhooks.”\n- “Which of our providers had a major incident this week?”\n- “Show me the last AWS incident and who we alerted about it.”\n\nIt’s the quickest way to answer “is it us or them?” when something breaks, without leaving the chat you’re already in.\n\n### CLI for your terminal and scripts\n\nThe [UptimeRobot CLI](https://uptimerobot.com/cli/) now has commands for third party services.\n\nYou can search the catalog, start tracking a provider, check its status, and read its incidents and who was alerted, all from the shell you already have open. Add the –json flag to get JSON output, so you can feed a provider’s status straight into your own tooling.\n\nAlready using the CLI? Update it to get the new commands. The [README on GitHub](https://github.com/uptimerobot/uptimerobot-cli#readme) shows each one with an example.\n\n## Which providers should you track?\n\nMost teams remember their big providers and forget the email API that sends password resets, or the DNS host nobody has logged into for years.\n\nOur guide to [third-party services every SaaS should monitor](https://uptimerobot.com/knowledge-hub/monitoring/saas-third-party-monitoring/) groups common providers by what breaks when they go down.\n\nWe’re also working on a CLI command that goes through your project and suggests what to monitor, third party services included.\n\n## Which plans include Third party service monitoring?\n\nThird party service monitoring is included in every paid plan. Each plan comes with its own allowance of third party services, separate from your monitors, so tracking a provider never takes a slot away from your own websites and APIs.\n\n| Plan | Monitors | Third party services | \n|---|---|---|\n| Solo | 10 | 1 | \n| Solo | 50 | 5 | \n| Team | 100 | 20 | \n| Scale | 200 | 40 | \n| Scale | 500 | 100 | \n\nYou can search the full provider catalog on any paid plan. Your plan sets how many providers you track at once, whether you add them in the dashboard, through the API, MCP or the CLI.\n\nSee pricing for everything else each plan includes.\n\n## Add your providers today\n\nConnect the [UptimeRobot MCP server](https://uptimerobot.com/mcp/) to your AI assistant or update the [UptimeRobot CLI](https://uptimerobot.com/cli/), and add the providers your product depends on. The next time one of them has an incident, you’ll hear about it from us.\n\n- \nNo. Third party services have their own allowance on every paid plan, separate from your monitors.\n- \nAny MCP-compatible client. ChatGPT,[Claude.ai](http://Claude.ai) and Claude desktop connect through OAuth, so you sign in to UptimeRobot instead of pasting an API key.", "url": "https://wpnews.pro/news/third-party-service-monitoring-is-now-in-the-api-mcp-and-cli", "canonical_source": "https://uptimerobot.com/blog/third-party-monitoring-api-mcp-cli", "published_at": "2026-11-09 13:52:40+00:00", "updated_at": "2026-11-09 14:24:38.303742+00:00", "lang": "en", "topics": ["ai-tools", "ai-agents", "ai-products", "developer-tools", "agent-protocols"], "entities": ["UptimeRobot", "Stripe", "AWS", "Claude", "ChatGPT", "Slack", "Microsoft Teams", "PagerDuty"], "also_reported_by": [], "alternates": {"html": "https://wpnews.pro/news/third-party-service-monitoring-is-now-in-the-api-mcp-and-cli", "markdown": "https://wpnews.pro/news/third-party-service-monitoring-is-now-in-the-api-mcp-and-cli.md", "text": "https://wpnews.pro/news/third-party-service-monitoring-is-now-in-the-api-mcp-and-cli.txt", "jsonld": "https://wpnews.pro/news/third-party-service-monitoring-is-now-in-the-api-mcp-and-cli.jsonld"}}