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。

  • 授權條款不適用

    託管服務按其提供方的條款使用,因此這裡不要求授權條款。此檢查項不計入百分比。