Skip to main content
Glama
khrns-r

hetrixmcp

by khrns-r
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
HETRIXTOOLS_API_TOKENYesHetrixTools API token for authentication

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
extensions
{
  "io.modelcontextprotocol/ui": {}
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
get_account_limitsA

Get current HetrixTools account usage and limits.

Returns usage and limits for uptime monitors, blacklist monitors, sub-accounts, SMS credits, account credit, and API v1/v2 access.

list_contact_listsA

List contact lists configured on the account.

Each contact list includes id, name, default flag, and notification channel settings (email, phone_sms, telegram, slack, discord, webhook, and do-not-disturb settings).

list_blacklistsA

Get the list of blacklists (RBLs) checked by the HetrixTools platform.

Returns two arrays: ipv4 and domains, each containing entries with id, rbl name, and optional/ignored flags.

list_blacklist_monitorsA

List blacklist monitors with optional filters and pagination.

Returns a monitors array (id, name, type, target, rdns, report_id, status, contact_lists, listed array of {rbl, delist}, created_at, last_check) plus a meta object with pagination info.

get_blacklist_reportA

Get the blacklist report for a specific monitor.

Returns id, name, type, target, report_id, and a listed array describing which RBLs currently list the target.

list_uptime_monitorsA

List uptime monitors with optional filters and pagination.

Returns a monitors array with detailed info: id, name, type, target, resolve_address, port, keyword, category, timeout, check_frequency, uptime_status, monitor_status, uptime%, locations, ssl info, domain info, nameservers, etc.

get_uptime_reportA

Get the uptime report for a specific monitor.

Returns timezone, per-day data (uptime, response_time, optional hourly_stats), a summary object, and a history array.

list_downtimesA

List downtimes for a specific uptime monitor.

Returns a downtimes array (id, type, http_code, location, started_at, ended_at, duration) plus a meta object with pagination.

get_location_fail_logB

Get the fail log for a specific monitoring location of an uptime monitor.

Returns a fail_log array (id, type, http_code, started_at, ended_at, duration) plus a meta object with pagination.

list_warning_policiesB

List the warning policies configured for an uptime monitor.

update_warning_policiesB

Update the warning policies for an uptime monitor.

Sends a PUT request with the provided policies array.

list_status_pagesA

List all status pages configured on the account.

add_monitors_to_status_pageA

Add monitors to a status page.

Sends a POST request with the status page ID and monitor IDs to add.

remove_monitors_from_status_pageA

Remove monitors from a status page.

Sends a DELETE request with the status page ID and monitor IDs to remove.

list_scheduled_maintenanceA

List all scheduled maintenance windows.

create_scheduled_maintenanceA

Create a scheduled maintenance window.

Sends a POST request with the maintenance name, start/end dates, optional affected monitor IDs, and optional description.

delete_scheduled_maintenanceA

Delete a scheduled maintenance window by ID.

get_server_agentB

Get information for a specific server agent.

update_server_agentB

Update a server agent's configuration.

Sends a POST request with the provided settings dict.

delete_server_agentB

Delete a server agent by ID.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.6/5.0

Scored across 20 tools

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count4/5

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.

Completeness2/5

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.

Maintenance

ActivityStale
ResponsivenessNo issues

Resources