hetrixmcp
Related Servers
Alternatives to hetrixmcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceEnables AI assistants to interact with Uptime Agent monitoring system to check uptime status, manage incidents, create new monitors, and analyze downtime through natural conversation.71MIT
- AlicenseAqualityAmaintenanceUptime monitoring your AI agent can set up: create HTTP, SSL, ping, TCP and DNS monitors checked from multiple regions, run checks on demand, read and acknowledge incidents, manage cron heartbeats, maintenance windows and status page updates.49824 npmMIT
- AlicenseAqualityBmaintenanceEnables managing Uptime Kuma monitoring through natural language, including creating, editing, pausing, and deleting monitors, plus retrieving heartbeats, status, metrics, notifications, and status pages.12MIT
- AlicenseCqualityAmaintenanceEnables interaction with the Atera RMM/PSA API v3 for managing tickets, customers, contacts, agents, alerts, contracts, knowledge base, billing, custom fields, network devices, departments, and rates. It exposes 47 tools with read-only defaults and optional write or delete access.3251 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to interact with Healthchecks.io, allowing users to list, create, update, pause, resume, and delete checks, as well as view ping history and integrations.49 npm1MIT

watchcron-mcpofficial
AlicenseAqualityCmaintenanceEnables AI agents to manage cron job and scheduled task monitoring through the WatchCron API. Supports listing, creating, updating, pausing, and deleting monitors, retrieving ping URLs and ping/incident history, and listing notification channels.9317 npmMIT
TDQS
Scored across 20 tools
Each tool targets a distinct resource and action, with clear separation between list/get/update/create/delete operations. Even similar-looking tools like list_blacklists and list_blacklist_monitors are differentiated by their descriptions (RBL definitions vs monitor instances). No two tools perform the same function.
All tools follow a consistent verb_noun pattern using snake_case. Verbs (list, get, update, create, delete, add, remove) clearly indicate the operation, and nouns precisely denote the resource. There are no mixed conventions or ambiguous names.
At 20 tools, the server is slightly above the typical 3-15 well-scoped range but still reasonable given the breadth of HetrixTools' monitoring domains (uptime, blacklist, status pages, agents, maintenance, etc.). Each tool serves a distinct purpose and the count is not overwhelming.
The server is heavily read-focused, with no create/update/delete operations for the core resources (uptime monitors and blacklist monitors). While scheduled maintenance and server agents have some write support, the missing CRUD for monitors and status pages leaves significant gaps for management workflows.