mcpbeat Sign in

SSL Certificate Check MCP Server

answering

SSL Certificate Check is answering right now. Last checked 15 min ago. It exposes 1 tools.

Inspect one endpoint's served certificate, expiry, hostname coverage, and accepted TLS versions.

Uptime history 9 days of history · worst day 99%
9 days agonow
100.0%
Uptime 24h
91 of 91 checks
1
Tools
read from the server
387 ms
Response time
average over 24h
open, no key
Access
streamable-http

SSL Certificate Check missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 15 min ago.

run in your terminal
claude mcp add ssl-certificate-check --transport http https://powmcp.com/ssl-certificate-check/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "ssl-certificate-check": {
      "url": "https://powmcp.com/ssl-certificate-check/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.ssl-certificate-check]
url = "https://powmcp.com/ssl-certificate-check/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "ssl-certificate-check": {
      "url": "https://powmcp.com/ssl-certificate-check/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "ssl-certificate-check": {
      "url": "https://powmcp.com/ssl-certificate-check/mcp"
    }
  }
}

Available tools 1

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

ssl
ssl_check
Opens its own TLS handshakes to one public host with openssl, using the URL's explicit port or 443 by default, and reports what they establish: which of TLS 1.3, TLS 1.2, TLS 1.1, TLS 1.0 and SSLv3 the server accepts, a protocol-support grade, and the certificate the server actually serves (subject, issuer, covered hostnames, hostname match, and validity dates). Reach for it on padlock, HTTPS, 'Not Secure', certificate-expiry and wrong-hostname questions, and to inspect which certificate is served after a renewal on the probed endpoint; this does not verify every load-balanced node. It does not fetch the page or establish whether plain HTTP is actually served or redirected, and it is not a browser trust decision: no chain-of-trust build, no revocation check, no cipher-suite inspection. Measured 0.05-1.5 seconds against real hosts; each probe is cut off at 12 seconds.

Endpoints

URLTransportStateLatencyChecked
https://powmcp.com/ssl-certificate-check/mcp streamable-http answering 494 ms 15 min ago

Alternatives to SSL Certificate Check

same job, measured the same way
Cve Intelligence
by cve-security

CVE intelligence: exploitation (KEV/EPSS), detection coverage, fixed versions. All tools keyless.

8 tools answering
Companybetatel
by companybetatel

Phone verification: free keyless coverage/pricing discovery + 4-channel OTP send. 15 tools.

30 installs/wk local only
Scry MCP
by pfeilisolana

Keyless MCP bridge to Scry Solana wallet intel: free coverage check, catalog, x402 paid endpoints.

36 installs/wk local only
Catalogapi
by catalogapi

Check reward coverage by country, search real catalog items, and ask how CatalogAPI works.

4 tools answering
DVERA CT verification tools
by suresofttechnologies

DVERA drives CT verification of mission-critical C/C++: setup, analysis, tests, coverage.

local only
Huntress MCP
by servosity

Every Huntress endpoint, plus a local SQLite mirror that delivers fleet-wide incident, coverage

local only
I
Python Package Runtime Test
by ligafew

Hosted Python sandbox for package runtime verification: pip install and usable-import evidence.

1 tools answering
I
agentgate
by ciceroyang

Read-only evidence for the tools agents run: MCP server records, coverage and policy.

local only

SSL Certificate Check — questions

Answers built from our own checks of this server.

What can SSL Certificate Check do?
It exposes 1 tools, read directly from the server on our last check. Among them: ssl_check. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is SSL Certificate Check working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 387 ms. The bar chart above shows every period we have measured.
How do I connect SSL Certificate Check?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does SSL Certificate Check need an API key?
No. SSL Certificate Check completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 1 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is SSL Certificate Check?
It answers our handshake in 387 ms on average, which is faster than 40% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.