402cron

com.402cron/402cronVersion 1.0.1

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

Status

Responds236 msNov 14, 2026, 13:44 UTCAnswered our handshake without sign-in.

Registry data may be out of date

We could not refresh it, so this page shows the last copy.

Last checked: Nov 14, 2026, 13:44 UTC
Latency: 236 ms
Remotes responding: 1 of 1
Sign-in: No sign-in
Hosting: Hosted outside the EU (detected)
Registry data as of: Nov 14, 2026, 22:14 UTC

Data from the official MCP Registry, checked by run.zero. How we check

Connect

Streamable HTTP

https://402cron.com/mcpResponds236 msNov 14, 2026, 13:44 UTC

No sign-in

Claude Code

claude mcp add --transport http 402cron https://402cron.com/mcp

Claude Desktop and claude.ai

1
2
3

Settings > Connectors > Add custom connector
Name: 402cron
Remote MCP server URL: https://402cron.com/mcp

Cursor

{
  "mcpServers": {
    "402cron": {
      "url": "https://402cron.com/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"402cron","type":"http","url":"https://402cron.com/mcp"}'

Built your own server? run.zero hosts MCP servers on European infrastructure.

Host your own MCP server on run.zero

Tools

16 tools

Tools of 402cron
	Description		Read-only	Idempotent	Open world
`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.	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.	Yes	No	Yes	Yes
`delete_destination`Remove a claimed URL. Refused while a task still points at it — delete the task first.	Remove a claimed URL. Refused while a task still points at it — delete the task first.	Yes	No	Yes	No
`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.	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.	Yes	No	Yes	No
`get_docs`One section of the machine documentation: quickstart, headers, signature, notice, errors, billing or limits. Omit `section` to get the whole document.	One section of the machine documentation: quickstart, headers, signature, notice, errors, billing or limits. Omit `section` to get the whole document.	No	Yes	Yes	No
`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.	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.	No	Yes	Yes	No
`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.	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.	No	Yes	Yes	No
`get_task`A single task: schedule, destination, state, next run, and how many failures in a row it carries.	A single task: schedule, destination, state, next run, and how many failures in a row it carries.	No	Yes	Yes	No
`list_destinations`The URLs you have claimed and whether each is verified. The signing secrets are never shown again.	The URLs you have claimed and whether each is verified. The signing secrets are never shown again.	No	Yes	Yes	No
`list_tasks`Your tasks and their state. Needs your management token as an Authorization header on this connection.	Your tasks and their state. Needs your management token as an Authorization header on this connection.	No	Yes	Yes	No
`pause_task`Stop firing until you resume. Nothing is charged while a task is paused.	Stop firing until you resume. Nothing is charged while a task is paused.	Yes	No	Yes	No
`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. 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.	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. 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.	Yes	No	No	No
`restore_task`Bring a task back from the recycle bin within 30 days. It comes back PAUSED — resume it explicitly.	Bring a task back from the recycle bin within 30 days. It comes back PAUSED — resume it explicitly.	No	No	Yes	No
`resume_task`Start firing again on the schedule. Refused if your balance is empty — buy deliveries first.	Start firing again on the schedule. Refused if your balance is empty — buy deliveries first.	Yes	No	Yes	Yes
`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.	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.	Yes	No	No	Yes
`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.	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.	Yes	No	Yes	Yes
`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 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.	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. Until this passes, no task may point at the destination.	No	No	No	Yes

Details

Registry status: Active
Published: Sep 21, 2026
Updated: Sep 21, 2026
Website: https://402cron.com/⁠ (opens in a new tab)
Repository: https://github.com/402cron/402cron⁠ (opens in a new tab)
Categories (suggested): Knowledge and notesSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
GDPR: Not declared

Are you the operator? Claim this listing