← All launches
0 Report

agent-cronjob

by FastDrop

MCP Verified 2 hours ago Registry import free

Scheduled, HMAC-signed, retried webhook triggers for AI agents. No account: self-register via tools.

Scheduled, HMAC-signed, retried webhook triggers for AI agents. No account: self-register via tools. Official MCP Registry: ai.agentasy/cronjob@0.0.1. Remote endpoint: https://cronjob.agentasy.ai/mcp

Problem it solves

Discoverable MCP server listed in the official MCP Registry.

How it's different

Remote MCP endpoint ingested from the official registry and probed by FastDrop.

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as ai.agentasy/cronjob and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Claim this listing

Tools this endpoint exposes

Read directly from the endpoint on 4 Nov 2026. Not supplied by the maker.

  • create_job

    Step 1. Register your webhook and schedule (no account, no API key). Returns job_id and a one-time setup_token, and POSTs a url_verification challenge to webhook_url. Your webhook must answer it (echo

  • verify_challenge

    Step 2 (callback mode). Send back the challenge value your webhook received. On success the result holds hmac_secret and management_token — SHOWN ONCE, store them now. (REST: POST /v1/jobs/{id}/verify

  • claim_credentials

    Step 3. Poll verification state with the setup_token. The first call after the webhook is verified returns hmac_secret (signs triggers) and management_token (manages the job) — SHOWN ONCE, store them

  • retry_challenge

    Re-send a fresh url_verification challenge to your webhook (at most 5 re-sends (6 challenges in total), at least 60 s apart). The previous challenge stops working. (REST: POST /v1/jobs/{id}/verificati

  • list_jobs

    Status of every job you hold a management token for. There are no accounts, so pass each {job_id, management_token} pair (up to 20); a pair without management_token uses the Authorization header. (RES

  • get_job

    Settings, status, next_run_at, run_count and credential prefixes of one job (webhook path masked). (REST: GET /v1/jobs/{id})

  • update_job

    Change a job in place. Currently only signature_in_body (true = triggers also carry cronjob_signature in the JSON body, for platforms that drop the X-Cronjob-* headers). Applies from the next attempt

  • pause_job

    Stop triggering (idempotent). Schedule points while paused are not made up later. (REST: POST /v1/jobs/{id}/pause)

Is this tool yours?

Claim this listing, then prove you own the domain with one DNS record: once it matches, the listing is yours right away.

Sign in to claim this listing

Matched on shared tags and the tools their MCP servers actually expose.

Reviews

Sign in to leave a review.

No reviews yet.

Comments

Sign in to join the discussion.

No comments yet - start the discussion.