Skip to content

Datoka Hooks

by datoka-hooks-test.bhazarstudio.workers.dev · remote · no sign-in to list tools · v0.7.6 · published by dev.workers.bhazarstudio.datoka-hooks-test

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

Deletes · 1Final · 1Changes · 4

9 tools: 1 can delete or cancel things, 1 do something that can't be undone, 4 change things and 3 only read.

Scanned Oct 21, 2026

2 checks matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http datoka-hooks https://datoka-hooks.bhazarstudio.workers.dev/mcp

Findings

Matches of fixed checks, with the text they matched.

1 warn1 info
  • The server marks "verify_destination" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "fetch": a word for reading.

    What this check looks for
  • The description mentions "credentials".

    Matched text

    description: "...er you control. Returns hookId, private credentials and the ownership challenge; delivery r..."

    What this check looks for

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

9 tools

Deletes or cancels 1Claude Code: deny
  • revoke_destinationPermanently revoke this hook with its management token after explicit owner approval.No findings

    Why it is in this group

    • The name "revoke_destination" says "revoke": a word for removing or ending something.
    • The description says "cannot be undone".
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
Can't be undone 1Claude Code: ask
  • purchase_hook_creditsRequest an x402 quote without payment, or buy credits with an explicitly authorized signed payment.No findings

    Why it is in this group

    • The name "purchase_hook_credits" says "purchase": a word that usually means money moves, which cannot be taken back.
    Description, as the server wrote it
    Request an x402 quote without payment, or buy credits with an explicitly authorized signed payment. Reuse purchaseId and the same payment after any timeout.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Changes things 4Claude Code: ask
  • accept_hook_eventEnqueue up to 65536 payload bytes for a previously verified receiver using its delivery token.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • register_destinationRegister an HTTPS receiver you control.1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...er you control. Returns hookId, private credentials and the ownership challenge; delivery r..."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • verify_destinationFetch the ownership challenge from the previously registered receiver and activate it when valid.1 finding

    Why it is in this group

    • The description's first verb is "fetch": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    Findings

    • Warn

      The server marks "verify_destination" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "fetch": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • verify_hook_receiptCheck an unchanged event and signed receipt returned by get_hook_delivery within the authenticated hook.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 3Claude Code: allow
  • get_destination_statusRead the existing hook ownership challenge and verification or revocation status using its management token.No findings

    Why it is in this group

    • The name "get_destination_status" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_hook_creditsRead remaining purchased admission credits for an existing hook using its management token.No findings

    Why it is in this group

    • The name "get_hook_credits" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_hook_deliveryRead one accepted event by its returned deliveryId and hook delivery token.No findings

    Why it is in this group

    • The name "get_hook_delivery" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 0.7.6. Values in angle brackets are yours to fill in.

claude mcp add --transport http datoka-hooks https://datoka-hooks.bhazarstudio.workers.dev/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__datoka-hooks__get_hook_credits",
      "mcp__datoka-hooks__get_destination_status",
      "mcp__datoka-hooks__get_hook_delivery"
    ],
    "ask": [
      "mcp__datoka-hooks__purchase_hook_credits",
      "mcp__datoka-hooks__register_destination",
      "mcp__datoka-hooks__verify_destination",
      "mcp__datoka-hooks__accept_hook_event",
      "mcp__datoka-hooks__verify_hook_receipt"
    ],
    "deny": [
      "mcp__datoka-hooks__revoke_destination"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as datoka-hooks. Review it before you use it.