Check if a website is up, SSL expiry and DNS. 24/7 uptime monitors. No account for a check.
Scored across 9 tools
Each tool targets a clearly different resource and action: one-off host checks (check_website, check_ssl, dns_lookup), third-party service status (service_status), and account/monitor management (signup, get_account, create_monitor, list_monitors, set_alert_webhook). The closest pair, check_website and check_ssl, is kept distinct by their verdict vs. certificate-expiry outputs, and descriptions make the boundary explicit.
The dominant convention is verb_noun snake_case: check_ssl, check_website, create_monitor, list_monitors, set_alert_webhook, get_account, dns_lookup. Two outliers break the pattern: service_status (noun_phrase, a query despite the noun form) and signup (bare verb, no object). Still readable and predictable overall, with only minor deviations.
Nine tools is well within the ideal range and every tool maps to a real, non-redundant capability, split cleanly between anonymous checks and authenticated account operations. Nothing feels padded or missing purely in terms of volume.
The monitor lifecycle is half-open: you can create and list monitors but there is no delete/pause/update monitor, no way to fetch a single monitor's details, and no access to downtime or incident history for your own monitors (only list_monitors' summary status). The read-only diagnostic tools and webhook clearing via empty URL are covered, but an agent wanting to stop or reconfigure monitoring hits a dead end.
Get the expiry date of the SSL/TLS certificate of a host and the number of days left. No account and no API key are necessary.
Inputs: host (required), api_key.
Check now if a website or a URL is up or down. The answer has the HTTP status, the response time and a plain verdict: up, down, reachable_but_refused or page_error. It is a real request from a PingDeck server in Singapore at the time of the call, not a stored value. No account and no API key are necessary.
Inputs: url (required), api_key.
Start 24/7 monitoring of a URL. PingDeck checks the URL on a schedule and records each downtime and the SSL certificate expiry. An alert goes to the webhook of the account (see set_alert_webhook). An API key is necessary: call signup first.
Inputs: url (required), name, api_key.
Get the DNS records of a domain: A, AAAA, CNAME, MX, TXT and NS. No account and no API key are necessary.
Inputs: domain (required), api_key.
Show the plan of the account, the API calls used this month, the number of monitors and if an alert webhook is set. For a Free account the answer has an upgrade link for the account owner. This call does not use the quota. An API key is necessary.
Inputs: api_key.
List the monitors of the account with the current status, the last response time and the SSL certificate expiry of each. An API key is necessary.
Inputs: api_key.
Check if a popular online service is down for everyone: for example ChatGPT, Claude, WhatsApp, YouTube, Discord, Roblox or Mobile Legends. The answer has the live status, the uptime percent of the last 90 days from PingDeck checks and the recent incidents. PingDeck follows 61 services. Call the tool with no service to get the list. No account and no API key are necessary.
Inputs: service.
Set the webhook URL that gets a message when a monitor goes down, comes back or has an SSL certificate near its expiry. A Slack or Discord incoming webhook works, and any HTTPS endpoint that accepts a JSON POST. An empty webhook_url removes the webhook. An API key is necessary.
Inputs: webhook_url (required), api_key.
Create a free PingDeck account and get an API key in one call. An account is necessary only for 24/7 monitors or for more than 100 checks a day. Ask the person you work for first, and use the real email address of that person. The person can log in at https://getpingdeck.com/app with the same email and password. Free plan: 5 monitors, one check each 5 minutes, 300 API calls a month. Store the api_key: PingDeck shows it one time.
Inputs: email (required), password (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Check if a site or service like Stripe is down, and monitor your sites, cron jobs and status pages.
Check if any website is up (status, latency, redirects, security headers) and set uptime alerts.
Website monitoring: uptime, SSL certificates, broken links, DNS, cron jobs and status pages.
Uptime checks, status pages, incidents, and maintenance for websites, APIs, DNS, and TCP.
Add one secure layer between your agents and this server.
