Free uptime monitoring: HTTP/TCP/TLS/DNS + MCP server checks, cron heartbeats, status pages, alerts.
Glama couldn't complete the latest health check. 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 12 tools
Each tool targets a distinct resource and action: monitors have create/get/list/update/delete, incidents have list/ack/note, plus status page and channel access are clearly separated. check_url is distinct as an on-demand probe versus create_monitor which is continuous monitoring. Descriptions clearly disambiguate overlapping actions like ack_incident vs add_incident_note.
All tool names follow a consistent verb_noun snake_case pattern: ack_, add_, check_, create_, delete_, get_, list_, update_. Verbs are predictable and the resource nouns (monitor, incident, account, status_page, channel) are consistent throughout. No stylistic deviations.
12 tools is well within the ideal 3-15 range and each tool earns its place. The set covers core monitoring operations (CRUD for monitors, incident handling, status page lookup, channel listing, account info) without unnecessary duplication. The extra check_url utility adds value without bloating the surface.
Monitor lifecycle is fully covered (create, read, list, update, delete) and incident workflows support listing, acknowledgement, and notes. Minor gaps exist: no single-incident detail endpoint, no channel/status page management (only read), and no explicit incident resolution tool, though incidents likely auto-resolve on recovery. These are workable via existing tools and the public API.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
check_url2 fields changedInput schema / properties / kindAdded value: +{
+ "description": "What to speak: plain HTTP (default) or an MCP initialize handshake",
+ "enum": [
+ "http",
+ "mcp"
+ ],
+ "type": "string"
+}Input schema / properties / url / descriptionPrevious value: -"Public http(s) URL to check, e.g. https://example.com"New value: +"Public http(s) URL to check, e.g. https://example.com — for kind=mcp the MCP endpoint URL, e.g. https://mcp.deepwiki.com/mcp"create_monitor2 fields changedInput schema / properties / kind / descriptionPrevious value: -"Monitor kind (default http)"New value: +"Monitor kind (default http; \"mcp\" monitors an MCP server via JSON-RPC initialize)"Input schema / properties / kind / enumPrevious value: -[
- "http",
- "tcp",
- "tls",
- "domain",
- "dns",
- "heartbeat"
-]New value: +[
+ "http",
+ "tcp",
+ "tls",
+ "domain",
+ "dns",
+ "heartbeat",
+ "mcp"
+]ack_incidentadd_incident_notecheck_urlcreate_monitordelete_monitorget_accountget_monitorget_status_pagelist_channelslist_incidentslist_monitorsupdate_monitorUptime monitoring and public status page: HTTP monitors, down/up alerts and incidents.
Uptime monitoring: create and manage HTTP, API, SSL, ping, port and domain checks
Uptime monitoring for developers — monitors, incidents, heartbeats and status pages
Uptime, API and server monitoring with outages, reporting, on-call and status pages.
Add one secure layer between your agents and this server.
