Server facts
tlsradar-claude-plugin MCP Server
Project
- Author
- TLS-Radar
- License
- Not specified
- Category
- Cloud & DevOps
Tech
- Runtime / language
- Not specified
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 3
- Last commit
- Data as of
Tags
- certificates
- letsencrypt
- monitoring
- security
- ssl
- tls
Overview
Domain certificate work in Claude Code and Cowork can move from a hostname scan to issuance and ongoing expiry tracking through the TLS Radar plugin. Scans return certificate details without an account. Issuance starts an order, supplies domain-validation challenges, checks DNS propagation, and finalizes the certificate. Users can publish DNS records manually, use Cloudflare or Route53 automation, or validate through an HTTP file. The plugin generates certificate keys and signing requests locally with openssl, keeping private keys on the user's machine. Status lookup helps resume interrupted orders, while renewal tools support continuing the issuance workflow.
Monitoring requires an OAuth connection and supports adding individual domains or batches, listing tracked certificates, removing entries, and finding certificates approaching expiry. Scan history for monitored domains helps users examine changes in issuers, grades, or vulnerabilities. Monitor configurations can be exported as JSON and imported with existing domains skipped. Account tools expose plan limits and usage, and team invitations support shared management. Completed certificate issuance also triggers a server-side handoff offering ongoing monitoring by email.
tlsradar-claude-plugin setup notes
- tlsradar-claude-plugin records stdio only; confirm a network transport upstream before planning remote access.
- tlsradar-claude-plugin has no recorded license; confirm reuse terms in its repository.