get_certificate_status — TLS Radar MCP Tool Read-only
get_certificate_status
(get certificate status) is one of 16 tools on the
TLS Radar
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_certificate_status from your client
- Claude Code TLS Radar get_certificate_status run in your project directory
- Claude Desktop TLS Radar get_certificate_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor TLS Radar get_certificate_status ~/.cursor/mcp.json
- VS Code TLS Radar get_certificate_status .vscode/mcp.json
- Zed TLS Radar get_certificate_status ~/.config/zed/settings.json
- Windsurf TLS Radar get_certificate_status ~/.codeium/windsurf/mcp_config.json
- Cline TLS Radar get_certificate_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI TLS Radar get_certificate_status ~/.gemini/settings.json
- Grok TLS Radar get_certificate_status .mcp.json (in your project root)
- ChatGPT TLS Radar get_certificate_status Settings → Connectors → Advanced → Developer mode
- Claude.ai TLS Radar get_certificate_status Settings → Connectors → Add custom connector
- LangChain TLS Radar get_certificate_status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http tlsradar https://tlsradar.com/api/v1/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.