Skip to content

Datoka Hooks MCP server

dev.workers.bhazarstudio.datoka-hooks-test/datoka-hooksdatoka-hooks-test.bhazarstudio.workers.devstreamable-httpv0.7.6Scanned

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

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

Tools: 1 delete, 1 irreversible, 4 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 5
  • Can send data out · 0
  • 2 findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things and 1 does something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Datoka Hooks MCP server can do

The Datoka Hooks MCP server is published by datoka-hooks-test.bhazarstudio.workers.dev, a domain the MCP Registry verified. It has 9 tools. It can delete or cancel things (1 tool: revoke_destination), do things that cannot be undone, such as sending, paying or publishing (purchase_hook_credits) and create or change data (4 tools: register_destination, verify_destination, accept_hook_event and verify_hook_receipt). 3 tools only read.

5 tools bring in text other people can write (purchase_hook_credits, register_destination, verify_destination and 2 more).

The fixed checks matched 2 findings (credentials-mention and annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 17, 2026, version 0.7.6.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

9 tools

Deletes or cancels 1Claude Code: deny
  • revoke_destinationPermanently revoke this hook with its management token after explicit owner approval.Reads text others writeNo 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).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    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.Reads text others writeNo 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.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    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.Reads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    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.Reads text others write1 finding

    Why it is in this group

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

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    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.Reads text others write1 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).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    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 3Show 3 read-only tools
  • 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.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write5
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:22 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
6
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 6 tools that change things (1 destructive, 1 irreversible, 4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://datoka-hooks.bhazarstudio.workers.dev/mcp: tools/list returned 9 tools to an anonymous client, including revoke_destination (destructive), purchase_hook_credits (irreversible), register_destination (write), verify_destination (write), accept_hook_event (write) and 1 more

    What this check looks for

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

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

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
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 or a way out, 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. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as datoka-hooks. Review it before you use it.

Capability tags behind 5 rules
  • mcp__datoka-hooks__purchase_hook_credits untrusted-input
  • mcp__datoka-hooks__register_destination untrusted-input
  • mcp__datoka-hooks__verify_destination untrusted-input
  • mcp__datoka-hooks__revoke_destination untrusted-input
  • mcp__datoka-hooks__accept_hook_event untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/dev.workers.bhazarstudio.datoka-hooks-test/datoka-hooks/verify?hash=f3de9caf4fc5d0fe8154ac8a674dc2faf4917af57faf8a43979fdf96f163110a" | jq -e '.changed == false'

Pinned hash f3de9caf4fc5, from Nov 17, 2026, 04:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/dev.workers.bhazarstudio.datoka-hooks-test/datoka-hooks/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for dev.workers.bhazarstudio.datoka-hooks-test/datoka-hooks
[![Anlyon Radar](https://radar.anlyon.com/badge/dev.workers.bhazarstudio.datoka-hooks-test/datoka-hooks.svg)](https://radar.anlyon.com/servers/dev.workers.bhazarstudio.datoka-hooks-test/datoka-hooks)

Source: MCP Registry. Synced Oct 21, 2026, 18:12 UTC.

Datoka Hooks MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Datoka Hooks MCP server safe?

No scan can promise that. What its definitions show: 9 tools, 6 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Datoka Hooks MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: revoke_destination.

Can the Datoka Hooks MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: purchase_hook_credits.

What tools does the Datoka Hooks MCP server have?

9 tools: 1 destructive, 1 irreversible, 4 write, 3 read. revoke_destination, purchase_hook_credits, register_destination, verify_destination, accept_hook_event, verify_hook_receipt, get_hook_credits, get_destination_status and 1 more.

Does the Datoka Hooks MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Datoka Hooks MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Datoka Hooks MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 17, 2026.