Croncool Cron Jobs
cool.cron/croncoolVersion 0.1.1Check your cron jobs, recent runs, workflows and webhooks, and run a job now when you confirm.
Status
Responds633 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 14:23 UTC
- Latency
- 633 ms
- Remotes responding
- 1 of 1
- Sign-in
- No sign-in
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 22:14 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://mcp.cron.cool/mcpResponds633 msNo sign-in
Claude Code
claude mcp add --transport http croncool https://mcp.cron.cool/mcpClaude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: croncool
Remote MCP server URL: https://mcp.cron.cool/mcpCursor
{
"mcpServers": {
"croncool": {
"url": "https://mcp.cron.cool/mcp"
}
}
}VS Code
code --add-mcp '{"name":"croncool","type":"http","url":"https://mcp.cron.cool/mcp"}'Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
11 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
get_jobUse this when the user wants to read the scheduling configuration and latest execution metadata of one CronCool job selected by its exact identifier. 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. | No | Yes | Yes | No |
get_job_runsUse this when the user wants to read execution history for one CronCool job to inspect success, failure, HTTP status and duration. 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. | No | Yes | Yes | No |
get_workflow_runUse this when the user wants to read one CronCool workflow execution and a bounded page of its step statuses for troubleshooting. 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. | No | Yes | Yes | No |
list_jobsUse this when the user wants to list scheduled jobs in CronCool to inspect schedules, enabled state and the latest execution status. 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. | No | Yes | Yes | No |
list_projectsUse this when the user wants to list projects accessible to the connected CronCool account, including identifiers needed to select a project. 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. | No | Yes | Yes | No |
list_webhook_subscriptionsUse this when the user wants to read CronCool webhook subscription configuration and recorded delivery failures. 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. | No | Yes | Yes | No |
list_workflow_runsUse this when the user wants to list executions of a durable workflow in CronCool, with optional workflow-name and status filters. 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. | No | Yes | Yes | No |
list_workflowsUse this when the user wants to list durable workflow definitions and run-count summaries for one CronCool project. 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. | No | Yes | Yes | No |
open_croncoolUse this when the user wants to open the CronCool project-selection sidebar when the user requests an interactive project and job browser. 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. | No | Yes | Yes | No |
run_jobUse this when the user wants to immediately execute the configured request for one CronCool job. 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. | Yes | No | No | Yes |
show_project_overviewUse this when the user wants to render a read-only overview of one CronCool project and a bounded preview of its scheduled jobs. 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. | No | Yes | Yes | No |
Details
- Registry status
- Active
- Published
- Sep 27, 2026
- Updated
- Sep 27, 2026
- Repository
- Not given
- Categories (suggested)
- Project managementDeveloper toolsSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared