Skip to content
MCP server

402cron

By 402cronAll 402cron servers

Paid cron for AI agents: we call your https URL on schedule, signed. No account, paid with x402.

First seen 2 Oct 2026. One server, whatever directories list it: each directory listing keeps its own page and history.

2
Directories
Collected by InvokeRank
16
Tools
From an anonymous probe
-
ToolBench grade
Not graded by Arcade
0
GitHub stars
From MCP Toplist

Tools

ToolDescriptionBehaviour
create_taskRegister 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.Not declared
delete_destinationRemove a claimed URL. Refused while a task still points at it — delete the task first.Not declared
delete_taskMove 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.Not declared
get_docsOne section of the machine documentation: quickstart, headers, signature, notice, errors, billing or limits. Omit `section` to get the whole document.Not declared
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.Not declared
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.Not declared
get_taskA single task: schedule, destination, state, next run, and how many failures in a row it carries.Not declared
list_destinationsThe URLs you have claimed and whether each is verified. The signing secrets are never shown again.Not declared
list_tasksYour tasks and their state. Needs your management token as an Authorization header on this connection.Not declared
pause_taskStop firing until you resume. Nothing is charged while a task is paused.Not declared
register_destinationClaim 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. Verification 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 first 512 bytes and do not check the HTTP status (2xx is fine). Then call POST /api/destinations/{id}/verify within 15 minutes of registering. A fixed-response webhook cannot pass: you need an endpoint you can program. Registering a URL that is still pending issues a new challenge and a new signing secret every time — the old secret immediately stops verifying deliveries; a verified URL is left untouched unless you add ?rotate=1. The daily verification allowance (10 per destination, 40 per client, UTC day) does not reset on re-registration.Not declared
restore_taskBring a task back from the recycle bin within 30 days. It comes back PAUSED — resume it explicitly.Not declared
resume_taskStart firing again on the schedule. Refused if your balance is empty — buy deliveries first.Not declared
run_task_nowDeliver 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.Not declared
update_taskChange 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.Not declared
verify_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 first 512 bytes and do not check the HTTP status (2xx is fine). Then call POST /api/destinations/{id}/verify within 15 minutes of registering. A fixed-response webhook cannot pass: you need an endpoint you can program. Registering a URL that is still pending issues a new challenge and a new signing secret every time — the old secret immediately stops verifying deliveries; a verified URL is left untouched unless you add ?rotate=1. The daily verification allowance (10 per destination, 40 per client, UTC day) does not reset on re-registration. Until this passes, no task may point at the destination.Not declared

Directory listings

DirectoryListingTierFirst seen
Official MCP Registry402cron-2 Oct 2026
Smithery402cron-2 Oct 2026