# cool.cron/croncool

Inspect scheduled jobs, runs, durable workflows, and webhook health; run one confirmed job.

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the content rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 0.1.0
- **Author:** cool.cron
- **License:** Unknown
- **Endpoints:** streamable-http https://mcp.cron.cool/mcp
- **Source:** https://www.cron.cool/developers/#mcp
- **Endpoint health:** reachable (last checked 2026-09-25T21:50:06.663Z, 5 samples) — uptime is not a security property and is not part of the trust score
- **Compatible clients:** claude-code, cursor, copilot, chatgpt, gemini (basis: transport)

## Trust

60/100 (B), scored on the content rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: clean
- Obfuscation scan: clean
- Evidence age: 0 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-25T21:50:06.663Z
- **Version scanned:** live
- **CVEs:** no coverage — this entry has no package coordinates to query OSV against, so "no known CVEs" is NOT asserted for it.

## Tools

10 declared. Observed from a live `tools/list` probe.
- `list_projects` — List a bounded set of Croncool projects the authenticated user can access. Returns only the project id needed for follow-up calls, display name, and creation ti
- `list_jobs` — List a bounded page of Croncool jobs in the authenticated organization, optionally filtered by exact project id. Returns safe scheduling metadata and target ori
- `get_job` — Fetch a single Croncool cron job by exact id. Returns safe scheduling metadata and only the target HTTP(S) origin; request payloads and credential-bearing URL p
- `run_job` — Trigger one existing Croncool job by exact id immediately, outside its schedule. This is destructive under host review policy, open-world, and non-idempotent: e
- `get_job_runs` — Fetch a bounded execution history for one exact Croncool job id, most recent first. Returns execution id, status, HTTP status, duration, and timestamp only; res
- `list_workflows` — List a bounded set of durable workflows for one exact Croncool project id with per-status run counts and most recent run time. Workflow inputs, outputs, error m
- `list_workflow_runs` — List a bounded page of durable workflow runs for one exact Croncool project id, optionally filtered by workflow name and status. Returns only run identity, stat
- `get_workflow_run` — Fetch one durable workflow run by exact project id and run id together with a bounded set of steps. Returns status/timing metadata and machine error codes only;
- `list_webhook_subscriptions` — List a bounded set of webhook delivery-health records in the authenticated Croncool organization, optionally filtered by exact project id. Returns endpoint orig
- `show_project_overview` — Render a bounded overview for one known Croncool project id. Use after list_projects. Shows safe project metadata and up to 12 tenant-scoped jobs with target or

## Install

**Verdict: review** — Installable, but 2 things to check first: No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
**Cautions** (coverage gaps and advisories — never blocking)
- No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"croncool\": {\n      \"type\": \"http\",\n      \"url\": \"https://mcp.cron.cool/mcp\"\n    }\n  }\n}"
```

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on someone else's infrastructure; read-only tool surface.
- Floor 9, ceiling 27 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/cool.cron%2Fcroncool
- Install plan: https://forgeregistry.com/api/v1/packages/cool.cron%2Fcroncool/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/cool.cron%2Fcroncool
- HTML page: https://forgeregistry.com/registry/cool.cron%2Fcroncool
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.