
Mcp Ssl Inspector
io.github.geekmarinev1.0.0Updated Sep 30, 2026
Audits TLS/SSL handshake latency, HSTS headers, and HTTPS availability on the edge.
Overview
AI-generated overview
Lets an assistant audit a site's TLS/SSL handshake latency, HSTS headers, and HTTPS availability from an edge endpoint.
- What it does
- This remote MCP server exposes checks around HTTPS configuration. According to its registry description, it audits TLS/SSL handshake latency, HSTS headers, and HTTPS availability on the edge. No tool list is published, so the exact tool names and parameters are not documented here.
- When to use it
- Worth considering when you want an assistant to sanity-check HTTPS setup, HSTS response headers, or handshake timing for a site without running your own TLS tooling. Less useful if you need deep certificate chain analysis or a documented, stable tool surface.
- Requirements
- A remote streamable HTTP endpoint; no package install is needed. No authentication, environment variables, or headers are declared, so it appears to need only network access to the endpoint.
Before you install
The server is a third-party remote endpoint, so any hostname or URL you ask it to inspect is sent to that operator. No authentication is declared, which means no access control is described. No tool list is published, so verify what it actually does before relying on it.
Installation
In SourceWeft
- Open Mcp Ssl Inspector in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"mcp-ssl-inspector": {
"type": "http",
"url": "https://mcp-ssl-inspector.stubby76.workers.dev/mcp"
}
}
}README
This repository has no README.
Tools
0Tool metadata has not been indexed yet.
Version history
1- v1.0.0LatestSep 30, 2026
