agent-cronjob

ai.agentasyPublished by agentasy.aiOfficial publisherv0.0.1Updated Nov 4, 2026

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

VerifiedStreamable HTTPWeb executableAI & ML

Overview

agent-cronjob's hosted MCP server (cronjob.agentasy.ai), published by agentasy.ai; no sign-in required; Streamable HTTP; 15 tools.

No AI overview yet: these facts come from the registry entry and the server itself.

Publisher
agentasy.ai
Endpoint
cronjob.agentasy.ai
Last checked

Installation

In SourceWeft

  1. Open agent-cronjob in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.agentasy%2Fcronjob/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "agent-cronjob": {
      "type": "http",
      "url": "https://cronjob.agentasy.ai/mcp"
    }
  }
}

Tools

15

create_job

Create a job (start registration)

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: 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)

Parametersnamepayloadmax_runsschedulerequiredtimeout_mswebhook_urlrequiredoutgoing_authcatchup_policyretry_base_secsignature_in_bodyverification_modecatchup_window_sec+2 more

verify_challenge

Verify the challenge (callback mode)

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)

Parametersjob_idrequiredchallengerequired

claim_credentials

Poll verification / collect 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 now; later calls say credentials: "already_issued". (REST: GET /v1/jobs/{id}/verification)

Parametersjob_idrequiredsetup_token

retry_challenge

Re-send the 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}/verification/retry)

Parametersjob_idrequiredsetup_token

list_jobs

List your 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. (REST: GET /v1/jobs/{id} (once per job))

Parametersjobsrequired

get_job

Get a job

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

Parametersjob_idrequiredmanagement_token

update_job

Change job settings

Change 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})

Parametersjob_idrequiredmax_runsmanagement_tokensignature_in_body

pause_job

Pause a job

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

Parametersjob_idrequiredmanagement_token

resume_job

Resume a job

Resume a paused or disabled job from its next schedule point; resets consecutive_failures. (REST: POST /v1/jobs/{id}/resume)

Parametersjob_idrequiredmanagement_token

delete_job

Delete a job

Stop the job forever and revoke all its credentials. Cannot be undone. (REST: DELETE /v1/jobs/{id})

Parametersjob_idrequiredmanagement_token

get_deliveries

Run history

Trigger 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)

Parameterslimitsinceuntilcursorjob_idrequiredstatusmanagement_token

get_run

One run with every delivery attempt

One run and each delivery attempt: sent_at, response status, duration, error and next retry. (REST: GET /v1/jobs/{id}/runs/{run_id})

Parametersjob_idrequiredrun_idrequiredmanagement_token

get_stats

Punctuality stats

On-time rate, p50/p95 first-attempt delay and success rate over a window (default 24h). (REST: GET /v1/jobs/{id}/stats)

Parametersjob_idrequiredwindowmanagement_token

rotate_secret

Rotate the HMAC signing secret

New 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)

Parametersjob_idrequiredgrace_secmanagement_token

rotate_token

Rotate the management token

New 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)

Parametersjob_idrequiredgrace_secmanagement_token

Version history

1
  1. v0.0.1LatestNov 3, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.