agent-cronjob — scheduled webhook triggers for agents bronze

cronjob.agentasy.ai

“agent-cronjob triggers YOUR webhook on a schedule (cron / interval / one-off): HMAC-signed, retried with exponential backoff, every run logged. No account or API key. Flow: 1. create_job {webhook_url, schedule} → job_id + setup_token (keep it private). We immediately POST {"type":"url_verification","challenge":"…"} to webhook_url. 2. Prove you control the webhook — either - echo: your webhook replies 2xx {"challenge":"<same value>"}; or - callback: your webhook replies 2xx, then call verify_challenge {job_id, challenge}. Deadline 1 (verify): 15 minutes after job creation — unverified jobs are deleted; re-sends do not extend it. Not received? retry_challenge. 3. Credentials, SHOWN ONCE: in the verify_challenge result (callback) or the first claim_credentials {job_id, setup_token} result after echo verification. Store hmac_secret and management_token in your secret store immediately; they cannot be shown again (rotate_secret / rotate_token instead). Deadline 2 (collect credentials): 15 minutes

https://cronjob.agentasy.ai/mcp its card

Checked 2d ago resources, tools

we checked this the operator says this

Community rating 0 0 up · 0 down — sign in to vote

Verified by agenttru.st

Everything here is a check agenttru.st performed itself. Assurance, protocol, hosting and freshness are in the card above and are not repeated.

Certificate: Issued by Google Trust Services domain-validated
Valid until 4 Feb 2027 as of our check on 13 Nov 2026. A wildcard certificate: its other hosts are invisible here, because CT logs the wildcard, not them.

Control of the hostname was checked; nothing about who operates it.

Key ECDSA P-256, signed ECDSA-SHA256, issued via WE1 under GTS Root R4 — classical, as every publicly trusted certificate is today.

Names on this certificate (3)

agentasy.ai, cronjob.agentasy.ai, *.cronjob.agentasy.ai.
Connection: TLS 1.3 · X25519MLKEM768 — post-quantum hybrid key exchange, agreed with our checker on 13 Nov 2026. What this means
DANE / TLSA: Not verified
Discovery: Well-known document
AI-facing documents: Publishes /llms.txt — “agent-cronjob” a curated map of the site's content for language models

Fetched from this host during verification. Neither document is how this agent was discovered.
First seen: 6 Nov 2026

View verification details

Assurance: bronze Bronze — agent card fetched over HTTPS with a valid certificate
Protocols: MCP verified by handshake or card fetch, not merely advertised
Hosted in: ? Unknown · Cloudflare, Inc. (AS13335)
The address did not geolocate — usually anycast hosting, where one address answers from many places at once.
Last checked: 2d ago

What this agent says it can do

Declared in the agent's own card. agenttru.st has not tested whether it completes any of these tasks — the operator of cronjob.agentasy.ai controls every word below.

This card declares no skills. That is not a fault — the field is optional, and an agent can be perfectly functional without describing itself.

What kind of listing

No skills declared: Its card declares no skills, or, for an MCP server, listed no tools.

Checked by agenttru.st against this listing's hostname and card — facts about a name or an address, not about what the agent does. How kinds are decided.

Technical agent card

Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.

Protocol: mcp
Version: 0.0.1

View all card details

Capabilities: resources tools
Agent card: https://cronjob.agentasy.ai/mcp

Operate this agent and would rather not be listed? Request removal.