All servers / AI / 402cron
402cron
Paid cron for AI agents: we call your https URL on schedule, signed. No account, paid with x402.
Tested by ConnectATD Hosted serverTested 2026-11-22. Address: https://402cron.com/mcp · Registry name: com.402cron/402cron
Score 100 out of 100. Tested 2026-11-22.
Score breakdown
| Connects and stays up | 20 / 20 | |
|---|---|---|
| Tool descriptions | 20 / 20 | |
| Inputs explained | 15 / 15 | |
| Speed | 15 / 15 | |
| Safety basics | 15 / 15 | |
| Upkeep | 15 / 15 |
What we saw
- Connects and answers the MCP handshake: yes (0.2 seconds)
- Uses an encrypted (https) connection: yes
- Server reports itself as: 402cron 1.0.0
- Tools offered: 16 · Parameters with a plain description: 28 of 28
- One safe, read-only test call to
get_pricing: worked (first call 0.0 seconds, repeat calls 0.0 seconds) - Official registry entry last updated: 2026-11-17
From the publisher
- No notes.
How hosted servers are graded
Hosted servers run on the publisher's own machines, so we cannot score downloads or install safety. We use six checks instead (connects and stays up 20, tool descriptions 20, inputs explained 15, speed 15, safety basics 15, upkeep 15). Speed is the first call to a safe, read-only tool (when a server marks none, the time to connect and list its tools), using a fresh request where we can so a saved answer cannot hide a slow one. We never call tools that write data or cost money. A server that needs a login or key is not graded. Full method.
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions.
get_pricingno parametersWhat 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_docs1 of 1 parameter describedOne section of the machine documentation: quickstart, headers, signature, notice, errors, billing or limits. Omit `section` to get the whole document.
get_service_statusno parametersWhether 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_tasks3 of 3 parameters describedYour tasks and their state. Needs your management token as an Authorization header on this connection.
get_task1 of 1 parameter describedA single task: schedule, destination, state, next run, and how many failures in a row it carries.
create_task7 of 7 parameters describedRegister 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_task8 of 8 parameters describedChange 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_task1 of 1 parameter describedStop firing until you resume. Nothing is charged while a task is paused.
resume_task1 of 1 parameter describedStart firing again on the schedule. Refused if your balance is empty — buy deliveries first.
run_task_now1 of 1 parameter describedDeliver 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_task1 of 1 parameter describedMove 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_task1 of 1 parameter describedBring a task back from the recycle bin within 30 days. It comes back PAUSED — resume it explicitly.
register_destination1 of 1 parameter describedClaim 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.
verify_destination1 of 1 parameter describedVerification 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.
list_destinationsno parametersThe URLs you have claimed and whether each is verified. The signing secrets are never shown again.
delete_destination1 of 1 parameter describedRemove a claimed URL. Refused while a task still points at it — delete the task first.
Tested by ConnectATD. Spotted a mistake? Tell us.