Croncool Cron Jobs
by cron.cool · remote · no sign-in to list tools · v0.1.1 · published by cool.cron
Check your cron jobs, recent runs, workflows and webhooks, and run a job now when you confirm.
11 tools: 1 can delete or cancel things, 1 change things and 9 only read.
Scanned Oct 21, 2026
- Deletes or cancels1Claude Code: deny: see these tools
- Can't be undone0Claude Code: ask
- Changes things1Claude Code: ask: see these tools
- Only reads9Claude Code: allow: see these tools
1 check matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.
claude mcp add --transport http croncool https://mcp.cron.cool/mcpFindings
Matches of fixed checks, with the text they matched.
- Warnopen_croncool
The server marks "open_croncool" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "open_croncool" says "open": a word for a change.
Tools
Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.
11 tools
Deletes or cancels 1Claude Code: deny
run_jobUse this when the user wants to immediately execute the configured request for one CronCool job.Reads text others writeNo findings
Why it is in this group
- The name "run_job" says "run": a word for a change.
- The server marks it destructive (destructiveHint: true).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Use 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.
Annotations the server declares
- title: Run a cron job now
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
Changes things 1Claude Code: ask
open_croncoolUse this when the user wants to open the CronCool project-selection sidebar when the user requests an interactive project and job browser.Reads text others write1 finding
Why it is in this group
- The name "open_croncool" says "open": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe description's first sentence says "browser": it reads web pages, which anyone can write.
Findings
- Warn
The server marks "open_croncool" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "open_croncool" says "open": a word for a change.
Description, as the server wrote it Use 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 9Claude Code: allow
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.No findings
Why it is in this group
- The name "get_job" says "get": a word for reading.
Description, as the server wrote it Use 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.
Annotations the server declares
- title: Get cron job details
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_job_runsUse this when the user wants to read execution history for one CronCool job to inspect success, failure, HTTP status and duration.Reads text others writeNo findings
Why it is in this group
- The name "get_job_runs" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "http": it reads web pages, which anyone can write.
Description, as the server wrote it Use 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.
Annotations the server declares
- title: Check a job's run history
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_workflow_runUse this when the user wants to read one CronCool workflow execution and a bounded page of its step statuses for troubleshooting.No findings
Why it is in this group
- The name "get_workflow_run" says "get": a word for reading.
Description, as the server wrote it Use 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.
Annotations the server declares
- title: Trace a workflow run
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_jobsUse this when the user wants to list scheduled jobs in CronCool to inspect schedules, enabled state and the latest execution status.No findings
Why it is in this group
- The name "list_jobs" says "list": a word for reading.
Description, as the server wrote it Use 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.
Annotations the server declares
- title: List scheduled cron jobs
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_projectsUse this when the user wants to list projects accessible to the connected CronCool account, including identifiers needed to select a project.No findings
Why it is in this group
- The name "list_projects" says "list": a word for reading.
Description, as the server wrote it Use 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.
Annotations the server declares
- title: List your Croncool projects
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_webhook_subscriptionsUse this when the user wants to read CronCool webhook subscription configuration and recorded delivery failures.No findings
Why it is in this group
- The name "list_webhook_subscriptions" says "list": a word for reading.
Description, as the server wrote it Use 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.
Annotations the server declares
- title: Check webhook delivery health
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_workflow_runsUse this when the user wants to list executions of a durable workflow in CronCool, with optional workflow-name and status filters.No findings
Why it is in this group
- The name "list_workflow_runs" says "list": a word for reading.
Description, as the server wrote it Use 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.
Annotations the server declares
- title: List workflow runs
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_workflowsUse this when the user wants to list durable workflow definitions and run-count summaries for one CronCool project.No findings
Why it is in this group
- The name "list_workflows" says "list": a word for reading.
Description, as the server wrote it Use 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.
Annotations the server declares
- title: List durable workflows
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
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.No findings
Why it is in this group
- The name "show_project_overview" says "show": a word for reading.
Description, as the server wrote it Use 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
- title: Show Croncool project overview
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write3
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Oct 22, 2026, 14:44 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- none
- RFC 9728 protected resource metadata
- https://mcp.cron.cool/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://api.authrice.com
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (1 destructive, 1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.cron.cool/mcp: tools/list returned 11 tools to an anonymous client, including run_job (destructive), open_croncool (write)
Install
Pinned to version 0.1.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http croncool https://mcp.cron.cool/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__croncool__list_projects",
"mcp__croncool__list_jobs",
"mcp__croncool__get_job",
"mcp__croncool__get_job_runs",
"mcp__croncool__list_workflows",
"mcp__croncool__list_workflow_runs",
"mcp__croncool__get_workflow_run",
"mcp__croncool__list_webhook_subscriptions",
"mcp__croncool__show_project_overview"
],
"ask": [
"mcp__croncool__open_croncool"
],
"deny": [
"mcp__croncool__run_job"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as croncool. Review it before you use it.
Capability tags behind 3 rules
- mcp__croncool__run_job untrusted-input
- mcp__croncool__get_job_runs untrusted-input
- mcp__croncool__open_croncool untrusted-input