Ssl Inspector MCP Server

by guardbee Your server? Claim it

local only

Ssl Inspector runs on your own machine — the client starts it, so there is no endpoint to ping. 396 installs a week from npm. Last commit 6 Nov 2026.

TLS certificate/cipher/protocol inspection

Installs per day peak 563 · avg 78 · -49% w/w

a month agotoday

396

Installs / week

npm · @guardbee/mcp-ssl-inspector

Stars

11 open issues

6 Nov 2026

Last commit

17 releases in 90 days

MIT

License

TypeScript

Nothing serious here today

Today is the operative word: we check Ssl Inspector every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add ssl-inspector -- npx -y @guardbee/mcp-ssl-inspector

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "ssl-inspector": {
      "command": "npx",
      "args": [
        "-y",
        "@guardbee/mcp-ssl-inspector"
      ]
    }
  }
}

~/.codex/config.toml

[mcp_servers.ssl-inspector]
command = "npx"
args = ["-y", "@guardbee/mcp-ssl-inspector"]

.cursor/mcp.json

{
  "mcpServers": {
    "ssl-inspector": {
      "command": "npx",
      "args": [
        "-y",
        "@guardbee/mcp-ssl-inspector"
      ]
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "ssl-inspector": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@guardbee/mcp-ssl-inspector"
      ]
    }
  }
}

Alternatives to Ssl Inspector

same job, measured the same way

Ssl Inspector

by 4hmetuyar

TLS certificate/cipher/protocol inspection

local only

X509 MCP

by mrfentmen

Decode PEM certificates, check expiry and inspect a live TLS certificate, all offline

118 installs/wk local only

Domain Osint MCP

by robertoyanguas-ops

Inspects live IPv4/IPv6 DNS resolution, TLS certificate issuer/expiry, and HTTP security grade.

2 tools answering

Ssl Cert MCP

by mrfentmen

Inspect TLS certificates of a host: issuer, expiry, and SAN. No key required.

75 installs/wk local only

Studex MCP Server

by itshivams

Model Context Protocol server for Studex tools, notifications, and profile integrations

answering

SSL Certificate Check

by powmcp

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

1 tools answering

Conecto E-signature

by conecto

PDFs signed in the browser and sealed with a signing certificate. Pay per action.

38 tools answering

recon

by pueo-labs

Public DNS, certificate transparency, and identity observations.

4 018 installs/wk local only

Ssl Inspector — questions

Answers built from our own checks of this server.

Why is there no uptime for Ssl Inspector?

Ssl Inspector runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the npm package @guardbee/mcp-ssl-inspector was installed 396 times last week.

How do I connect Ssl Inspector?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It runs locally, so the command pulls @guardbee/mcp-ssl-inspector straight from npm; nothing to host, nothing to sign up for.

How many people use Ssl Inspector?

The npm package @guardbee/mcp-ssl-inspector was installed 396 times in the last week. Week over week that is -49%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.

Is Ssl Inspector open source?

Yes — it is published under the MIT licence, written in TypeScript, 2 stars on GitHub and 11 open issues. The source link is on this page, so you can read exactly what it does with your data before you connect it.