Datoka Hooks

dev.workers.bhazarstudio.datoka-hooks-test由 datoka-hooks-test.bhazarstudio.workers.dev 发布v0.7.6更新于 Oct 24, 2026

Public webhook relay with signed observations, retries and verified receivers. Self-service.

已验证Streamable HTTP可网页运行开发者工具安全与监控

概览

AI 生成的概览

一个远程 webhook 中继,让助手注册已验证的 HTTPS 接收端、入队事件、购买投递额度并查看签名回执。

可以做什么
Datoka Hooks 是一个远程 webhook 中继。工具可让助手注册自己控制的 HTTPS 接收端,发布所有权挑战并验证目标,然后入队最大 65536 字节的事件负载,并轮询排队、重试或已完成的投递状态。它还能读取剩余准入额度、请求 x402 报价或用已签名的付款购买额度、查询目标状态、验证签名回执,以及永久吊销某个 hook。
适用场景
当助手需要通过带重试、所有权验证和签名投递记录的中继,把事件推送到自己控制的 HTTPS 端点时使用;也适合查看和管理已有 hook 的额度、状态与投递情况。
运行要求
以远程 streamable HTTP 端点运行,无需本地包或运行时。传输层未声明认证,但各工具需要 hook 管理令牌或投递令牌,注册会返回 hookId、私有凭据和 recoveryKey。购买额度涉及 x402 付款。需要能访问该端点以及你自己的 HTTPS 接收端。
安装前请注意
购买额度会通过 x402 签名付款产生费用,应先请求报价,超时后复用 purchaseId。注册会返回私有凭据和 recoveryKey,必须保密。吊销目标是永久操作且不可撤销,也不会取消已排队的事件。签名回执只证明中继尝试,不代表业务处理成功或恰好一次投递。事件负载会发送给第三方中继。

安装

在 SourceWeft 中

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

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

交给智能体安装

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

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

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

其他 MCP 客户端

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

{
  "mcpServers": {
    "datoka-hooks": {
      "type": "http",
      "url": "https://datoka-hooks.bhazarstudio.workers.dev/mcp"
    }
  }
}

工具

9

get_hook_credits

Get Hook Credits

Read remaining purchased admission credits for an existing hook using its management token. Free and read-only; does not purchase credits. Use purchase_hook_credits to request a quote. The daily free allowance remains separate.

输入参数hookId必填managementToken必填

purchase_hook_credits

Purchase Hook Credits

Request an x402 quote without payment, or buy credits with an explicitly authorized signed payment. Reuse purchaseId and the same payment after any timeout.

输入参数hookId必填paymentpurchaseId必填managementToken必填

register_destination

Register Destination

Register an HTTPS receiver you control. Returns hookId, private credentials and the ownership challenge; delivery remains inactive. Publish the exact challenge on your origin, then call verify_destination. Keep recoveryKey secret and reuse it with the identical target after interruption; do not register again with a new key.

输入参数target必填recoveryKey必填

verify_destination

Verify Destination

Fetch the ownership challenge from the previously registered receiver and activate it when valid. First publish the exact challenge returned by register_destination. Requires the management token; does not deliver an event. Use get_destination_status to inspect progress without activation.

输入参数hookId必填managementToken必填

get_destination_status

Get Destination Status

Read the existing hook ownership challenge and verification or revocation status using its management token. No activation or delivery. Use after registration or an interrupted verification; use get_hook_delivery for one accepted event.

输入参数hookId必填managementToken必填

revoke_destination

Revoke Destination

Permanently revoke this hook with its management token after explicit owner approval. New submissions are rejected; previously accepted deliveries finish. This does not cancel queued events and cannot be undone. Use get_destination_status first if you only need to inspect access.

输入参数hookId必填managementToken必填

accept_hook_event

Accept Hook Event

Enqueue up to 65536 payload bytes for a previously verified receiver using its delivery token. Returns a deliveryId, not proof of delivery. Reuse eventId and exact bytes on retries, then poll get_hook_delivery. The free allowance is 100 events/day per verified receiver; extra admissions consume purchased credits. No arbitrary destination can be supplied here.

输入参数token必填hookId必填eventId必填bodyBase64必填contentType必填

get_hook_delivery

Get Hook Delivery

Read one accepted event by its returned deliveryId and hook delivery token. Poll after accept_hook_event to distinguish queued, retried and completed delivery. Signed observations attest relay attempts, not successful business processing by the receiver. No new delivery or payment.

输入参数token必填hookId必填deliveryId必填

verify_hook_receipt

Verify Hook Receipt

Check an unchanged event and signed receipt returned by get_hook_delivery within the authenticated hook. Requires the delivery token; does not send an event. A valid signature attests relay observations, not business truth or exactly-once processing.

输入参数event必填token必填hookId必填receipt必填

版本历史

4
  1. v0.7.6最新Oct 4, 2026
  2. v0.7.4Oct 2, 2026
  3. v0.7.1Oct 1, 2026
  4. v0.4.0Sep 29, 2026

评分

已满足适用检查项的 72%

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

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

    请在注册中心条目中发布图标。

  • 文档15 分

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

  • 许可证不适用

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