statuscake

Create an uptime check

statuscake_create_uptime_check

Destructive

Start monitoring a URL, host or IP. Returns the new check's id as data.new_id. Faster check rates and some regions depend on the plan. StatusCake: POST /uptime.

Input Schema

TableJSON Schema

Name	Required	Description
`host`	No	Name of the hosting provider (informational).
`name`	Yes	Name of the check.
`port`	No	Destination port (TCP, SMTP, SSH checks).
`tags`	No	Tags for the check. An empty list clears them.
`paused`	No	true to pause the check (stops running and alerting), false to resume.
`dns_ips`	No	IP addresses the DNS record must resolve to (DNS checks).
`regions`	No	Region codes to run the check from (see statuscake_list_uptime_locations).
`timeout`	No	Seconds to wait for the first byte, 5-75 (default 15).
`use_jar`	No	Enable cookie storage between requests.
`post_raw`	No	Raw HTTP POST body to send.
`post_body`	No	JSON object string submitted with the request; setting it makes the check use HTTP POST.
`test_type`	Yes	Check type: HTTP, HEAD, TCP, DNS, SMTP, SSH or PING.
`check_rate`	Yes	Seconds between checks: 0, 30, 60, 300, 900, 1800, 3600 or 86400.
`dns_server`	No	Nameserver to query (DNS checks).
`user_agent`	No	Custom User-Agent sent with each check.
`do_not_find`	No	Invert find_string: the check is down if the string IS present.
`find_string`	No	String to look for in the response; the check is down if not found.
`website_url`	Yes	URL, FQDN or IP address to check.
`confirmation`	No	Number of confirmation servers that must agree before alerting, 0-3 (default 2).
`trigger_rate`	No	Minutes to wait before sending an alert, 0-60 (default 0).
`custom_header`	No	JSON object string of headers to send, e.g. {"X-Env":"prod"}.
`basic_password`	No	HTTP basic-auth password for the target.
`basic_username`	No	HTTP basic-auth username for the target.
`contact_groups`	No	Contact group ids to alert (see statuscake_list_contact_groups). An empty list clears them.
`final_endpoint`	No	Where the redirect chain should end (with follow_redirects).
`include_header`	No	Include response headers in the find_string search.
`enable_ssl_alert`	No	Alert when the site's SSL certificate is about to expire.
`follow_redirects`	No	Follow redirects when testing (off by default).
`status_codes_csv`	No	Comma-separated HTTP status codes that count as down, e.g. "500,502,503".

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 29, 2026

TDQS

B3.4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no output schema, the description usefully discloses that the new check's id is returned as data.new_id, and it warns that faster check rates and certain regions are plan-gated. The destructiveHint=true annotation is not contradicted (the description makes no read-only claim), though it does not explain any auth or permission requirements either.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the purpose and information-dense; the return-value hint and plan caveat both earn their place. The trailing "StatusCake: POST /uptime." is minor trivia but not harmful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 29-parameter creation tool it covers the essentials that structured data does not: the return value (no output schema exists) and plan-dependency caveats. It stops short of auth/prerequisite context and any guidance on the many optional parameters, so it is adequate but not complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all 29 parameters thoroughly. The description only alludes to check_rate and regions via the plan caveat, adding marginal meaning beyond the schema. Baseline 3 is appropriate when the schema carries the load.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a concrete verb and resource ("Start monitoring a URL, host or IP"), which maps directly to creating an uptime check and clearly separates it from the heartbeat/SSL create siblings. What it lacks is an explicit call-out of those siblings, so an agent must infer the boundary from the tool name rather than the text.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to choose this tool over create_ssl_check, create_heartbeat_check, or create_maintenance_window, and no preconditions or exclusions. Usage is only implied by the word "monitoring," which is weak given four sibling creation tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All statuscake tools Inspect

Try in Browser

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

Glama MCP Gateway

Add one secure layer between your agents and this server.

Create an uptime check

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources