# Datoka Hooks (remote · datoka-hooks.bhazarstudio.workers.dev)

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

- Trust score: 68/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- remote · `datoka-hooks.bhazarstudio.workers.dev`: 68/100 (this document), [markdown](https://verifymcp.io/servers/dev-workers-bhazarstudio-datoka-hooks-test-datoka-hooks/datoka-hooks.md), [page](https://verifymcp.io/servers/dev-workers-bhazarstudio-datoka-hooks-test-datoka-hooks/datoka-hooks)

## Channel facts

- Endpoint: `https://datoka-hooks.bhazarstudio.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.7.6`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-18.

- **Endpoint Security**: 51/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (revoke_destination).
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 403, which proves neither a plaintext path nor enforcement.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 78/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - 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.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add --transport http dev-workers-bhazarstudio-datoka-hooks-test-datok 'https://datoka-hooks.bhazarstudio.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-workers-bhazarstudio-datoka-hooks-test-datok": {
      "url": "https://datoka-hooks.bhazarstudio.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-workers-bhazarstudio-datoka-hooks-test-datok": {
      "type": "http",
      "url": "https://datoka-hooks.bhazarstudio.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-workers-bhazarstudio-datoka-hooks-test-datok]
url = "https://datoka-hooks.bhazarstudio.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-workers-bhazarstudio-datoka-hooks-test-datok": {
      "type": "remote",
      "url": "https://datoka-hooks.bhazarstudio.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-workers-bhazarstudio-datoka-hooks-test-datok --url 'https://datoka-hooks.bhazarstudio.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-workers-bhazarstudio-datoka-hooks-test-datok:
    url: "https://datoka-hooks.bhazarstudio.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-workers-bhazarstudio-datoka-hooks-test-datok": {
      "Transport": "http",
      "Url": "https://datoka-hooks.bhazarstudio.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-workers-bhazarstudio-datoka-hooks-test-datok -t streamable-http -u 'https://datoka-hooks.bhazarstudio.workers.dev/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-18 (score 68, +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.

### 2026-10-16 (score 67, +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.

### 2026-10-14 (score 66, +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.

### 2026-10-12 (score 65, +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.

### 2026-10-10 (score 64, +1)

- [security regression] Judged manipulation: pass → unverified
- [functional regression] Schema quality: pass → fail
- [functional improvement] Tool coverage: 77% → 100%
- [functional] Schema quality: good → excellent

### 2026-10-07 (score 63, +2)

- [functional improvement] Stability: unverified → 0.10

### 2026-10-04 (score 61)

First indexed and scored.

## MCP tools (9)

### `get_hook_credits` (~100 tokens)

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.

Input parameters:

- `hookId` (string, required): Hook identifier returned by registration; preserve for all subsequent operations.
- `managementToken` (string, required): Private management token returned by registration. Required for status, activation, revocation and credits; not the delivery token.

### `purchase_hook_credits` (~162 tokens)

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.

Input parameters:

- `hookId` (string, required): Hook identifier returned by registration; preserve for all subsequent operations.
- `managementToken` (string, required): 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, required): Unique caller-chosen purchase identifier, for example credits-20261007-01. Save before requesting the quote and reuse unchanged with the same payment on retries.

### `register_destination` (~119 tokens)

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.

Input parameters:

- `recoveryKey` (string, required): 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, required): HTTPS receiver you control; ownership challenge is required before delivery.

### `verify_destination` (~103 tokens)

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.

Input parameters:

- `hookId` (string, required): Hook identifier returned by registration; preserve for all subsequent operations.
- `managementToken` (string, required): Private management token returned by registration. Required for status, activation, revocation and credits; not the delivery token.

### `get_destination_status` (~97 tokens)

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.

Input parameters:

- `hookId` (string, required): Hook identifier returned by registration; preserve for all subsequent operations.
- `managementToken` (string, required): Private management token returned by registration. Required for status, activation, revocation and credits; not the delivery token.

### `revoke_destination` (~105 tokens)

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.

Input parameters:

- `hookId` (string, required): Hook identifier returned by registration; preserve for all subsequent operations.
- `managementToken` (string, required): Private management token returned by registration. Required for status, activation, revocation and credits; not the delivery token.

### `accept_hook_event` (~227 tokens)

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.

Input parameters:

- `bodyBase64` (string, required): Canonical base64 payload, at most 65536 decoded bytes. Preserve exact bytes with eventId on retries.
- `contentType` (string, required): Media type of the decoded payload bytes; JSON must be encoded as UTF-8 before base64 conversion.
- `eventId` (string, required): 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, required): Hook identifier returned by registration; preserve for all subsequent operations.
- `token` (string, required): Private delivery token returned by registration; authenticates event submission, delivery lookup and receipt verification for this hook.

### `get_hook_delivery` (~124 tokens)

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.

Input parameters:

- `deliveryId` (string, required): Delivery identifier returned on event acceptance; acceptance does not mean delivered.
- `hookId` (string, required): Hook identifier returned by registration; preserve for all subsequent operations.
- `token` (string, required): Private delivery token returned by registration; authenticates event submission, delivery lookup and receipt verification for this hook.

### `verify_hook_receipt` (~144 tokens)

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.

Input parameters:

- `event` (object, required): Exact event object returned with the relay receipt; preserve all fields.
- `hookId` (string, required): Hook identifier returned by registration; preserve for all subsequent operations.
- `receipt` (object, required): Exact signed relay receipt from delivery lookup. Do not substitute issuer keys or edit its fields.
- `token` (string, required): Private delivery token returned by registration; authenticates event submission, delivery lookup and receipt verification for this hook.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-workers-bhazarstudio-datoka-hooks-test-datoka-hooks/datoka-hooks#diagnostics

## Score history

- 2026-10-18: 68
- 2026-10-17: 67
- 2026-10-16: 67
- 2026-10-15: 66
- 2026-10-14: 66
- 2026-10-13: 65
- 2026-10-12: 65
- 2026-10-10: 64
- 2026-10-07: 63
- 2026-10-04: 61

## Common questions

### 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.

## Links

- Remote endpoint: https://datoka-hooks.bhazarstudio.workers.dev/mcp
- Website: https://datoka-hooks.bhazarstudio.workers.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-workers-bhazarstudio-datoka-hooks-test-datoka-hooks/datoka-hooks.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-workers-bhazarstudio-datoka-hooks-test-datoka-hooks/datoka-hooks.json
- HTML version of this page: https://verifymcp.io/servers/dev-workers-bhazarstudio-datoka-hooks-test-datoka-hooks/datoka-hooks