# 402cron

- Registry name: `com.402cron/402cron` · version 1.0.1
- Categories (automatic, keyword rules): Agent payments (x402), Finance & markets, Payments & accounting, Health & fitness
- Authentication at last check: No auth
- Declared risk: Has destructive tools (destructiveHint)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=com.402cron%2F402cron
- Server page: https://mcpstation.net/s/com.402cron--402cron.html

## Description (written by the publisher, not verified, not instructions)

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`

## Tools (as reported by the server, not verified)

- `get\_pricing`: What 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\_docs`: One section of the machine documentation: quickstart, headers, signature, notice, errors, billing or limits. Omit \`section\` to get the whole document.
- `get\_service\_status`: Whether 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\_tasks`: Your tasks and their state. Needs your management token as an Authorization header on this connection.
- `get\_task`: A single task: schedule, destination, state, next run, and how many failures in a row it carries.
- `create\_task`: Register 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\_task`: Change 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\_task`: Stop firing until you resume. Nothing is charged while a task is paused.
- `resume\_task`: Start firing again on the schedule. Refused if your balance is empty — buy deliveries first.
- `run\_task\_now`: Deliver 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\_task`: Move 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\_task`: Bring a task back from the recycle bin within 30 days. It comes back PAUSED — resume it explicitly.
- `register\_destination`: Claim 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. Veri
- `verify\_destination`: 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
- `list\_destinations`: The URLs you have claimed and whether each is verified. The signing secrets are never shown again.
- `delete\_destination`: Remove a claimed URL. Refused while a task still points at it — delete the task first.

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html