agent-cronjob

ai.agentasy由 agentasy.ai 发布官方发布者v0.0.1更新于 Nov 4, 2026

面向 AI 智能体的定时、HMAC 签名、可重试的 webhook 触发器。无需账户:通过工具自行注册。

AI 翻译由 AI 模型根据下方的原文描述翻译,可能有误。

原文描述

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

已验证Streamable HTTP可网页运行AI 与机器学习

概览

agent-cronjob 的托管 MCP 服务(cronjob.agentasy.ai),由 agentasy.ai 发布;无需登录;Streamable HTTP;15 个工具。

暂无 AI 概览:以下信息来自注册中心条目和服务本身。

发布者
agentasy.ai
端点
cronjob.agentasy.ai
最近检查

安装

在 SourceWeft 中

  1. 打开 控制台中的 agent-cronjob,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/ai.agentasy%2Fcronjob/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

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

工具

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)

输入参数namepayloadmax_runsschedule必填timeout_mswebhook_url必填outgoing_authcatchup_policyretry_base_secsignature_in_bodyverification_modecatchup_window_sec另有 2 个

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)

输入参数job_id必填challenge必填

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)

输入参数job_id必填setup_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)

输入参数job_id必填setup_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))

输入参数jobs必填

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

输入参数job_id必填management_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})

输入参数job_id必填max_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)

输入参数job_id必填management_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)

输入参数job_id必填management_token

delete_job

Delete a job

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

输入参数job_id必填management_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)

输入参数limitsinceuntilcursorjob_id必填statusmanagement_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})

输入参数job_id必填run_id必填management_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)

输入参数job_id必填windowmanagement_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)

输入参数job_id必填grace_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)

输入参数job_id必填grace_secmanagement_token

版本历史

1
  1. v0.0.1最新Nov 3, 2026

评分

已满足适用检查项的 83%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分

    请声明包含 README 的 GitHub 仓库,或在 OAuth 受保护资源元数据中提供 resource_documentation。

  • 许可证不适用

    托管服务按其提供方的条款使用,因此这里不要求许可证。此检查项不计入百分比。