Back to search
100
MCP live MCP 2025-11-25 streamable-http

agent-cronjob

ai.agentasy/cronjob

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

Website ↗
Watch this dependency Share evidence report
Uptime
50.0%
2 direct probes · 30d
Response
766ms
last probe
Tools
15
callable
Resources
1
readable
Prompts
0
available
Primary URL
https://cronjob.agentasy.ai/mcp
Score: 100/100
Handshake verified by our own probe.
pass Answers the MCP handshake 50/50
The handshake and the list calls succeeded on the primary URL.
pass Lists tools, resources or prompts 30/30
15 tools, 1 resources, 0 prompts returned.
pass 3 or more catalogue items 10/10
16 items in total; 3 or more earns these points.
pass Describes itself 10/10
100 characters; more than 30 earns these points.

Tools · 15

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

pause_job

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

resume_job

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

delete_job

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

get_deliveries

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 /…

get_run

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

get_stats

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

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

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

Resources · 1

how_it_works

Complete agent guide: flow, verification, signature, retries, limits, errors.

https://cronjob.agentasy.ai/llms.txt

How to use

Claude Desktop or claude.ai: add a custom connector (Customize → Connectors; on Team and Enterprise plans an owner adds it under Organization settings → Connectors) with this server URL: https://cronjob.agentasy.ai/mcp

Cursor or Cline: add to your MCP config:

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