# agent-cronjob (remote · cronjob.agentasy.ai)

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

- Trust score: 24/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `cronjob.agentasy.ai`: 24/100 (this document), [markdown](https://verifymcp.io/servers/ai-agentasy-cronjob/cronjob.md), [page](https://verifymcp.io/servers/ai-agentasy-cronjob/cronjob)

## Channel facts

- Endpoint: `https://cronjob.agentasy.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.0.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 60/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint returned HTTP 502.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 5 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the agent-cronjob MCP server?

agent-cronjob is a hosted endpoint at https://cronjob.agentasy.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-agentasy-cronjob": {
      "type": "remote",
      "url": "https://cronjob.agentasy.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-agentasy-cronjob --url 'https://cronjob.agentasy.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-agentasy-cronjob:
    url: "https://cronjob.agentasy.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-agentasy-cronjob": {
      "Transport": "http",
      "Url": "https://cronjob.agentasy.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-agentasy-cronjob -t streamable-http -u 'https://cronjob.agentasy.ai/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 24, −41)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Authorization: fail → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Transport: pass → fail
- [functional regression] Schema quality: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-11-04 (score 65)

First indexed and scored.

## MCP tools (15)

### `create_job` (~397 tokens)

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)

Input parameters:

- `catchup_policy` (string)
- `catchup_window_sec` (integer)
- `max_runs`: Complete after this many dispatched runs; null = unlimited.
- `name` (string|null)
- `outgoing_auth`: Optional header your webhook requires (e.g. a Grok routine webhook that needs Authorization). Sent on the url_verification POST and every trigger; never overrides the X-Cronjob-* headers.
- `payload` (object): Sent unchanged in every trigger (≤ 8 KB).
- `retry_base_sec` (integer)
- `retry_max_attempts` (integer)
- `retry_max_backoff_sec` (integer)
- `schedule` (object, required): Exactly one of {cron, timezone?}, {interval_sec}, {run_at}. Minimum spacing 60 s.
- `signature_in_body` (boolean): Default false. true = every trigger body also carries cronjob_signature {version, timestamp, delivery_id, signatures[], signature} (HMAC over "v1b:{timestamp}:{delivery_id}:" + canonical JSON of the…
- `timeout_ms` (integer)
- `verification_mode` (string): Informational; both answers work. Default echo.
- `webhook_url` (string, required): Public https URL of your agent. It receives the challenge now and the signed triggers later.

### `verify_challenge` (~92 tokens)

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)

Input parameters:

- `challenge` (string, required): The challenge value from the url_verification POST
- `job_id` (string, required): job_<ULID> returned by create_job

### `claim_credentials` (~128 tokens)

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)

Input parameters:

- `job_id` (string, required): job_<ULID> returned by create_job
- `setup_token` (string): act_st_… setup token from create_job. Optional if the MCP HTTP request carries Authorization: Bearer <setup_token>.

### `retry_challenge` (~111 tokens)

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)

Input parameters:

- `job_id` (string, required): job_<ULID> returned by create_job
- `setup_token` (string): act_st_… setup token from create_job. Optional if the MCP HTTP request carries Authorization: Bearer <setup_token>.

### `list_jobs` (~74 tokens)

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

Input parameters:

- `jobs` (array, required)

### `get_job` (~87 tokens)

Get a job

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

Input parameters:

- `job_id` (string, required): job_<ULID> returned by create_job
- `management_token` (string): act_mt_… management token. Optional if the MCP HTTP request carries Authorization: Bearer <management_token>.

### `update_job` (~196 tokens)

Change job settings

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 sent; returns the updated job. (REST: PATCH /v1/jobs/{id})

Input parameters:

- `job_id` (string, required): job_<ULID> returned by create_job
- `management_token` (string): act_mt_… management token. Optional if the MCP HTTP request carries Authorization: Bearer <management_token>.
- `signature_in_body` (boolean): Default false. true = every trigger body also carries cronjob_signature {version, timestamp, delivery_id, signatures[], signature} (HMAC over "v1b:{timestamp}:{delivery_id}:" + canonical JSON of the…

### `pause_job` (~84 tokens)

Pause a job

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

Input parameters:

- `job_id` (string, required): job_<ULID> returned by create_job
- `management_token` (string): act_mt_… management token. Optional if the MCP HTTP request carries Authorization: Bearer <management_token>.

### `resume_job` (~84 tokens)

Resume a job

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

Input parameters:

- `job_id` (string, required): job_<ULID> returned by create_job
- `management_token` (string): act_mt_… management token. Optional if the MCP HTTP request carries Authorization: Bearer <management_token>.

### `delete_job` (~79 tokens)

Delete a job

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

Input parameters:

- `job_id` (string, required): job_<ULID> returned by create_job
- `management_token` (string): act_mt_… management token. Optional if the MCP HTTP request carries Authorization: Bearer <management_token>.

### `get_deliveries` (~148 tokens)

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)

Input parameters:

- `cursor` (string)
- `job_id` (string, required): job_<ULID> returned by create_job
- `limit` (integer)
- `management_token` (string): act_mt_… management token. Optional if the MCP HTTP request carries Authorization: Bearer <management_token>.
- `since` (string)
- `status` (string)
- `until` (string)

### `get_run` (~98 tokens)

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

Input parameters:

- `job_id` (string, required): job_<ULID> returned by create_job
- `management_token` (string): act_mt_… management token. Optional if the MCP HTTP request carries Authorization: Bearer <management_token>.
- `run_id` (string, required)

### `get_stats` (~98 tokens)

Punctuality stats

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

Input parameters:

- `job_id` (string, required): job_<ULID> returned by create_job
- `management_token` (string): act_mt_… management token. Optional if the MCP HTTP request carries Authorization: Bearer <management_token>.
- `window` (string)

### `rotate_secret` (~116 tokens)

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)

Input parameters:

- `grace_sec` (integer)
- `job_id` (string, required): job_<ULID> returned by create_job
- `management_token` (string): act_mt_… management token. Optional if the MCP HTTP request carries Authorization: Bearer <management_token>.

### `rotate_token` (~104 tokens)

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)

Input parameters:

- `grace_sec` (integer)
- `job_id` (string, required): job_<ULID> returned by create_job
- `management_token` (string): act_mt_… management token. Optional if the MCP HTTP request carries Authorization: Bearer <management_token>.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-agentasy-cronjob/cronjob#diagnostics

## Score history

- 2026-11-05: 24
- 2026-11-04: 65

## Common questions

### What is the agent-cronjob MCP server?

agent-cronjob is an MCP server listed in the public MCP registry as ai.agentasy/cronjob. Scheduled, HMAC-signed, retried webhook triggers for AI agents. No account: self-register via tools. This page covers its hosted endpoint (https://cronjob.agentasy.ai/mcp).

### Is the agent-cronjob MCP server safe to use?

agent-cronjob scores 24 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the agent-cronjob MCP server expose?

agent-cronjob exposes 15 tools: create_job, verify_challenge, claim_credentials, retry_challenge, list_jobs, and 10 more. Their descriptions and schemas cost roughly 1,896 tokens of context every time the server is loaded.

### Does the agent-cronjob MCP server require authentication?

Its publisher declares no required credentials for agent-cronjob. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

### Is the agent-cronjob MCP server still maintained?

agent-cronjob is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the agent-cronjob MCP server?

VerifyMCP ran 5 checks on agent-cronjob, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 1 more. 6 items could not be completed, a gap on our side rather than a finding about agent-cronjob: Authorization, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://cronjob.agentasy.ai/mcp
- Website: https://cronjob.agentasy.ai/
- Changelog RSS feed: https://verifymcp.io/servers/ai-agentasy-cronjob/cronjob.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-agentasy-cronjob/cronjob/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/ai-agentasy-cronjob/cronjob.json
- HTML version of this page: https://verifymcp.io/servers/ai-agentasy-cronjob/cronjob