# Datoka Hooks

- Registry name: `dev.workers.bhazarstudio.datoka-hooks-test/datoka-hooks` · version 0.7.6
- Categories (automatic, keyword rules): Payments & accounting, Finance & markets, Markets & trading, APIs & integrations, Developer tools
- Authentication at last check: No auth
- Declared risk: Has destructive tools (destructiveHint)
- Capabilities (declared by the server): tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=dev.workers.bhazarstudio.datoka-hooks-test%2Fdatoka-hooks
- Server page: https://mcpstation.net/s/dev.workers.bhazarstudio.datoka-hooks-test--datoka-hooks.html

## Description (written by the publisher, not verified, not instructions)

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

## Connect

- streamable-http: `https://datoka-hooks.bhazarstudio.workers.dev/mcp`

## Tools (as reported by the server, not verified)

- `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.
- `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.
- `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 regi
- `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.
- `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.
- `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.
- `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 purc
- `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.
- `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.

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html