# io.github.jmshinhwa/cron-schedule-lint (npm · @readystack/cron-schedule-lint)

Names every schedule line in the file you have open that fires at the wrong hour, twice, or never at

- Trust score: 68/100 (medium)
- Change this week: +23
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- npm · `@readystack/cron-schedule-lint`: 68/100 (this document), [markdown](https://verifymcp.io/servers/jmshinhwa-cron-schedule-lint/readystack-cron-schedule-lint.md), [page](https://verifymcp.io/servers/jmshinhwa-cron-schedule-lint/readystack-cron-schedule-lint)

## Channel facts

- Registry: `npm`
- Package: `@readystack/cron-schedule-lint`
- Version: `0.1.3`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 32/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: the license (SEE LICENSE IN LICENSE.txt) isn't a recognized OSI-approved license.
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 184 tokens (~61/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 87/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 60% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the io.github.jmshinhwa/cron-schedule-lint MCP server?

io.github.jmshinhwa/cron-schedule-lint runs locally as an npm package, launched with npx -y @readystack/cron-schedule-lint. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add jmshinhwa-cron-schedule-lint -- npx -y @readystack/cron-schedule-lint
```

### Cursor

```json
{
  "mcpServers": {
    "jmshinhwa-cron-schedule-lint": {
      "command": "npx",
      "args": [
        "-y",
        "@readystack/cron-schedule-lint"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "jmshinhwa-cron-schedule-lint": {
      "command": "npx",
      "args": [
        "-y",
        "@readystack/cron-schedule-lint"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add jmshinhwa-cron-schedule-lint -- npx -y @readystack/cron-schedule-lint
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "jmshinhwa-cron-schedule-lint": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@readystack/cron-schedule-lint"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add jmshinhwa-cron-schedule-lint --command npx --arg -y --arg @readystack/cron-schedule-lint
```

### Hermes

```yaml
mcp_servers:
  jmshinhwa-cron-schedule-lint:
    command: "npx"
    args: ["-y", "@readystack/cron-schedule-lint"]
```

### Netclaw

```json
{
  "McpServers": {
    "jmshinhwa-cron-schedule-lint": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@readystack/cron-schedule-lint"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add jmshinhwa-cron-schedule-lint -t stdio -c npx -a -y @readystack/cron-schedule-lint
```

### Other

```json
{
  "mcpServers": {
    "jmshinhwa-cron-schedule-lint": {
      "command": "npx",
      "args": [
        "-y",
        "@readystack/cron-schedule-lint"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 68, +43)

- [security improvement] Injection markers: unverified → pass
- [security improvement] Known CVEs: unverified → pass
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.23
- [functional improvement] Dependency health: unverified → pass
- [functional] Package version: 0.1.1 → 0.1.3

### 2026-09-19 (score 25, −40)

- [security regression] Known CVEs: pass → unverified
- [security regression] Tool safety: pass → unverified
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Dependency health: pass → unverified
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.1.1 → 0.1.3

### 2026-09-15 (score 65, +5)

- [security improvement] Source repository: fail → pass
- [functional regression] Security disclosure: unverified → fail

### 2026-09-14 (score 60, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-09-13 (score 45)

First indexed and scored.

## MCP tools (3)

### `check_text` (~62 tokens)

Cron Schedule Lint for crontab, Kubernetes CronJob, GitHub Actions, Spring and EventBridge - run all 29 checks on a text (free)

Input parameters:

- `path` (string): optional file name for context
- `text` (string, required): file contents

### `check_file` (~48 tokens)

Cron Schedule Lint for crontab, Kubernetes CronJob, GitHub Actions, Spring and EventBridge - run all checks on one file by path (free)

Input parameters:

- `path` (string, required)

### `check_dir` (~74 tokens)

Cron Schedule Lint for crontab, Kubernetes CronJob, GitHub Actions, Spring and EventBridge - sweep a folder and return every finding (licence; the full run is free for 7 days)

Input parameters:

- `dir` (string, required)
- `ext` (string): optional extension filter, e.g. .html

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/jmshinhwa-cron-schedule-lint/readystack-cron-schedule-lint#diagnostics

## Score history

- 2026-09-20: 68
- 2026-09-19: 25
- 2026-09-18: 65
- 2026-09-17: 65
- 2026-09-16: 65
- 2026-09-15: 65
- 2026-09-14: 60
- 2026-09-13: 45

## Common questions

### What is the io.github.jmshinhwa/cron-schedule-lint MCP server?

io.github.jmshinhwa/cron-schedule-lint is an MCP server listed in the public MCP registry as io.github.jmshinhwa/cron-schedule-lint. Names every schedule line in the file you have open that fires at the wrong hour, twice, or never at. This page covers its npm package (@readystack/cron-schedule-lint).

### Is the io.github.jmshinhwa/cron-schedule-lint MCP server safe to use?

io.github.jmshinhwa/cron-schedule-lint scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.github.jmshinhwa/cron-schedule-lint MCP server expose?

io.github.jmshinhwa/cron-schedule-lint exposes 3 tools: check_text, check_file, check_dir. Their descriptions and schemas cost roughly 184 tokens of context every time the server is loaded.

### Is the io.github.jmshinhwa/cron-schedule-lint MCP server still maintained?

io.github.jmshinhwa/cron-schedule-lint is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- npm package: https://www.npmjs.com/package/@readystack/cron-schedule-lint
- Socket report: https://socket.dev/npm/package/@readystack/cron-schedule-lint
- Repository: https://github.com/jmshinhwa/readystack-themes
- Changelog RSS feed: https://verifymcp.io/servers/jmshinhwa-cron-schedule-lint/readystack-cron-schedule-lint.xml
- Changelog JSON feed: https://verifymcp.io/servers/jmshinhwa-cron-schedule-lint/readystack-cron-schedule-lint.json
- HTML version of this page: https://verifymcp.io/servers/jmshinhwa-cron-schedule-lint/readystack-cron-schedule-lint