agent-cronjob MCP Server

by agentasy Your server? Claim it

answering

agent-cronjob is answering right now. Last checked 9 min ago. It exposes 15 tools.

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

Uptime history 6 days of history · worst day 35%

6 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

411 ms

Response time

average over 24h

open, no key

Access

streamable-http

agent-cronjob does not always answer

Over the last week it answered 79.6% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

Settings → Connectors → Add custom connector, then paste this address

https://cronjob.agentasy.ai/mcp

~/.codex/config.toml

[mcp_servers.cronjob]
url = "https://cronjob.agentasy.ai/mcp"

.cursor/mcp.json

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

.vscode/mcp.json

{
  "servers": {
    "cronjob": {
      "type": "http",
      "url": "https://cronjob.agentasy.ai/mcp"
    }
  }
}

Available tools 15

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

job

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

delete_job

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

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

rotate

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)

claim

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

deliveries

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 /v1/jobs/{id}/runs)

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

jobs

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

pause

pause_job

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

resume

resume_job

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

retry

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

stats

get_stats

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

verify

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)

Endpoints

URL	Transport	State	Latency	Checked
https://cronjob.agentasy.ai/mcp	streamable-http	answering	309 ms	9 min ago

Alternatives to agent-cronjob

same job, measured the same way

402cron

by 402cron

Paid cron for AI agents: we call your https URL on schedule, signed. No account, paid with x402.

16 tools answering

Webhook AI MCP

by csoai-org

Webhook Ai tools for AI agents. Capabilities: validate webhook signature, log webhook event, replay

156 installs/wk local only

AgentCron

by noriget

Schedule tasks for later from your AI agent: reminders, delayed webhooks, recurring jobs.

answering

AgentScrape

by hshintelligence

Pay-per-call web scraping for AI agents via x402 on Base USDC. Six tools, no signup.

6 tools answering

Pingfyr

by pingfyr

Schedule reminders for AI agents via email, webhook, Slack, Discord, Telegram, or Google Calendar.

answering

Cryptyx MCP Server

by cryptyx-ai

Institutional crypto intelligence for agents. 30 tools: signals, backtests, regime, triggers.

48 installs/wk local only

Otterkit

by useotterkit

Tunnels and webhooks for AI agents: capture, await, verify, replay, and send signed test events.

62 installs/wk local only

The Agent Lounge

by kphatak001

A guestbook for AI agents: read what other agents wrote, sign it yourself, and check the counters.

3 tools answering

agent-cronjob — questions

Answers built from our own checks of this server.

What can agent-cronjob do?

It exposes 15 tools, read directly from the server on our last check. Among them: claim_credentials, create_job, delete_job, get_deliveries, get_job, get_run and 9 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is agent-cronjob mostly used for?

Its tools cluster around job and rotate. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is agent-cronjob working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 411 ms. The bar chart above shows every period we have measured.

How do I connect agent-cronjob?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does agent-cronjob need an API key?

No. agent-cronjob completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 15 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is agent-cronjob?

It answers our handshake in 411 ms on average, which is faster than 31% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.