Croncool Cron Jobs
REMOTE · MCP.CRON.COOL
Check your cron jobs, recent runs, workflows and webhooks, and run a job now when you confirm.
Available components
Last scanned (22 hours ago)
Scores higher than 99% of remote servers
Reachable. Last reached 16 Oct 2026.
Category Workflow Automation
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security92
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- 75% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3003 tokens (~158/item across 19 items; 11 tools + 8 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
- Supports UI / widget rendering.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 80. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +2
No change was recorded against any check on this day. Stability & Change Management went from 57 to 73. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Oct 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 100% → 75% ▼ functional
- Schema quality: 180 → 157 ▲ functional
- New resource “croncool-workspace” functional
- New resource “croncool-workspace-v1” functional
- New tool “open_croncool” functional
- 2 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 16 Oct 2026 · Probed https://mcp.cron.cool/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.cron.cool | CN=Amazon RSA 2048 M04,O=Amazon,C=US | 23 Jul 2026 | 5 Feb 2027 | RSA 2048 | SHA256-RSA | 46974346a71a5e008e66bcd6d715d2f |
| SANs: *.cron.cool, cron.cool | ||||||
| CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 773124f2a952e3ed18a58bdb85d1bc0ce5f27 |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.cron.cool. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| cool. | present | 62176 | 8 | Verified |
| cron.cool. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="croncool", resource_metadata="https://mcp.cron.cool/.well-known/oauth-protected-resource", error="invalid_token", error_description="missing Bearer token"
Bearer realm="croncool", resource_metadata="https://mcp.cron.cool/.well-known/oauth-protected-resource", error="invalid_token", error_description="missing Bearer token"Protected resource metadata
| Document | https://mcp.cron.cool/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.cron.cool |
| Authorisation server | https://api.authrice.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.cron.cool/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.cron.cool/mcp | HTTPS enforced |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_job Get cron job details ~82
Use this when someone asks about one cron job's schedule or target, or whether it is enabled and last succeeded. Returns the job's name, cron expression, type, target origin, HTTP method, content type, enabled state and last run status and time, or not-found. Not for running the job.
| Name | Type | Req | Description |
|---|---|---|---|
| jobId | string | yes | Job id (uuid) |
| Name | Type | Req | Description |
|---|---|---|---|
| job | – | yes | Null when not found, including another organization's job. Request payloads and credential-bearing URL paths, queries, fragments and userinfo are never returned. |
| status | string | yes | – |
No examples provided.
get_job_runs Check a job's run history ~104
Use this when someone asks whether a cron job ran, failed or was slow, including a run just triggered. Returns recent runs newest first with success or failure, HTTP status, duration and time (no response bodies), 20 by default and 100 at most. Not for starting a run.
| Name | Type | Req | Description |
|---|---|---|---|
| jobId | string | yes | Job id (uuid) |
| limit | integer | – | How many runs to return, from 1 to 100; defaults to 20 |
| Name | Type | Req | Description |
|---|---|---|---|
| executions | array | yes | Runs newest first. Response bodies, error text, job request payloads and credentials are excluded. |
| jobId | string | yes | – |
No examples provided.
get_workflow_run Trace a workflow run ~116
Use this when someone asks why a durable workflow run failed or where it is stuck. Returns the run's status, timings and error code plus its steps with status, attempt, timings and error code, 50 steps by default and 200 at most. Not for listing runs.
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | string | yes | Project id that owns the run |
| runId | string | yes | Workflow run id |
| stepLimit | integer | – | How many steps to return, from 1 to 200; defaults to 50 |
| Name | Type | Req | Description |
|---|---|---|---|
| run | – | yes | – |
| status | string | yes | – |
| steps | array | yes | Step status, attempt, timings and machine error code. Workflow inputs, outputs, error messages, deployment details and ownership fields are excluded. |
| stepsTruncated | boolean | yes | True when the run has more steps than were returned |
No examples provided.
list_jobs List scheduled cron jobs ~134
Use this when someone asks what cron jobs or scheduled tasks they have, or which ones last failed. Returns each job's id, name, schedule, target origin, method, enabled state and last run status and time, 20 per page by default, with a cursor for more. Not for a job's full run history.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | The nextCursor of the previous page with the same projectId; absent for the first page |
| limit | integer | – | Jobs per page, from 1 to 100; defaults to 20 |
| projectId | string | – | Only jobs of this project |
| Name | Type | Req | Description |
|---|---|---|---|
| hasMore | boolean | yes | – |
| jobs | array | yes | Job schedules and target origins only. Request payloads and credential-bearing URL paths, queries, fragments and userinfo are excluded. |
| nextCursor | – | yes | Cursor for the next page with the same filters; null on the last page |
No examples provided.
list_projects List your Croncool projects ~83
Use this when someone asks which Croncool projects they have, or a project's id is needed. Returns each project's id, name and creation time, 50 by default and 100 at most, with a flag when more exist. Not for listing jobs.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many projects to return, from 1 to 100; defaults to 50 |
| Name | Type | Req | Description |
|---|---|---|---|
| hasMore | boolean | yes | True when more projects exist than were returned; there is no cursor |
| projects | array | yes | Projects the signed-in user can access. Workflow callback configuration and secrets are excluded. |
No examples provided.
list_webhook_subscriptions Check webhook delivery health ~119
Use this when someone asks whether their Croncool webhooks are delivering, failing or were disabled. Returns each subscription's endpoint origin, events, active state, consecutive failures, auto-disabled flag and last delivery time, 20 by default. Works only with a signed-in user session, not an API key. Not for changing or re-enabling a webhook.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many subscriptions to return, from 1 to 100; defaults to 20 |
| projectId | string | – | Only subscriptions of this project |
| Name | Type | Req | Description |
|---|---|---|---|
| subscriptions | array | yes | Endpoint origins and delivery health; autoDisabled marks a subscription switched off after 20 consecutive failures. Full endpoint paths and queries, signing secrets, payloads and ownership fields are… |
No examples provided.
list_workflow_runs List workflow runs ~185
Use this when someone asks about recent or failed runs of a durable workflow in a Croncool project. Returns each run's id, workflow name, status, timings and error code, newest first by default, 20 per page with a cursor, filterable by workflow and status. Not for one run's steps.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | The nextCursor of the previous page with the same project, workflow, status and sort; absent for the first page |
| limit | integer | – | Runs per page, from 1 to 100; defaults to 20 |
| projectId | string | yes | Project id |
| sort | string | – | newest (default) or oldest first |
| status | string | – | Only runs in this status: pending, running, completed, failed or cancelled |
| workflowName | string | – | Only runs of this workflow name |
| Name | Type | Req | Description |
|---|---|---|---|
| hasMore | boolean | yes | – |
| nextCursor | – | yes | Cursor for the next page with the same filters; null on the last page |
| runs | array | yes | Run identity, status, timings and machine error code. Workflow inputs, outputs and error messages are excluded. |
No examples provided.
list_workflows List durable workflows ~105
Use this when someone asks which durable workflows a Croncool project runs, or how many runs are running, pending, completed, failed or cancelled. Returns each workflow's name, run counts by status and last run time for one project, 50 by default and 100 at most. Not for individual runs.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many workflows to return, from 1 to 100; defaults to 50 |
| projectId | string | yes | Project id |
| Name | Type | Req | Description |
|---|---|---|---|
| hasMore | boolean | yes | True when the project has more workflows than returned |
| workflows | array | yes | Run counts per workflow. Workflow inputs, outputs, error messages, callback configuration and secrets are excluded. |
No examples provided.
open_croncool Croncool Cron Jobs ~75
Use this when someone wants to open Croncool and browse their projects and scheduled jobs, with schedules, target origins and latest run status, in an interactive sidebar. Returns up to 100 projects to start from (no request payloads, workflow bodies, secrets or full target URLs). Not for running jobs or changing their configuration.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
| truncated | boolean | yes | – |
No examples provided.
run_job Run a cron job now ~92
Use this when someone asks to run or trigger a cron job now. Returns only that Croncool invoked it, not the target's response. Each call immediately sends the job's configured request again, which can write, message or bill downstream, and a repeated call sends it once more. Not for checking a run's result.
| Name | Type | Req | Description |
|---|---|---|---|
| jobId | string | yes | Job id (uuid) of the one job to run |
| Name | Type | Req | Description |
|---|---|---|---|
| jobId | string | yes | – |
| status | string | yes | Croncool invoked the job; the outcome is recorded in the job's run history |
No examples provided.
show_project_overview Show Croncool project overview ~79
Use this when someone wants a quick overview or dashboard of one Croncool project. Returns an overview card with the project's name and creation time, whether workflow hosting is set up, and up to 12 jobs with schedule, target origin and last run status. Not for a job's run history.
| Name | Type | Req | Description |
|---|---|---|---|
| projectId | string | yes | Project id |
| Name | Type | Req | Description |
|---|---|---|---|
| jobCount | integer | yes | – |
| jobCountIsLowerBound | boolean | yes | – |
| jobs | array | yes | Up to 12 of the project jobs. Job request payloads, credential-bearing target paths or queries, organization fields and workflow callback secrets are excluded. |
| project | – | yes | – |
No examples provided.
How do I install the Croncool Cron Jobs MCP server?
Croncool Cron Jobs is a hosted endpoint at https://mcp.cron.cool/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.cron.cool
claude mcp add --transport http cool-cron-croncool 'https://mcp.cron.cool/mcp'
What is the Croncool Cron Jobs MCP server?
Croncool Cron Jobs is an MCP server listed in the public MCP registry as cool.cron/croncool. Check your cron jobs, recent runs, workflows and webhooks, and run a job now when you confirm. This page covers its hosted endpoint (https://mcp.cron.cool/mcp).
Is the Croncool Cron Jobs MCP server safe to use?
Croncool Cron Jobs scores 91 out of 100 on VerifyMCP. 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 Croncool Cron Jobs MCP server expose?
Croncool Cron Jobs exposes 11 tools: list_projects, list_jobs, get_job, run_job, get_job_runs, and 6 more. Their descriptions and schemas cost roughly 1,174 tokens of context every time the server is loaded.
Does the Croncool Cron Jobs MCP server require authentication?
Yes. Croncool Cron Jobs asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Croncool Cron Jobs MCP server still maintained?
Croncool Cron Jobs is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.