このMCPでできること
Creates and manages uptime monitors for HTTP, APIs, ping, ports, SSL certificates, and domain expiry, with incidents, notifications, and performance statistics.
機能
ツール
15
ツール
create_api_monitor
Create API monitor
Watch a JSON or REST endpoint where the response itself matters, not only that the host answered. Use it for health endpoints, webhooks and any API whose failure would be invisible to a plain page check. For an ordinary web page, create_http_monitor is lighter and enough.
外部アクセスあり
入力スキーマ
{'type': 'object', 'required': ['name', 'url'], 'properties': {'url': {'type': 'string', 'description': 'Full endpoint URL including scheme, for example https://api.example.com/v1/status.'}, 'name': {'type': 'string', 'maxLength': 50, 'description': 'Label shown in the dashboard and in alerts, up to 50 characters. Something recognisable months later beats the bare hostname.'}, 'isActive': {'type': 'boolean', 'description': 'Start monitoring immediately (default true)'}, 'frequency': {'type': 'integer', 'maximum': 1440, 'minimum': 1, 'description': 'Check frequency in minutes (1-1440, default 5)'}, 'requestTimeout': {'type': 'integer', 'maximum': 60, 'minimum': 1, 'description': 'Request timeout in seconds (1-60, default 30)'}}, 'additionalProperties': False}
出力スキーマ
{'type': 'object', 'required': ['id'], 'properties': {'id': {'type': 'integer', 'description': 'Monitor id, used by every other tool.'}, 'url': {'type': 'string'}, 'name': {'type': 'string'}, 'type': {'enum': ['PING', 'HTTP', 'API', 'SSL', 'DOMAIN', 'PORT'], 'type': 'string'}, 'isActive': {'type': 'boolean', 'description': 'False while the monitor is paused.'}, 'frequency': {'type': 'integer', 'description': 'Check interval in minutes.'}, 'statusSummary': {'type': 'string', 'description': 'Current state, for example GOOD or ERROR.'}}}
create_domain_monitor
Create domain expiry monitor
Watch a domain registration and report how long is left before it lapses, read from WHOIS. This catches the failure no uptime check can see: everything works perfectly right up to the day the domain expires. Distinct from create_ssl_monitor, which watches the certificate rather than the registration; the two expire on different dates and both are worth watching.
外部アクセスあり
入力スキーマ
{'type': 'object', 'required': ['name', 'url'], 'properties': {'url': {'type': 'string', 'description': 'Registrable domain, for example example.com. Use the registered domain rather than a subdomain: a subdomain has no registration date of its own.'}, 'name': {'type': 'string', 'maxLength': 50, 'description': 'Label shown in the dashboard and in alerts, up to 50 characters. Something recognisable months later beats the bare hostname.'}, 'isActive': {'type': 'boolean', 'description': 'Start monitoring immediately (default true)'}}, 'additionalProperties': False}
出力スキーマ
{'type': 'object', 'required': ['id'], 'properties': {'id': {'type': 'integer', 'description': 'Monitor id, used by every other tool.'}, 'url': {'type': 'string'}, 'name': {'type': 'string'}, 'type': {'enum': ['PING', 'HTTP', 'API', 'SSL', 'DOMAIN', 'PORT'], 'type': 'string'}, 'isActive': {'type': 'boolean', 'description': 'False while the monitor is paused.'}, 'frequency': {'type': 'integer', 'description': 'Check interval in minutes.'}, 'statusSummary': {'type': 'string', 'description': 'Current state, for example GOOD or ERROR.'}}}
create_http_monitor
Create HTTP monitor
Watch a web page or endpoint over HTTP/HTTPS and treat an unexpected status code, a timeout or a connection failure as downtime. This is the right type for anything a browser would open. Choose create_api_monitor instead when the response body matters as well as the status code. Checks run from probes in several countries. Call list_monitors first so you do not create a duplicate of an existing url.
外部アクセスあり
入力スキーマ
{'type': 'object', 'required': ['name', 'url'], 'properties': {'url': {'type': 'string', 'description': 'Full URL including scheme, for example https://example.com/health. A bare hostname is not accepted here - use create_ping_monitor for that.'}, 'name': {'type': 'string', 'maxLength': 50, 'description': 'Label shown in the dashboard and in alerts, up to 50 characters. Something recognisable months later beats the bare hostname.'}, 'isActive': {'type': 'boolean', 'description': 'Start monitoring immediately (default true)'}, 'frequency': {'type': 'integer', 'maximum': 1440, 'minimum': 1, 'description': 'Check frequency in minutes (1-1440, default 5)'}, 'requestTimeout': {'type': 'integer', 'maximum': 60, 'minimum': 1, 'description': 'Request timeout in seconds (1-60, default 30)'}}, 'additionalProperties': False}
出力スキーマ
{'type': 'object', 'required': ['id'], 'properties': {'id': {'type': 'integer', 'description': 'Monitor id, used by every other tool.'}, 'url': {'type': 'string'}, 'name': {'type': 'string'}, 'type': {'enum': ['PING', 'HTTP', 'API', 'SSL', 'DOMAIN', 'PORT'], 'type': 'string'}, 'isActive': {'type': 'boolean', 'description': 'False while the monitor is paused.'}, 'frequency': {'type': 'integer', 'description': 'Check interval in minutes.'}, 'statusSummary': {'type': 'string', 'description': 'Current state, for example GOOD or ERROR.'}}}
create_ping_monitor
Create ping monitor
Watch a host with ICMP ping: it answers whether the machine is reachable at all, and reports round-trip time and packet loss. Use it for servers, routers and anything with no web service on top. It says nothing about whether a site or service on that host is working - a box can ping perfectly while its web server is down. Some hosting providers block ICMP, in which case the monitor will read as down.
外部アクセスあり
入力スキーマ
{'type': 'object', 'required': ['name', 'url'], 'properties': {'url': {'type': 'string', 'description': 'Hostname or IP address, with no scheme and no port, for example example.com or 1.2.3.4.'}, 'name': {'type': 'string', 'maxLength': 50, 'description': 'Label shown in the dashboard and in alerts, up to 50 characters. Something recognisable months later beats the bare hostname.'}, 'isActive': {'type': 'boolean', 'description': 'Start monitoring immediately (default true)'}, 'frequency': {'type': 'integer', 'maximum': 1440, 'minimum': 1, 'description': 'Check frequency in minutes (1-1440, default 5)'}}, 'additionalProperties': False}
出力スキーマ
{'type': 'object', 'required': ['id'], 'properties': {'id': {'type': 'integer', 'description': 'Monitor id, used by every other tool.'}, 'url': {'type': 'string'}, 'name': {'type': 'string'}, 'type': {'enum': ['PING', 'HTTP', 'API', 'SSL', 'DOMAIN', 'PORT'], 'type': 'string'}, 'isActive': {'type': 'boolean', 'description': 'False while the monitor is paused.'}, 'frequency': {'type': 'integer', 'description': 'Check interval in minutes.'}, 'statusSummary': {'type': 'string', 'description': 'Current state, for example GOOD or ERROR.'}}}
create_port_monitor
Create port monitor
Watch one TCP or UDP port on a host and report it up only when the service behind it actually answers. This is the type for game servers, databases, mail and anything else that speaks its own protocol rather than HTTP - Minecraft, Rust, CS2, FiveM, Postgres, Redis, SMTP. The port must be given as part of the url. Set protocol to UDP for game servers; most of them do not answer on TCP at all.
外部アクセスあり
入力スキーマ
{'type': 'object', 'required': ['name', 'url'], 'properties': {'url': {'type': 'string', 'description': 'Host and port separated by a colon, for example example.com:443 or 1.2.3.4:25565. The port is required; without it the monitor cannot be created.'}, 'name': {'type': 'string', 'maxLength': 50, 'description': 'Label shown in the dashboard and in alerts, up to 50 characters. Something recognisable months later beats the bare hostname.'}, 'isActive': {'type': 'boolean', 'description': 'Start monitoring immediately (default true)'}, 'protocol': {'enum': ['TCP', 'UDP'], 'type': 'string', 'description': 'TCP is the default and fits most services. Use UDP for game servers and anything else that does not answer on TCP; on UDP the port counts as up only when the server actually replies.'}, 'frequency': {'type': 'integer', 'maximum': 1440, 'minimum': 1, 'description': 'Check frequency in minutes (1-1440, default 5)'}}, 'additionalProperties': False}
出力スキーマ
{'type': 'object', 'required': ['id'], 'properties': {'id': {'type': 'integer', 'description': 'Monitor id, used by every other tool.'}, 'url': {'type': 'string'}, 'name': {'type': 'string'}, 'type': {'enum': ['PING', 'HTTP', 'API', 'SSL', 'DOMAIN', 'PORT'], 'type': 'string'}, 'isActive': {'type': 'boolean', 'description': 'False while the monitor is paused.'}, 'frequency': {'type': 'integer', 'description': 'Check interval in minutes.'}, 'statusSummary': {'type': 'string', 'description': 'Current state, for example GOOD or ERROR.'}}}
create_ssl_monitor
Create SSL certificate monitor
Watch a TLS certificate: whether it is valid, who issued it, and how many days remain before it expires. This is about the certificate, not about the site being reachable - pair it with create_http_monitor when you want both. Note that such a monitor carries two independent states, one for reachability and one for expiry, so a certificate can be days from expiring while the check still reads up.
外部アクセスあり
入力スキーマ
{'type': 'object', 'required': ['name', 'url'], 'properties': {'url': {'type': 'string', 'description': 'Domain whose certificate to inspect, for example example.com. No scheme, no path.'}, 'name': {'type': 'string', 'maxLength': 50, 'description': 'Label shown in the dashboard and in alerts, up to 50 characters. Something recognisable months later beats the bare hostname.'}, 'isActive': {'type': 'boolean', 'description': 'Start monitoring immediately (default true)'}}, 'additionalProperties': False}
出力スキーマ
{'type': 'object', 'required': ['id'], 'properties': {'id': {'type': 'integer', 'description': 'Monitor id, used by every other tool.'}, 'url': {'type': 'string'}, 'name': {'type': 'string'}, 'type': {'enum': ['PING', 'HTTP', 'API', 'SSL', 'DOMAIN', 'PORT'], 'type': 'string'}, 'isActive': {'type': 'boolean', 'description': 'False while the monitor is paused.'}, 'frequency': {'type': 'integer', 'description': 'Check interval in minutes.'}, 'statusSummary': {'type': 'string', 'description': 'Current state, for example GOOD or ERROR.'}}}
delete_monitor
Delete monitor
Permanently delete a monitor together with its entire check history, incidents and statistics. This cannot be undone and there is no trash to restore from. Confirm with the user before calling it, and prefer pause_monitor whenever the intent is only to stop the checking for a while.
破壊的操作あり
外部アクセスあり
冪等
入力スキーマ
{'type': 'object', 'required': ['id'], 'properties': {'id': {'type': 'integer', 'minimum': 1, 'description': 'Monitor id to delete, as returned by list_monitors. Deletion is irreversible.'}}, 'additionalProperties': False}
出力スキーマ
{'type': 'object', 'required': ['success'], 'properties': {'message': {'type': 'string'}, 'success': {'type': 'boolean'}}}
get_incidents
Get incidents
Read the downtime history of one monitor: when each outage began, when it ended, how long it lasted and what the failure actually was - HTTP status, error text, and which probe saw it. This is the tool for "what happened" and "how often does this break". For the shape of response times around an outage, follow up with get_stats_hourly.
読み取り専用
外部アクセスあり
冪等
入力スキーマ
{'type': 'object', 'required': ['monitorId'], 'properties': {'page': {'type': 'integer', 'minimum': 1, 'description': 'Page number, 1-based. Defaults to 1.'}, 'monitorId': {'type': 'integer', 'minimum': 1, 'description': 'Monitor id, as returned by list_monitors.'}}, 'additionalProperties': False}
出力スキーマ
{'type': 'object', 'required': ['items'], 'properties': {'items': {'type': 'array', 'items': {'type': 'object'}, 'description': 'The rows on this page.'}, 'totalItems': {'type': ['integer', 'null'], 'description': 'Total across all pages, not just this one.'}}}
get_monitor
Get one monitor
Read one monitor in full: its configuration, current status, and the type-specific detail the list view omits - expected status codes for HTTP, port and protocol for PORT, certificate or registration expiry date for SSL and DOMAIN. Use it after list_monitors when the answer depends on how the check is configured, for instance whether a timeout is too tight or which port is actually being watched.
読み取り専用
外部アクセスあり
冪等
入力スキーマ
{'type': 'object', 'required': ['id'], 'properties': {'id': {'type': 'integer', 'minimum': 1, 'description': 'Monitor id, as returned by list_monitors.'}}, 'additionalProperties': False}
出力スキーマ
{'type': 'object', 'required': ['id'], 'properties': {'id': {'type': 'integer', 'description': 'Monitor id, used by every other tool.'}, 'url': {'type': 'string'}, 'name': {'type': 'string'}, 'type': {'enum': ['PING', 'HTTP', 'API', 'SSL', 'DOMAIN', 'PORT'], 'type': 'string'}, 'isActive': {'type': 'boolean', 'description': 'False while the monitor is paused.'}, 'frequency': {'type': 'integer', 'description': 'Check interval in minutes.'}, 'statusSummary': {'type': 'string', 'description': 'Current state, for example GOOD or ERROR.'}}}
get_notifications
Get notification history
Read the alerts this account has sent, across email, Telegram, webhook and the web interface, with the delivery outcome of each. Use it to answer "was I actually told about this outage" and to find a channel that is silently failing - a monitor can be detecting downtime correctly while its webhook has been rejecting every delivery. Covers the whole account, not one monitor.
読み取り専用
外部アクセスあり
冪等
入力スキーマ
{'type': 'object', 'properties': {'page': {'type': 'integer', 'minimum': 1, 'description': 'Page number, 1-based. Defaults to 1.'}, 'status': {'type': 'string', 'description': 'Return only alerts with this delivery status.'}, 'channel': {'enum': ['email', 'telegram', 'webhook', 'web'], 'type': 'string', 'description': 'Return only alerts sent through this channel. Omit for all channels.'}}, 'additionalProperties': False}
出力スキーマ
{'type': 'object', 'required': ['items'], 'properties': {'items': {'type': 'array', 'items': {'type': 'object'}, 'description': 'The rows on this page.'}, 'totalItems': {'type': ['integer', 'null'], 'description': 'Total across all pages, not just this one.'}}}
get_stats_daily
Get daily statistics
Response time and uptime for one monitor aggregated per day, with min, max, average and p95. This is the tool for reports and trends over weeks or months, and for comparing one monitor against another over the same window. When a single day looks wrong, zoom into it with get_stats_hourly.
読み取り専用
外部アクセスあり
冪等
入力スキーマ
{'type': 'object', 'required': ['monitorId'], 'properties': {'page': {'type': 'integer', 'minimum': 1, 'description': 'Page number, 1-based. Defaults to 1.'}, 'dateTo': {'type': 'string', 'description': 'Last day to include, as YYYY-MM-DD. Defaults to today.'}, 'dateFrom': {'type': 'string', 'description': 'First day to include, as YYYY-MM-DD. Defaults to the start of available history.'}, 'monitorId': {'type': 'integer', 'minimum': 1, 'description': 'Monitor id, as returned by list_monitors.'}}, 'additionalProperties': False}
出力スキーマ
{'type': 'object', 'required': ['items'], 'properties': {'items': {'type': 'array', 'items': {'type': 'object'}, 'description': 'The rows on this page.'}, 'totalItems': {'type': ['integer', 'null'], 'description': 'Total across all pages, not just this one.'}}}
get_stats_hourly
Get hourly statistics
Response time and uptime for one monitor broken down by hour, with min, max, average and p95 per bucket. Use it to see the shape of a problem: whether a service degrades before it fails, whether outages cluster at a particular time of day, or how long a single incident really lasted. Best over hours or days; for weeks and months use get_stats_daily instead, which returns far fewer rows.
読み取り専用
外部アクセスあり
冪等
入力スキーマ
{'type': 'object', 'required': ['monitorId'], 'properties': {'page': {'type': 'integer', 'minimum': 1, 'description': 'Page number, 1-based. Defaults to 1.'}, 'dateTo': {'type': 'string', 'description': 'Last day to include, as YYYY-MM-DD. Defaults to today.'}, 'dateFrom': {'type': 'string', 'description': 'First day to include, as YYYY-MM-DD. Defaults to the start of available history.'}, 'monitorId': {'type': 'integer', 'minimum': 1, 'description': 'Monitor id, as returned by list_monitors.'}}, 'additionalProperties': False}
出力スキーマ
{'type': 'object', 'required': ['items'], 'properties': {'items': {'type': 'array', 'items': {'type': 'object'}, 'description': 'The rows on this page.'}, 'totalItems': {'type': ['integer', 'null'], 'description': 'Total across all pages, not just this one.'}}}
list_monitors
List monitors
List the monitors on the account, newest first, 30 per page. Each entry carries the id needed by every other tool, plus name, url, type, current status, check frequency and the uptime percentage over the last 24 hours. Start here when the request names a monitor by name rather than by id, and when asked what is broken - filtering by status "down" answers that in one call. Returns an empty list rather than an error when nothing matches.
読み取り専用
外部アクセスあり
冪等
入力スキーマ
{'type': 'object', 'properties': {'page': {'type': 'integer', 'minimum': 1, 'description': 'Page number, 1-based. Defaults to 1.'}, 'type': {'enum': ['PING', 'HTTP', 'API', 'SSL', 'DOMAIN', 'PORT'], 'type': 'string', 'description': 'Return only monitors of this type. Omit for all types.'}, 'status': {'enum': ['up', 'down', 'paused', 'pending'], 'type': 'string', 'description': 'Return only monitors in this state. "pending" means created but not yet checked; "paused" means checking is switched off, so it is neither up nor down.'}}, 'additionalProperties': False}
出力スキーマ
{'type': 'object', 'required': ['items'], 'properties': {'items': {'type': 'array', 'items': {'type': 'object'}, 'description': 'The rows on this page.'}, 'totalItems': {'type': ['integer', 'null'], 'description': 'Total across all pages, not just this one.'}}}
pause_monitor
Pause monitor
Stop checking a monitor without deleting it. History and configuration survive, and resume_monitor puts it back to work. Use this around planned maintenance so the downtime does not land in the uptime figures or fire alerts. A paused monitor reports neither up nor down, so it is easy to forget one is off.
外部アクセスあり
冪等
入力スキーマ
{'type': 'object', 'required': ['id'], 'properties': {'id': {'type': 'integer', 'minimum': 1, 'description': 'Monitor id to pause, as returned by list_monitors.'}}, 'additionalProperties': False}
出力スキーマ
{'type': 'object', 'required': ['id'], 'properties': {'id': {'type': 'integer', 'description': 'Monitor id, used by every other tool.'}, 'url': {'type': 'string'}, 'name': {'type': 'string'}, 'type': {'enum': ['PING', 'HTTP', 'API', 'SSL', 'DOMAIN', 'PORT'], 'type': 'string'}, 'isActive': {'type': 'boolean', 'description': 'False while the monitor is paused.'}, 'frequency': {'type': 'integer', 'description': 'Check interval in minutes.'}, 'statusSummary': {'type': 'string', 'description': 'Current state, for example GOOD or ERROR.'}}}
resume_monitor
Resume monitor
Start checking a paused monitor again, with the configuration it had before. The first check runs immediately rather than after the usual interval, so the current state is known within moments. Safe to call on a monitor that is already running.
外部アクセスあり
冪等
入力スキーマ
{'type': 'object', 'required': ['id'], 'properties': {'id': {'type': 'integer', 'minimum': 1, 'description': 'Monitor id to resume, as returned by list_monitors.'}}, 'additionalProperties': False}
出力スキーマ
{'type': 'object', 'required': ['id'], 'properties': {'id': {'type': 'integer', 'description': 'Monitor id, used by every other tool.'}, 'url': {'type': 'string'}, 'name': {'type': 'string'}, 'type': {'enum': ['PING', 'HTTP', 'API', 'SSL', 'DOMAIN', 'PORT'], 'type': 'string'}, 'isActive': {'type': 'boolean', 'description': 'False while the monitor is paused.'}, 'frequency': {'type': 'integer', 'description': 'Check interval in minutes.'}, 'statusSummary': {'type': 'string', 'description': 'Current state, for example GOOD or ERROR.'}}}
履歴
最近のツール変更
追加
get_notifications
2026年9月17日12:38
追加
get_stats_daily
2026年9月17日12:38
追加
get_stats_hourly
2026年9月17日12:38
追加
get_incidents
2026年9月17日12:38
追加
delete_monitor
2026年9月17日12:38
追加
resume_monitor
2026年9月17日12:38
追加
pause_monitor
2026年9月17日12:38
追加
create_domain_monitor
2026年9月17日12:38
追加
create_ssl_monitor
2026年9月17日12:38
追加
create_port_monitor
2026年9月17日12:38
追加
create_ping_monitor
2026年9月17日12:38
追加
create_api_monitor
2026年9月17日12:38
追加
create_http_monitor
2026年9月17日12:38
追加
get_monitor
2026年9月17日12:38
追加
list_monitors
2026年9月17日12:38
関連MCP
類似のMCPサーバー
shiply
now.shiply/shiply
Publishes and manages web applications with SQL databases, serverless functions, domains, email tests, client intake, contracts, …
Fine Structure
ai.finestructure/fine-structure
Builds and hosts full-stack applications from prompts and supports agent communication through WhatsApp and email.
mcp
cloud.redu/mcp
Provisions and manages cloud instances, networks, storage, databases, backups, VPNs, application deployments, and autocoding-agen…
EchoRelay
dev.echorelay/management
Manages a hosted API relay runtime, including projects, endpoints, credentials, publishing, keys, delivery logs, and dead-letter …
Supero
io.github.supero-platform/supero
Builds, validates, publishes, tests, and deploys multi-tenant applications with schemas, CRUD operations, external data connector…
Replicate
io.github.pipeworx-io/replicate
Provides access to Replicate models, versions, collections, hardware, predictions, and deployments for running and managing hoste…
Relin
io.github.earonesty/relin
Configures webhook sources and destinations, monitors delivery health, investigates failures, manages retries, and replays events.
Scalix Cloud
world.scalix/cloud
Provides managed databases, SQL tools, container builds, persistent Linux machines, domains, scheduled functions, storage, and pr…