Datoka Hooks

dev.workers.bhazarstudio.datoka-hooks-testPublished by datoka-hooks-test.bhazarstudio.workers.devv0.7.6Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

A remote webhook relay that lets an assistant register verified HTTPS receivers, enqueue events, buy delivery credits and check signed delivery receipts.

What you can do
Datoka Hooks is a remote webhook relay. Tools let an assistant register an HTTPS receiver it controls, publish an ownership challenge and verify the destination, then enqueue event payloads of up to 65536 bytes and poll for queued, retried or completed delivery. It also reads remaining admission credits, requests x402 quotes or buys credits with a signed payment, checks destination status, verifies signed receipts, and permanently revokes a hook.
When to use it
Use it when an assistant needs to push events to an HTTPS endpoint it controls through a relay with retries, ownership verification and signed delivery observations, or when you want to inspect and manage an existing hook's credits, status and deliveries.
Requirements
Runs as a remote streamable HTTP endpoint; no local package or runtime is needed. No authentication is declared at the transport level, but tools require a hook management token or delivery token, and registration returns a hookId, private credentials and a recoveryKey. Purchasing credits involves an x402 payment. Network access to the endpoint and to your own HTTPS receiver is required.
Before you install
Purchasing credits spends money through an x402 signed payment; request a quote first and reuse the purchaseId after a timeout. Registration returns private credentials and a recoveryKey that must be kept secret. Revoking a destination is permanent and cannot be undone, and does not cancel queued events. Signed receipts attest relay attempts only, not successful processing or exactly-once delivery. Event payloads are sent to a third-party relay.

Installation

In SourceWeft

  1. Open Datoka Hooks in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.workers.bhazarstudio.datoka-hooks-test%2Fdatoka-hooks/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

Tools

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.

ParametershookIdrequiredmanagementTokenrequired

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.

ParametershookIdrequiredpaymentpurchaseIdrequiredmanagementTokenrequired

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.

ParameterstargetrequiredrecoveryKeyrequired

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.

ParametershookIdrequiredmanagementTokenrequired

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.

ParametershookIdrequiredmanagementTokenrequired

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.

ParametershookIdrequiredmanagementTokenrequired

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.

ParameterstokenrequiredhookIdrequiredeventIdrequiredbodyBase64requiredcontentTyperequired

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.

ParameterstokenrequiredhookIdrequireddeliveryIdrequired

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.

ParameterseventrequiredtokenrequiredhookIdrequiredreceiptrequired

Version history

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

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.