Is there a 402cron MCP server?

You don't need an MCP server to give your agent 402cron. Jentic connects it directly from the API Directory: import 402cron, store your token once, and your agent schedules and tracks deliveries straight away. That keeps your agent's context free of an extra server's tool definitions, since operations are discovered on demand.

Can I limit what my agent is allowed to do with the 402cron API?

Yes. Because the task id travels in the URL path, you can write a rule that allows only the create-task and run-now operations for one task, so the agent can schedule and trigger deliveries for that task and nothing else. Deleting tasks or removing destinations stays out of the rule unless you add it, and every call the agent makes is logged.

Can I schedule recurring deliveries with the 402cron API?

Yes. Create a task with a cron timetable and 402cron delivers to your verified destination on that schedule, retrying an unreachable host up to three attempts in total. You can also run a task once immediately without touching its schedule, pause and resume it, and read its failure counters and next run times at any point.

What are the rate limits for the 402cron API?

The 402cron OpenAPI spec does not publish request rate limits. What it does bound is delivery: a failing cycle is attempted at most three times in total, so one unreachable destination costs at most three credits. Check the 402cron documentation at https://402cron.com/docs for any current request limits.

How do I schedule a delivery with the 402cron API through Jentic?

Search the Jentic API Directory for an intent like 'schedule a recurring HTTP delivery', import 402cron, and store your bearer token once. Your agent then registers a destination, verifies it, and creates a task pointing at that URL by calling the create-task and run-now operations through Jentic. To run it on your own infrastructure, install Jentic One from its GitHub repo.