402cron

What 402cron does

The 402cron MCP server lets AI agents create and manage recurring HTTP delivery tasks. Each task associates a UTC cron schedule with a verified HTTPS destination, then sends requests when the schedule fires. Requests include an HMAC signature so the receiving application can check that the delivery came from 402cron.

The service is hosted and accessed remotely through Streamable HTTP at https://402cron.com/mcp. It also provides a REST interface. Management operations use a bearer token, while delivery usage is paid with prepaid x402 credits in USDC on Base. Credits are measured in delivery attempts rather than monetary units, and purchased packs do not expire.

How it works

Before creating a task, claim the destination URL and complete verification. Registration sends a challenge and reveals a signing secret once. The receiving endpoint must answer the verification request within five seconds, without redirecting, and the verification API call must follow within 15 minutes. A destination grants access to its registered path and everything below that path, but not to a parent path.

After verification, create a task with a name, schedule, destination, and delivery settings. Names are idempotent: creating a task with an existing name updates that task instead of making a duplicate. Scheduled delivery attempts consume credits. An immediate test through run_task_now also costs one credit per attempt and may consume up to three credits when retries are needed.

Setup and configuration

Connect an MCP client to the remote endpoint and provide the management bearer token as the connection's Authorization header where required. Use get_pricing before purchasing credits to inspect available packs and the exact x402 payment requirements. get_service_status reports whether sales are enabled and which network is configured; it is not the service health check.

The receiving endpoint must be programmable. During verification, it receives a POST containing the challenge in both a header and JSON body. It must return either the bare challenge or an object containing that value in the response body. Fixed-response webhook services cannot complete this process.

Tools and capabilities

The 402cron MCP server provides tools for the complete task lifecycle:

• Inspect pricing, documentation sections, service configuration, tasks, individual task state, and claimed destinations.
• Register, verify, list, and delete HTTPS destinations.
• Create, update, pause, resume, run immediately, delete, and restore scheduled tasks.
• Change a task's schedule, destination, method, timeout, headers, or body with update_task.
• Restore deleted tasks for up to 30 days; restored tasks return paused and require an explicit resume.

Task creation is free, but each delivery attempt is billed. Pausing a task stops firing and does not consume credits.

Limitations and notes

A destination cannot be removed while a task still references it. Deleting a task stops delivery immediately and moves it to a recycle bin; after 30 days it cannot be recovered, and spent credits are not refunded.

Registering a pending destination again creates a new challenge and signing secret, invalidating the old secret. Verified destinations remain unchanged unless rotation is explicitly requested. Verification is limited to 10 attempts per destination and 40 per client per UTC day, and re-registration does not reset those allowances.

The signing secret is shown only during registration. Store it before continuing, because the service does not display it again. A task cannot point to an unverified destination, and resume_task is refused when the credit balance is empty.