Can the agent check a specific endpoint's uptime and recent downtime?

Yes. uptime_get_monitor_details returns the monitor's current status, uptime_get_monitor_availability gives its uptime statistics, and uptime_get_monitor_response_times shows latency. For background jobs, the heartbeat tools confirm whether they are still reporting in.

Why is Better Stack second and not first for uptime monitoring?

Because the top pick spans broader telemetry beyond uptime. For the narrow up-or-down question, though, Better Stack is the most direct tool: its monitors, availability stats, and incident tools target exactly that, which is why it ranks second of four here.

Better Stack for uptime monitoring

Pick 2 of 4 for uptime monitoringOfficialBetter Stack

When something goes down, the first questions are whether it is really down, since when, and what is on fire. Better Stack's official server answers exactly those, which makes it the second of four picks for uptime monitoring and the most direct one for the job. Its tools are built around monitors and incidents, so an agent can check endpoint health and read the latest downtime without a human bouncing between status pages.

It sits second rather than first only because the field's top pick spans broader telemetry, but for the literal uptime question Better Stack is the on-target tool. Monitors, availability stats, response times, and the incident trail are all directly addressable here.

How Better Stack fits

This is the use case the toolset was made for. uptime_list_monitors enumerates what is watched, uptime_get_monitor_details returns a single monitor's config and current status, and uptime_get_monitor_availability and uptime_get_monitor_response_times give the uptime percentage and latency behind a spike. Heartbeat tools (uptime_list_heartbeats, uptime_get_heartbeat_details, uptime_get_heartbeat_availability) confirm that cron-style background jobs are still checking in. When a check shows a real outage, uptime_create_incident opens the record and uptime_list_incidents, uptime_get_incident_details, uptime_get_incident_timeline, and uptime_get_incident_comments let the agent narrate what happened.

The siblings approach health from other angles. Sentry tells you about application errors rather than endpoint reachability, useful once you know the service is up but misbehaving. Datadog is the pick when you want uptime folded into a full metrics-and-traces platform. PagerDuty owns the paging side, getting the alert to a responder, more than the up-or-down check itself. For answering "is it up and what did the last downtime look like," Better Stack is the cleaner fit.

Tools you would use

Tool	What it does
uptime_list_monitors	Lists Uptime monitors, with filtering options.
uptime_get_monitor_details	Gets the configuration and status of a single monitor.
uptime_get_monitor_availability	Returns availability/uptime statistics for a monitor.
uptime_get_monitor_response_times	Returns response-time data for a monitor.
uptime_list_heartbeats	Lists heartbeat checks.
uptime_get_heartbeat_details	Gets the details of a single heartbeat.
uptime_get_heartbeat_availability	Returns availability statistics for a heartbeat.
uptime_create_incident	Creates a new incident.
uptime_list_incidents	Lists incidents, with filtering options.
uptime_get_incident_details	Gets the details of a single incident.

Full Better Stack setup and config →

FAQ

Can the agent check a specific endpoint's uptime and recent downtime?: Yes. uptime_get_monitor_details returns the monitor's current status, uptime_get_monitor_availability gives its uptime statistics, and uptime_get_monitor_response_times shows latency. For background jobs, the heartbeat tools confirm whether they are still reporting in.
Why is Better Stack second and not first for uptime monitoring?: Because the top pick spans broader telemetry beyond uptime. For the narrow up-or-down question, though, Better Stack is the most direct tool: its monitors, availability stats, and incident tools target exactly that, which is why it ranks second of four here.