MCP.Market

Cron Tools MCP server

by basitalisandhu·io.github.basitalisandhu/mcp-cron-tools·v0.3.0·1 stars

Parse, explain and validate 5-field cron expressions and list upcoming runs in a time zone.

A88/100grade A
What users say
No reviews yet
Be the first
Safety scan
A88/100

not scanned yet

Adoption
New

1 stars

Reviews

Write one

Nobody has reviewed Cron Tools yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Cron Tools tools

No tool declarations could be read from the package source. They show once the server is installed.

Not scanned yet. New listings are scanned within a day or two of arriving.

How Cron Tools compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
88/100
higher than 75% of 48,255 servers
GitHub stars
1
more than 65% of 28,688 servers

Release history: 4 versions in the registry since 2026-10-09, latest 2026-10-28, typically one every 5 days.

Install Cron Tools in Claude Code, Cursor or VS Code

claude mcp add mcp-cron-tools -- docker run -i --rm ghcr.io/basitalisandhu/mcp-cron-tools:0.3.0
Add to Cursor

What the publisher says

From the Cron Tools repository's README, as published. We do not edit it. Read it on GitHub

dev-mcp-servers

Ten small MCP servers for everyday development and security checks. Each one is a separate npm package you add to Claude Code, Claude Desktop, Cursor or any other MCP client with one line, and each does one job well: look up vulnerabilities, grade security headers, decode a JWT, test a regex, explain a cron expression, validate JSON against a schema, lint an OpenAPI document or a Dockerfile, read statistics out of a git repository, or build an llms.txt.

All servers are TypeScript on the official @modelcontextprotocol/sdk, speak stdio only, validate every input with zod, bound their inputs and run time, send no telemetry, and ship with node:test suites that cover every tool.

Servers

Every package README lists its tools with inputs and outputs, the exact claude mcp add command, a .mcp.json snippet, and what the server touches on disk and on the network.

Quick start

With Claude Code:

claude mcp add jwt-tools -- npx -y @basitalisandhu/mcp-jwt-tools@0.2.0
claude mcp list

Add -s user to install for every project rather than the current one. For clients that read .mcp.json (Claude Code, Claude Desktop, Cursor), add an entry per server:

{
  "mcpServers": {
    "jwt-tools": { "command": "npx", "args": ["-y", "@basitalisandhu/mcp-jwt-tools@0.2.0"] },
    "osv-advisories": { "command": "npx", "args": ["-y", "@basitalisandhu/mcp-osv-advisories@0.2.0"] }
  }
}

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Cron Tools: common questions

Is Cron Tools MCP server safe?
Yes, by our scan: it is graded A (88/100). Read the Cron Tools safety report
How do I install Cron Tools?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Cron Tools need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Cron Tools maintained?
The last commit was 26 days ago (2026-10-09). The latest release is v0.3.0.
How does Cron Tools compare with other MCP servers?
safety score 88/100 (higher than 75% of 48,255 servers); github stars 1 (more than 65% of 28,688 servers). Full comparison.

More from basitalisandhu →