Skip to main content

agent-cronjob

ai.agentasy/cronjobVersion 0.0.1

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

Status

Responds635 msAnswered 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:26 UTC
Latency
635 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://cronjob.agentasy.ai/mcpResponds635 ms
No sign-in

Claude Code

claude mcp add --transport http cronjob https://cronjob.agentasy.ai/mcp

Claude Desktop and claude.ai

Settings > Connectors > Add custom connector
Name: cronjob
Remote MCP server URL: https://cronjob.agentasy.ai/mcp

Cursor

{
  "mcpServers": {
    "cronjob": {
      "url": "https://cronjob.agentasy.ai/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"cronjob","type":"http","url":"https://cronjob.agentasy.ai/mcp"}'

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

Host your own MCP server on run.zero

Tools

15 tools

Tools of agent-cronjob
Read-only
Idempotent
Open world
claim_credentialsStep 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 now; later calls say credentials: "already_issued". (REST: GET /v1/jobs/{id}/verification)NoNoNoNo
create_jobStep 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: reply 2xx {"challenge":"<same>"}) — then call claim_credentials. Or reply 2xx and call verify_challenge with the value (callback). Nothing triggers before verification. (REST: POST /v1/jobs)NoNoNoYes
delete_jobStop the job forever and revoke all its credentials. Cannot be undone. (REST: DELETE /v1/jobs/{id})YesNoYesNo
get_deliveriesTrigger log, newest first: scheduled_at, first attempt time, delay, attempts, status and last response code of each run. since/until (ISO 8601) filter scheduled_at; page with next_cursor. (REST: GET /v1/jobs/{id}/runs)NoYesYesNo
get_jobSettings, status, next_run_at, run_count and credential prefixes of one job (webhook path masked). (REST: GET /v1/jobs/{id})NoYesYesNo
get_runOne run and each delivery attempt: sent_at, response status, duration, error and next retry. (REST: GET /v1/jobs/{id}/runs/{run_id})NoYesYesNo
get_statsOn-time rate, p50/p95 first-attempt delay and success rate over a window (default 24h). (REST: GET /v1/jobs/{id}/stats)NoYesYesNo
list_jobsStatus 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. (REST: GET /v1/jobs/{id} (once per job))NoYesYesNo
pause_jobStop triggering (idempotent). Schedule points while paused are not made up later. (REST: POST /v1/jobs/{id}/pause)NoNoYesNo
resume_jobResume a paused or disabled job from its next schedule point; resets consecutive_failures. (REST: POST /v1/jobs/{id}/resume)NoNoYesNo
retry_challengeRe-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}/verification/retry)NoNoNoYes
rotate_secretNew hmac_secret (SHOWN ONCE, store it now). Until previous.expires_at (grace_sec, default 24 h) triggers carry two v1= signatures, new first. (REST: POST /v1/jobs/{id}/rotate-secret)YesNoNoNo
rotate_tokenNew management_token (SHOWN ONCE, store it now). The old one stops working after grace_sec (default 0 = immediately). (REST: POST /v1/jobs/{id}/rotate-token)YesNoNoNo
update_jobChange a job in place: 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 sent) and/or max_runs. Raising max_runs on a job completed with max_runs_reached reactivates it (next run = next occurrence after now, no catch-up); there is no separate resume for completed jobs. Returns the updated job. (REST: PATCH /v1/jobs/{id})NoNoYesNo
verify_challengeStep 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)NoNoNoNo

Details

Registry status
Active
Published
Nov 3, 2026
Updated
Nov 3, 2026
Repository
Not given
Categories (suggested)
SecuritySuggested 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