Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

PingDeck Uptime Monitoring

REMOTE · GETPINGDECK.COM

Check if a website is up, SSL expiry and DNS. 24/7 uptime monitors. No account for a check.

Available components

+4 this week 78 Trust /100

Last scanned (16 hours ago)

Scores higher than 72% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Monitoring and Observability

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability74
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1193 tokens (~132/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
  • Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 12 Nov 26 73

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://getpingdeck.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=getpingdeck.com CN=YE2,O=Let's Encrypt,C=US 8 Oct 2026 6 Jan 2027 ECDSA 256 ECDSA-SHA384 5fe9cac8f881fdf92317fd99b1c9498c9c2
SANs: getpingdeck.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of getpingdeck.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
getpingdeck.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; connect-src 'self'; frame-ancestors 'none'; base-uri 'none'; form-action 'self'; object-src 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://getpingdeck.com/mcp Verified 200
http (plaintext) http://getpingdeck.com/mcp HTTPS enforced 308 https://getpingdeck.com/mcp
MCP tools · 9 exposed · ~1,079 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check_ssl ~102

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.

NameTypeReqDescription
api_keystring–Optional. A PingDeck API key (pd_live_...). Without a key the check uses the free pool: 100 checks a day for each IP address.
hoststringyesA host name, for example example.com. A port is optional: example.com:8443.

No output schema declared.

No examples provided.

check_website ~146

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.

NameTypeReqDescription
api_keystring–Optional. A PingDeck API key (pd_live_...). Without a key the check uses the free pool: 100 checks a day for each IP address.
urlstringyesA URL or a domain, for example https://example.com/health or example.com.

No output schema declared.

No examples provided.

create_monitor ~137

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.

NameTypeReqDescription
api_keystring–A PingDeck API key (pd_live_...) from the signup tool. Not necessary when the client sends the key in the header "Authorization: Bearer <key>".
namestring–Optional. A short name for the monitor.
urlstringyesThe URL to monitor, for example https://example.com.

No output schema declared.

No examples provided.

dns_lookup ~93

Get the DNS records of a domain: A, AAAA, CNAME, MX, TXT and NS. No account and no API key are necessary.

NameTypeReqDescription
api_keystring–Optional. A PingDeck API key (pd_live_...). Without a key the check uses the free pool: 100 checks a day for each IP address.
domainstringyesA domain name, for example example.com.

No output schema declared.

No examples provided.

get_account ~105

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.

NameTypeReqDescription
api_keystring–A PingDeck API key (pd_live_...) from the signup tool. Not necessary when the client sends the key in the header "Authorization: Bearer <key>".

No output schema declared.

No examples provided.

list_monitors ~80

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.

NameTypeReqDescription
api_keystring–A PingDeck API key (pd_live_...) from the signup tool. Not necessary when the client sends the key in the header "Authorization: Bearer <key>".

No output schema declared.

No examples provided.

service_status ~134

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.

NameTypeReqDescription
servicestring–The name, the slug or the domain of the service, for example "chatgpt", "Mobile Legends" or "whatsapp.com". Omit it to list all services.

No output schema declared.

No examples provided.

set_alert_webhook ~127

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.

NameTypeReqDescription
api_keystring–A PingDeck API key (pd_live_...) from the signup tool. Not necessary when the client sends the key in the header "Authorization: Bearer <key>".
webhook_urlstringyesThe webhook URL. An empty text removes the webhook.

No output schema declared.

No examples provided.

signup ~155

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.

NameTypeReqDescription
emailstringyesThe email address of the account owner.
passwordstringyesA password of 8 characters or more. Make a strong one and give it to the account owner.

No output schema declared.

No examples provided.

Install

How do I install the PingDeck Uptime Monitoring MCP server?

PingDeck Uptime Monitoring is a hosted endpoint at https://getpingdeck.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · getpingdeck.com

# add to Claude Code
claude mcp add --transport http com-getpingdeck-uptime 'https://getpingdeck.com/mcp'
Common questions

What is the PingDeck Uptime Monitoring MCP server?

PingDeck Uptime Monitoring is an MCP server listed in the public MCP registry as com.getpingdeck/uptime. Check if a website is up, SSL expiry and DNS. 24/7 uptime monitors. No account for a check. This page covers its hosted endpoint (https://getpingdeck.com/mcp).

Is the PingDeck Uptime Monitoring MCP server safe to use?

PingDeck Uptime Monitoring scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the PingDeck Uptime Monitoring MCP server expose?

PingDeck Uptime Monitoring exposes 9 tools: check_website, service_status, check_ssl, dns_lookup, signup, and 4 more. Their descriptions and schemas cost roughly 1,079 tokens of context every time the server is loaded.

Does the PingDeck Uptime Monitoring MCP server require authentication?

No. We connected to PingDeck Uptime Monitoring without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the PingDeck Uptime Monitoring MCP server still maintained?

PingDeck Uptime Monitoring is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the PingDeck Uptime Monitoring MCP server?

VerifyMCP ran 13 checks on PingDeck Uptime Monitoring, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.