SSL Certificate Check
REMOTE · POWMCP.COM · SCANNED SEP 25
Inspect one endpoint's served certificate, expiry, hostname coverage, and accepted TLS versions.
Available components
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 Security74
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 764 tokens (~764/item across 1 items; 1 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 Management50
- Stability observed for 15 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 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
How do I install the SSL Certificate Check MCP server?
SSL Certificate Check is a hosted endpoint at https://powmcp.com/ssl-certificate-check/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 · powmcp.com
claude mcp add --transport http com-powmcp-ssl-certificate-check 'https://powmcp.com/ssl-certificate-check/mcp'
{
"mcpServers": {
"com-powmcp-ssl-certificate-check": {
"url": "https://powmcp.com/ssl-certificate-check/mcp"
}
}
} {
"servers": {
"com-powmcp-ssl-certificate-check": {
"type": "http",
"url": "https://powmcp.com/ssl-certificate-check/mcp"
}
}
} [mcp_servers.com-powmcp-ssl-certificate-check] url = "https://powmcp.com/ssl-certificate-check/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-powmcp-ssl-certificate-check": {
"type": "remote",
"url": "https://powmcp.com/ssl-certificate-check/mcp",
"enabled": true
}
}
} openclaw mcp add com-powmcp-ssl-certificate-check --url 'https://powmcp.com/ssl-certificate-check/mcp' --transport streamable-http
mcp_servers:
com-powmcp-ssl-certificate-check:
url: "https://powmcp.com/ssl-certificate-check/mcp" {
"McpServers": {
"com-powmcp-ssl-certificate-check": {
"Transport": "http",
"Url": "https://powmcp.com/ssl-certificate-check/mcp"
}
}
} assistant mcp add com-powmcp-ssl-certificate-check -t streamable-http -u 'https://powmcp.com/ssl-certificate-check/mcp'
{
"mcpServers": {
"com-powmcp-ssl-certificate-check": {
"type": "http",
"url": "https://powmcp.com/ssl-certificate-check/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 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.
- 17 Sept 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.
- 15 Sept 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.
- 13 Sept 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.
- 11 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- Server version: 0.2.4 → 0.2.5 functional
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 25 Sept 2026 · Probed https://powmcp.com/ssl-certificate-check/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=powmcp.com | CN=WE1,O=Google Trust Services,C=US | 18 Aug 2026 | 16 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 86489ad185ea61460e8ec5accd535821 |
| SANs: powmcp.com, *.powmcp.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of powmcp.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| powmcp.com. | absent | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://powmcp.com/ssl-certificate-check/mcp | Verified | 200 | |
| http (plaintext) | http://powmcp.com/ssl-certificate-check/mcp | HTTPS enforced | 308 | https://powmcp.com/ssl-certificate-check/mcp |
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 →
ssl_check ~277
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Full public URL of the site to probe. Its hostname and explicit port drive the handshakes; port 443 is used when no port is named. The submitted scheme is reported, but the page is never fetched and… |
| Name | Type | Req | Description |
|---|---|---|---|
| certificate | object | – | The certificate the server served during the handshake |
| checkedAt | string | yes | Probe timestamp |
| host | string | yes | The hostname the handshakes were opened against |
| https | boolean | yes | Whether anything completed a TLS handshake on the port |
| issues | array | yes | Protocol, certificate, and submitted-scheme observations found by the probe |
| port | number | yes | The port the handshakes were opened against (443 unless the URL named another) |
| protocolGrade | string | – | A+ (TLS 1.3, no legacy protocols), A, B, or C: read from protocol support ALONE by this app. It ignores the certificate entirely, so an expired or wrong-hostname certificate can still sit behind an A… |
| protocols | object | – | Protocol versions the server agreed to speak |
| servedOverHttp | boolean | – | Legacy field name: true when the submitted URL used the http scheme and TLS answered on the probed port. It records the input scheme in this TLS result, not whether HTTP content is served, redirected… |
| url | string | yes | The URL as requested |
No examples provided.
What is the SSL Certificate Check MCP server?
SSL Certificate Check is an MCP server listed in the public MCP registry as com.powmcp/ssl-certificate-check. Inspect one endpoint's served certificate, expiry, hostname coverage, and accepted TLS versions. This page covers its hosted endpoint (https://powmcp.com/ssl-certificate-check/mcp).
Is the SSL Certificate Check MCP server safe to use?
SSL Certificate Check scores 76 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 SSL Certificate Check MCP server expose?
SSL Certificate Check exposes 1 tool: ssl_check. Their descriptions and schemas cost roughly 277 tokens of context every time the server is loaded.
Does the SSL Certificate Check MCP server require authentication?
No. We connected to SSL Certificate Check without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the SSL Certificate Check MCP server still maintained?
SSL Certificate Check is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.