Datoka Hooks MCP Server

by workers-bhazarstudio-datoka-hooks-test Your server? Claim it

answering

Datoka Hooks is answering right now. Last checked 6 min ago. It exposes 9 tools.

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

Uptime history 35 days of history · worst day 99%

35 days agonow

100.0%

Uptime 24h

182 of 182 checks

Tools

read from the server

232 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 45

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 1 October 2026. No other catalogue keeps this.

7 Oct 9 tools changed the parameters they ask for accept_hook_event, get_destination_status, get_hook_credits and 6 more

7 Oct 8 tool descriptions were rewritten accept_hook_event, get_destination_status, get_hook_credits and 5 more

7 Oct a tool changed version2 times that day

5 Oct a tool changed version4 times that day

4 Oct 9 tools changed the parameters they ask for accept_hook_event, get_destination_status, get_hook_credits and 6 more

4 Oct a tool changed version

3 Oct a tool changed version

2 Oct a tool changed version3 times that day

1 Oct a tool changed version6 times that day

1 Oct 2 tools appeared get_hook_credits, purchase_hook_credits

and 11 more, back to 1 October 2026

Datoka Hooks missed 2 checks this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 6 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

Settings → Connectors → Add custom connector, then paste this address

https://datoka-hooks-test.bhazarstudio.workers.dev/mcp

~/.codex/config.toml

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

.cursor/mcp.json

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

.vscode/mcp.json

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

This server publishes 1 more address. The block above uses the one we reach during checks; the full list is under Endpoints below, and the author may intend a particular one for your client.

Available tools 9

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

hook

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.

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

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.

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.

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.

destination

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.

purchase

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 register again with a new key.

revoke

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.

Endpoints

URL	Transport	State	Latency	Checked
https://datoka-hooks-test.bhazarstudio.workers.dev/mcp	streamable-http	answering	68 ms	6 min ago
https://datoka-hooks.bhazarstudio.workers.dev/mcp	streamable-http	answering	161 ms	6 min ago

Alternatives to Datoka Hooks

same job, measured the same way

Verzi Health

by verzi

Medicare DME coverage by HCPCS code and date of service, with CMS citations and signed receipts.

6 tools answering

Otterkit

by useotterkit

Tunnels and webhooks for AI agents: capture, await, verify, replay, and send signed test events.

45 installs/wk local only

Wever Pay Open Exchange Public Beta

by weverpay

Open Base Sepolia testnet exchange for autonomous buyer and seller agents, with signed receipts.

50 tools answering

ImpactLine public research

by theguysaccount

Search public laws and implementation evidence with sources, scope limits and dated coverage.

3 tools answering

Webhook Crash Lab

by krrishkumar125

Lets coding agents crash-test webhook handlers and re-run until they survive retries.

129 installs/wk local only

MCP Debug

by standardbeagle

Debug and develop MCP servers with hot-swapping, session recording, and playback testing

70 installs/wk local only

The Wiley Rule (public data)

by thewileyrule

Read-only public data on 7-OH and related products: research, test results, FDA actions, state laws

11 tools answering

G62 Patent Search

by g62

Public patent search with ranked candidates, source links and coverage context. Developer beta.

answering

Datoka Hooks — questions

Answers built from our own checks of this server.

What can Datoka Hooks do?

It exposes 9 tools, read directly from the server on our last check. Among them: accept_hook_event, get_destination_status, get_hook_credits, get_hook_delivery, purchase_hook_credits, register_destination and 3 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is Datoka Hooks mostly used for?

Its tools cluster around verify and hook. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is Datoka Hooks working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 182 of 182 checks got a reply (100.0%), average response time 232 ms. The bar chart above shows every period we have measured.

How do I connect Datoka Hooks?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Datoka Hooks need an API key?

No. Datoka Hooks completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 9 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Datoka Hooks?

It answers our handshake in 232 ms on average, which is faster than 60% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.