datoka-hooks

Tools

9 tools: 4 read-only, 3 change data, 2 high risk (delete, pay, send or run code).

1 tool can move money or change orders; they are listed first.

read-only

Only reads or looks things up. Safe for an agent to call on its own.

changes data

Creates, edits or sends something. Worth a person's approval the first time.

high risk

Can delete, pay, send on your behalf or run code. Hard or impossible to undo.

Connecting costs an agent about 1,891 tokens of tool definitions and a 690 ms handshake.

• high riskpurchase_hook_creditsmoves money or changes ordersRequest an x402 quote without payment, or buy credits with an explicitly authorized signed payment. Reuse purchaseId and the same payment after any timeout.
• high riskrevoke_destinationPermanently revoke client access. Previously accepted deliveries finish.
• changes dataregister_destinationCreate an isolated access. Keep recoveryKey secret and reuse it only with the same target on retries.
• changes dataverify_destinationVerify the well-known challenge file and activate your destination.
• changes dataaccept_hook_eventEnqueue an event for your verified receiver, idempotent by eventId and exact bytes.
• read-onlyget_hook_creditsRead your extra admission credit balance.
• read-onlyget_destination_statusRead verification/revocation status and challenge.
• read-onlyget_hook_deliveryRead delivery state and signed observations.
• read-onlyverify_hook_receiptVerify a relay receipt within your authenticated hook.

Levels are automated estimates from each tool's public name, description and annotations, and can be wrong. Descriptions as the server publishes them.

Status

Newest check: answered with tools, from the daily check, 2026-10-05, 690 ms.

From one check a day over the last 1 day. Servers whose owner verified them are checked every 5 minutes. Sign-in and payment answers count as up.

Last 30 days

2026-09-062026-10-05

answered with toolssign-in or payment askednot answeringnot checked

Compare: the most reliable servers in Payments and finance, ranked by days answering.

Badge

Live: status, days reachable, the tokens its tool list costs an agent. For a README:

[![7Maps](https://7it.co.il/7maps/badge/datoka-hooks.bhazarstudio.workers.dev/mcp.svg)](https://7it.co.il/7maps/s/datoka-hooks.bhazarstudio.workers.dev/mcp)

Other styles: add ?style=uptime (30-day uptime), ?style=stars (agents’ rating) or ?style=verified (owner mark) to the image address, or ?style=top (shows "top 10%" when the server ranks in the top tenth of its category by days answering; otherwise the standard badge).

Is this badge genuine? Anyone can check what a genuine badge for this server says right now: /7maps/verify/badge?server=datoka-hooks.bhazarstudio.workers.dev%2Fmcp (add the same &style= for another style).

Own this server? Verify that it is yours.

Status widget

A live status card for a status page, docs or a dashboard: current status, the 30-day strip, uptime and handshake time.

Script (renders where it is placed, in its own shadow DOM):

<script src="https://7it.co.il/7maps/widget/datoka-hooks.bhazarstudio.workers.dev/mcp.js" async></script>

Or an iframe:

<iframe src="https://7it.co.il/7maps/widget/datoka-hooks.bhazarstudio.workers.dev/mcp" title="7Maps status" width="360" height="176" style="border:0;max-width:100%" loading="lazy"></iframe>

The widget is drawn only from 7it.co.il. Is a status shown elsewhere genuine? Check it: /7maps/verify/badge?server=datoka-hooks.bhazarstudio.workers.dev%2Fmcp.

Add ?theme=light or ?theme=dark to either address (default: follows the visitor's setting). Refreshed every 5 minutes. Open the card · script.

For AI agents

Before connecting, an agent can ask 7Maps for this server's full condition, every tool's risk level and what changed since a person approved it: the road_conditions, watch and route tools on https://7it.co.il/7maps/mcp, paid per call in USDC via x402. About 7Maps.