MCP.Market

Cron MCP server

not responding
by Shreyas-Profile·io.github.Shreyas-Profile/cron-mcp·v0.1.0

Cron-as-a-service MCP. Schedule prompts; when the cron fires we POST to your callback URL.

B78/100grade B
What users say
No reviews yet
Be the first
Safety scan
B78/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed Cron yet.

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

Cron tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Public scan report

scanner v0.1.9 · 2026-09-22 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 104ms (auth required)20/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualityauth enforced (unknown)9/15
  • Maintenancelast push 67 days ago12/15
  • Maintainer identitynamespace and repository owner differ; GitHub account older than a year6/10
Overall 78/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Cron compares

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

Safety score
78/100
higher than 57% of 48,273 servers
Uptime
0%
of our recent checks; the typical remote server answers 100%

Install Cron in Claude Code, Cursor or VS Code

claude mcp add --transport http cron-mcp https://cron.regiq.in/api/mcp
Add to Cursor

What the publisher says

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

cron-mcp

Built by Shreyas · Shipped by Globalion

Cron-as-a-service MCP. Schedule any prompt on any cron expression; when it fires we POST the job to your callback URL. No LLM in our stack.

Your agent (Claude Desktop, Cursor, a custom script) does the thinking. We just:

  • store the schedule + prompt + your callback URL
  • match minutes against the cron expression
  • POST the job body to your callback, signed with X-Cron-Signature

That's it. Perfect for daily briefings, hourly polls, weekly digests, or anything else that repeats on a fixed schedule and needs to run through an LLM.

Hosted at cron.regiq.in or self-host with the Docker Compose below.

Use it (hosted)

  1. Visit https://cron.regiq.in, sign in with Google or GitHub.
  2. Generate an MCP API key on the dashboard, copy it.
  3. Add to Claude Desktop's claudedesktopconfig.json (or Cursor / any MCP client):
{
      "mcpServers": {
        "cron": {
          "url": "https://cron.regiq.in/api/mcp",
          "headers": {
            "Authorization": "Bearer YOUR_KEY_HERE"
          }
        }
      }
    }
  1. Have your agent call schedule_job with a cron expression, a prompt, and the URL you want us to POST to when it fires.

Tools

Webhook payload

When a job fires, we POST:

POST <your callbackUrl>
Content-Type: application/json
X-Cron-Signature: <hex-hmac-sha256-of-body>

{
  "jobId":    "clx...",
  "name":     "daily AI news briefing",
  "prompt":   "summarise the top 5 AI news items from the last 24h",
  "metadata": { ... },
  "firedAt":  "2026-07-16T08:00:00.412Z"
}

Verify the signature by re-hashing the raw body with your shared signing secret (env CRONWEBHOOKSIGNING_SECRET) and comparing to the X-Cron-Signature header. Return any 2xx to mark the fire as ok — anything else is logged as a failure and the schedule still advances (so a failing callback won't stop future runs).

Self-host

You'll need:

  • Docker + Compose
  • A Google OAuth client — Cloud Console. Scopes: openid, email, profile. Redirect: /api/auth/callback/google
  • A public HTTPS domain (Cloudflare Tunnel or ngrok http 3015 locally)

No LLM key required. Your callback is where inference happens.

git clone https://github.com/globalion/cron-mcp
cd cron-mcp
cp .env.example .env
# fill NEXTAUTH_SECRET, GOOGLE_*, PUBLIC_BASE_URL, CRON_WEBHOOK_SIGNING_SECRET
docker compose up -d
# open http://localhost:3015

Architecture

Shortened. The full README is on GitHub.

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

Cron: common questions

Is Cron MCP server safe?
Mostly: it is graded B (78/100). Read the Cron safety report
How do I install Cron?
It runs remotely at cron.regiq.in. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Cron need an API key?
Yes. The registry entry asks for Authorization.
Is Cron maintained?
The last commit was 108 days ago (2026-07-17). The latest release is v0.1.0.
Is Cron up?
0% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Cron compare with other MCP servers?
safety score 78/100 (higher than 57% of 48,273 servers); uptime 0% (of our recent checks; the typical remote server answers 100%). Full comparison.

More from Shreyas-Profile →