Tls Cert Lifetime Lint

io.github.jmshinhwaPublished by GitHub account jmshinhwav0.1.5Updated Oct 24, 2026

Finds the 12 settings that break when public TLS certificates fall to 100 days on 2027-03-15: openss

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Local stdio MCP server that scans TLS certificate configuration for settings that break when public certificates drop to 100 days.

What you can do
The registry description says it finds the 12 settings that break when public TLS certificates fall to 100 days on 2027-03-15, mentioning openssl. No tools are listed in the manifest, so the exact operations an assistant can call are not documented. The README contains only unrelated theme-project text and adds no usage detail.
When to use it
Worth considering if you maintain servers or services with public TLS certificates and want to check configuration ahead of the 100-day certificate lifetime change. Given the thin documentation, verify what it actually does before relying on it.
Requirements
Runs as a local process over stdio, launched with npx from the npm package @readystack/tls-cert-lifetime-lint, so Node.js and npx are needed. No authentication, environment variables or headers are declared. Desktop only.
Before you install
The README does not describe this tool at all, so its behavior and data handling cannot be confirmed from the supplied material. No credentials are declared, but review the package before running it locally.

Installation

In SourceWeft

  1. Open Tls Cert Lifetime Lint in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

readystack-themes

Made by ReadyStack · free calculators and templates at getreadystack.com VS Code themes by ReadyStack

Source: README.md at commit ee1c884

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v0.1.5LatestSep 23, 2026
  2. v0.1.1Sep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.