DevOps
getpingdeck.com
Provides PingDeck tools for website uptime checks, SSL expiry monitoring, DNS lookups, and creating 24/7 monitors with alerts.
ENDPOINT 1
https://getpingdeck.com/mcp
MCP server metadata
- Name
- pingdeck
- Version
- 1.0.0
Uptime/SSL/DNS checks and 24/7 monitoring. Start with the signup tool (one call, free plan) if you have no api_key; then create_monitor to watch sites persistently. Docs: https://getpingdeck.com/api
Known tools 6
check_websiteLive up/down check of any public URL: HTTP status and response time from PingDeck cloud servers.
Inferred read-onlycreate_monitorStart 24/7 uptime monitoring of a URL with downtime + SSL-expiry alerts (webhook configurable in the dashboard).
Inferred read-onlylist_monitorsList the account's monitors with live status, last response time and SSL expiry.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.pingdeck]
url = "https://getpingdeck.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"pingdeck": {
"type": "http",
"url": "https://getpingdeck.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: pingdeck
Remote MCP URL: https://getpingdeck.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"pingdeck": {
"url": "https://getpingdeck.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"pingdeck": {
"type": "http",
"url": "https://getpingdeck.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "pingdeck",
"transport": "streamable-http",
"url": "https://getpingdeck.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.