Review uptime, SSL, pagespeed and heartbeat checks, alerts and maintenance windows; create checks.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
Scored across 21 tools
Tools are cleanly separated by resource (uptime, SSL, heartbeat, pagespeed, maintenance, contact groups) and action. The only ambiguity is between the three uptime history tools (get_uptime_history, get_uptime_periods, list_uptime_alerts), but descriptions clarify their distinct purposes. No tool overlaps with another.
Every tool follows a strict statuscake_{verb}_{resource} pattern with consistent verbs (list, get, create, update). Plural/singular distinctions are consistent (e.g., list_uptime_checks, get_uptime_check). No naming deviations.
At 21 tools, this is above the ideal range of 3-15 for a scoped server. The breadth of domains (uptime, SSL, pagespeed, heartbeat, maintenance, contacts) explains the count, but it still feels heavy. It is borderline but justified by domain coverage.
Uptime checks have read and update but no delete, and create is present. SSL, heartbeat, pagespeed, and maintenance windows lack update or delete operations, and update_ssl_check is missing. Contact groups are only listable, not creatable. Significant gaps in lifecycle operations for most resources.
Uptime monitoring: create and manage HTTP, API, SSL, ping, port and domain checks
Uptime checks for sites and APIs, status pages, cron heartbeats, Lighthouse and SEO audits.
Uptime checks, cron heartbeats, status pages and alerts, set up by your agent.
Check if any website is up (status, latency, redirects, security headers) and set uptime alerts.
Add one secure layer between your agents and this server.
