Tls Cert Lifetime Lint MCP server
Finds the 12 settings that break when public TLS certificates fall to 100 days on 2027-03-15: openss
A89/100grade A
Adoption
Growing
0 stars365 downloads/wk
Reviews
Write oneNobody has reviewed Tls Cert Lifetime Lint yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Tls Cert Lifetime Lint tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.3 · 2026-09-19 · same rubric, same numbers if you re-run it
no findings
- Code scan5 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 0 days ago15/15
- Maintainer identityregistry namespace matches repository owner6/10
Overall 89/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON
Install directly
Runs npx -y @readystack/tls-cert-lifetime-lint on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add tls-cert-lifetime-lint -- npx -y @readystack/tls-cert-lifetime-lint
Tls Cert Lifetime Lint: common questions
- Is Tls Cert Lifetime Lint MCP server safe?
- Yes, by our scan: it is graded A (89/100). Read the Tls Cert Lifetime Lint safety report
- How do I install Tls Cert Lifetime Lint?
- It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
- Does Tls Cert Lifetime Lint need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Tls Cert Lifetime Lint maintained?
- The last commit was in the last day (2026-09-19). The latest release is v0.1.1.