Cron Schedule Lint runs on your own machine — the client starts it, so there is no endpoint to ping. 317 installs a week from npm.
Names every schedule line in the file you have open that fires at the wrong hour, twice, or never at
The linked repository no longer exists on GitHub — it was deleted or made private.
Quiet is not dead — but it is worth knowing when it wakes up, or when someone else takes it over. We watch the repository and tell you either way.
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 mcp add cron-schedule-lint -- npx -y @readystack/cron-schedule-lint
{
"mcpServers": {
"cron-schedule-lint": {
"args": [
"-y",
"@readystack/cron-schedule-lint"
],
"command": "npx"
}
}
}
[mcp_servers.cron-schedule-lint]
command = "npx"
args = ["-y", "@readystack/cron-schedule-lint"]
{
"mcpServers": {
"cron-schedule-lint": {
"args": [
"-y",
"@readystack/cron-schedule-lint"
],
"command": "npx"
}
}
}
{
"mcpServers": {
"cron-schedule-lint": {
"args": [
"-y",
"@readystack/cron-schedule-lint"
],
"command": "npx"
}
}
}
Names every line in the file you have open that starts a recurring cloud charge, with the published
Reads security headers and CSP line by line in your config file and names the lines that silently do
Names every WCAG 2.2 AA form failure on its line, with the criterion and the fix
Finds the LLM model IDs pinned in your code that vendors have already switched off, or have dated to
Ask a repository what depends on what. Every answer cites the file, line and commit it came from.
15 checks for the apiVersions kubectl no longer serves, on the manifest open in your editor
Local-first MCP that scores your codebase's build readiness. Your code never leaves your machine.
Seventeen rules on your .tex file: the statements the editorial office looks for, and the source tha
Answers built from our own checks of this server.