Datoka Hooks
REMOTE · DATOKA-HOOKS.BHAZARSTUDIO.WORKERS.DEV
Public webhook relay with signed observations, retries and verified receivers. Self-service.
Available components
Last scanned (6 hours ago)
Scores higher than 58% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Workflow Automation
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security51
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (revoke_destination). See how to fix → View diagnostics → Fail
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 403, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1299 tokens (~144/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
- Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- Manipulation not yet verified: only 1 of 10 captured unit(s) of tool text has been judged so far, so we will not certify text no model has read as clean.Unverified
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 27. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Oct 26 +1
- Judged manipulation: pass → unverified ▼ security
- Schema quality: pass → fail ▼ functional
- Tool coverage: 77% → 100% ▲ functional
- Schema quality: good → excellent functional
- 7 Oct 26 +2
- Stability: unverified → 0.10 ▲ functional
- 4 Oct 26 61
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 18 Oct 2026 · Probed https://datoka-hooks.bhazarstudio.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=bhazarstudio.workers.dev | CN=YE2,O=Let's Encrypt,C=US | 3 Sept 2026 | 2 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5ab0e87130a64d96f2f3d39cc4055a1aac7 |
| SANs: *.bhazarstudio.workers.dev, bhazarstudio.workers.dev | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of datoka-hooks.bhazarstudio.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://datoka-hooks.bhazarstudio.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://datoka-hooks.bhazarstudio.workers.dev/mcp | Inconclusive | 403 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
accept_hook_event Accept Hook Event ~227
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.
| Name | Type | Req | Description |
|---|---|---|---|
| bodyBase64 | string | yes | Canonical base64 payload, at most 65536 decoded bytes. Preserve exact bytes with eventId on retries. |
| contentType | string | yes | Media type of the decoded payload bytes; JSON must be encoded as UTF-8 before base64 conversion. |
| eventId | string | yes | Stable caller-chosen event identifier, for example order-20261007-01. Reuse with identical payload bytes on retry; different bytes under the same ID are rejected. |
| hookId | string | yes | Hook identifier returned by registration; preserve for all subsequent operations. |
| token | string | yes | Private delivery token returned by registration; authenticates event submission, delivery lookup and receipt verification for this hook. |
No output schema declared.
No examples provided.
get_destination_status Get Destination Status ~97
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.
| Name | Type | Req | Description |
|---|---|---|---|
| hookId | string | yes | Hook identifier returned by registration; preserve for all subsequent operations. |
| managementToken | string | yes | Private management token returned by registration. Required for status, activation, revocation and credits; not the delivery token. |
No output schema declared.
No examples provided.
get_hook_credits Get Hook Credits ~100
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.
| Name | Type | Req | Description |
|---|---|---|---|
| hookId | string | yes | Hook identifier returned by registration; preserve for all subsequent operations. |
| managementToken | string | yes | Private management token returned by registration. Required for status, activation, revocation and credits; not the delivery token. |
No output schema declared.
No examples provided.
get_hook_delivery Get Hook Delivery ~124
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.
| Name | Type | Req | Description |
|---|---|---|---|
| deliveryId | string | yes | Delivery identifier returned on event acceptance; acceptance does not mean delivered. |
| hookId | string | yes | Hook identifier returned by registration; preserve for all subsequent operations. |
| token | string | yes | Private delivery token returned by registration; authenticates event submission, delivery lookup and receipt verification for this hook. |
No output schema declared.
No examples provided.
purchase_hook_credits Purchase Hook Credits ~162
Request an x402 quote without payment, or buy credits with an explicitly authorized signed payment. Reuse purchaseId and the same payment after any timeout.
| Name | Type | Req | Description |
|---|---|---|---|
| hookId | string | yes | Hook identifier returned by registration; preserve for all subsequent operations. |
| managementToken | string | yes | Private management token returned by registration. Required for status, activation, revocation and credits; not the delivery token. |
| payment | object | – | Original signed x402 payment payload authorized by the payer. Omit to request a quote without paying. Never fabricate or replace an uncertain authorization. |
| purchaseId | string | yes | Unique caller-chosen purchase identifier, for example credits-20261007-01. Save before requesting the quote and reuse unchanged with the same payment on retries. |
No output schema declared.
No examples provided.
register_destination Register Destination ~119
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.
| Name | Type | Req | Description |
|---|---|---|---|
| recoveryKey | string | yes | Generate 32 random bytes locally and encode as 64 lowercase hex characters. Save privately before registration; reuse with the identical target after interruption. |
| target | string | yes | HTTPS receiver you control; ownership challenge is required before delivery. |
No output schema declared.
No examples provided.
revoke_destination Revoke Destination ~105
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.
| Name | Type | Req | Description |
|---|---|---|---|
| hookId | string | yes | Hook identifier returned by registration; preserve for all subsequent operations. |
| managementToken | string | yes | Private management token returned by registration. Required for status, activation, revocation and credits; not the delivery token. |
No output schema declared.
No examples provided.
verify_destination Verify Destination ~103
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.
| Name | Type | Req | Description |
|---|---|---|---|
| hookId | string | yes | Hook identifier returned by registration; preserve for all subsequent operations. |
| managementToken | string | yes | Private management token returned by registration. Required for status, activation, revocation and credits; not the delivery token. |
No output schema declared.
No examples provided.
verify_hook_receipt Verify Hook Receipt ~144
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.
| Name | Type | Req | Description |
|---|---|---|---|
| event | object | yes | Exact event object returned with the relay receipt; preserve all fields. |
| hookId | string | yes | Hook identifier returned by registration; preserve for all subsequent operations. |
| receipt | object | yes | Exact signed relay receipt from delivery lookup. Do not substitute issuer keys or edit its fields. |
| token | string | yes | Private delivery token returned by registration; authenticates event submission, delivery lookup and receipt verification for this hook. |
No output schema declared.
No examples provided.
How do I install the Datoka Hooks MCP server?
Datoka Hooks is a hosted endpoint at https://datoka-hooks.bhazarstudio.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · datoka-hooks.bhazarstudio.workers.dev
claude mcp add --transport http dev-workers-bhazarstudio-datoka-hooks-test-datok 'https://datoka-hooks.bhazarstudio.workers.dev/mcp'
What is the Datoka Hooks MCP server?
Datoka Hooks is an MCP server listed in the public MCP registry as dev.workers.bhazarstudio.datoka-hooks-test/datoka-hooks. Public webhook relay with signed observations, retries and verified receivers. Self-service. This page covers its hosted endpoint (https://datoka-hooks.bhazarstudio.workers.dev/mcp).
Is the Datoka Hooks MCP server safe to use?
Datoka Hooks scores 68 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Datoka Hooks MCP server expose?
Datoka Hooks exposes 9 tools: get_hook_credits, purchase_hook_credits, register_destination, verify_destination, get_destination_status, and 4 more. Their descriptions and schemas cost roughly 1,181 tokens of context every time the server is loaded.
Does the Datoka Hooks MCP server require authentication?
No. We connected to Datoka Hooks without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Datoka Hooks MCP server still maintained?
Datoka Hooks is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.