All servers · Agent payments (x402) · Payments & accounting · Health & fitness
402cron
com.402cron/402cron · v1.0.1
Has write/delete tools
Measured by MCP Station
| Last check | Reachable |
|---|---|
| Checked at | — |
| Check success 7 / 30 days | — |
| First-try success 30 days | — |
| Median response | — |
| Lookups 30 days | — |
| Authentication | No auth |
| MCP version | 2025-06-18 |
| Rank score | — |
| Declared risk | Has destructive tools (destructiveHint) |
| Capabilities declared | tools |
| Tool definitions | 16 tools · with description 100% · input schema is an object 100% · read/destructive hints 100% |
Description written by the publisher, not verified
Paid cron for AI agents: we call your https URL on schedule, signed. No account, paid with x402.
Connect
streamable-http · https://402cron.com/mcp
claude mcp add --transport http 402cron https://402cron.com/mcp{
"mcpServers": {
"402cron": {
"url": "https://402cron.com/mcp"
}
}
}Tools as reported by the server
get_pricingWhat a delivery costs, which packs exist, and the exact x402 payment requirements for each. Balance is counted in DELIVERIES, not money, and packs never expire. Call this before buying.get_docsOne section of the machine documentation: quickstart, headers, signature, notice, errors, billing or limits. Omit `section` to get the whole document.get_service_statusWhether the service is currently selling, on which network, and if not — why not. This is configuration, not liveness: the full health endpoint is at /health.list_tasksYour tasks and their state. Needs your management token as an Authorization header on this connection.get_taskA single task: schedule, destination, state, next run, and how many failures in a row it carries.create_taskwrite/deleteRegister a schedule against a destination you have already verified. Idempotent on "name": the same name updates the existing task instead of creating a second one. Creating costs nothing; each delivery ATTEMPT costs one credit.update_taskwrite/deleteChange the schedule, destination, method, timeout, headers or body of an existing task. Omit a field to leave it unchanged — sending null is refused, because "unchanged" and "cleared" must not look the same. State is NOT editable here: use pause_task and resume_task.pause_taskwrite/deleteStop firing until you resume. Nothing is charged while a task is paused.resume_taskwrite/deleteStart firing again on the schedule. Refused if your balance is empty — buy deliveries first.run_task_nowwrite/deleteDeliver immediately, outside the schedule. THIS COSTS ONE CREDIT per attempt, exactly like a scheduled firing, and a timeout or unreachable host is retried up to three times — so one call can cost up to three credits. Use it to test a destination.delete_taskwrite/deleteMove the task to the recycle bin. It stops firing immediately and can be restored for 30 days with restore_task; after that it is unrecoverable. Credits already spent are not refunded.restore_taskBring a task back from the recycle bin within 30 days. It comes back PAUSED — resume it explicitly.register_destinationwrite/deleteClaim an https:// URL you control. We answer with a challenge and a SIGNING SECRET that is shown ONCE and never again — store it before you do anything else; it is what lets you verify that a delivery really came from us. The permission covers that path and everything beneath it, nothing above. Veriverify_destinationVerification is one request from us to the exact URL you registered: POST, headers X-402cron-Challenge: <value> and X-402cron-Event: verify, JSON body {"challenge":"<value>"}. Reply within 5 seconds, without a redirect, with a body that is the bare value or {"challenge":"<value>"}; we read the firstlist_destinationsThe URLs you have claimed and whether each is verified. The signing secrets are never shown again.delete_destinationwrite/deleteRemove a claimed URL. Refused while a task still points at it — delete the task first.
Repository · Website · JSON · Text for agents · Registry updated 2026-09-21