Datoka API
REMOTE · DATOKA-API.BHAZARSTUDIO.WORKERS.DEV
Signed API declarations for agent handoffs. Free demo and verification; receipts cost 0.002 USDC.
Available components
Last scanned (17 hours ago)
Scores higher than 74% of remote servers
Reachable. Last reached 16 Oct 2026.
Category Security
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. How we score → Why this is hard to score →
Endpoint Security69
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 403, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 566 tokens (~94/item across 6 items; 4 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management44
- Stability check failed: schema churn in the 17 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (75% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 34 to 38.
- 12 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 24 to 31.
- 10 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 18 to 24.
- 8 Oct 26 +4
- Schema quality: 82 → 94 ▼ functional
- Tool coverage: 20% → 100% ▲ functional
- Schema quality: good → excellent functional
- Server version: 0.3.13 → 0.3.14 functional
- “issue_api_receipt” reworded the description of “event” cosmetic
- “prepare_api_exchange” reworded the description of “event” cosmetic
- “verify_api_receipt” reworded the description of “event” cosmetic
- “verify_api_receipt” reworded the description of “receipt” cosmetic
- Tool “get_api_public_keys” changed its title: Get API Public Keys cosmetic
- Tool “issue_api_receipt” changed its title: Issue API Receipt cosmetic
- Tool “prepare_api_exchange” changed its title: Prepare API Exchange cosmetic
- Tool “verify_api_receipt” changed its title: Verify API Receipt cosmetic
- 6 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 4 to 11.
- 4 Oct 26 +3
- HSTS header: fail → pass ▲ security
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- Server version: 0.3.10 → 0.3.11 functional
- 2 Oct 26 +2
- The server rewrote its instructions, which are the text every model session reads security
- Tool “verify_api_receipt” rewrote its description, which is the text the model reads security
- Schema quality: 346 → 494 ▼ functional
- The server now declares the “resources” capability functional
- First check of Schema quality: 100 functional
- New resource “demo-receipt” functional
- New resource “integration” functional
- Server version: 0.3.9 → 0.3.10 functional
- 1 Oct 26 0
- Tool “issue_api_receipt” rewrote its description, which is the text the model reads security
- Tool “prepare_api_exchange” rewrote its description, which is the text the model reads security
- Schema quality: 64 → 86 ▼ functional
- Tool coverage: 0% → 20% ▲ functional
- Server version: 0.3.8 → 0.3.9 functional
- Server version: 0.3.3 → 0.3.8 functional
- “issue_api_receipt” reworded the description of “idempotencyKey” cosmetic
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 16 Oct 2026 · Probed https://datoka-api.bhazarstudio.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=bhazarstudio.workers.dev | CN=YE2,O=Let's Encrypt,C=US | 3 Sept 2026 | 2 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5ab0e87130a64d96f2f3d39cc4055a1aac7 |
| SANs: *.bhazarstudio.workers.dev, bhazarstudio.workers.dev | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of datoka-api.bhazarstudio.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://datoka-api.bhazarstudio.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://datoka-api.bhazarstudio.workers.dev/mcp | Inconclusive | 403 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_api_public_keys Get API Public Keys ~23
Return issuer public keys. Establish issuer trust independently before offline verification.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| issuer | string | yes | – |
| keys | array | yes | – |
No examples provided.
issue_api_receipt Issue API Receipt ~162
Buy a portable signed commitment to a declared API exchange when a recipient needs independently verifiable receipt integrity: response handoff, archived decision input, or change investigation. Costs 0.002 USDC per receipt via x402 when enabled; verification is free. A local log may suffice for disposable data. Requires caller-approved budget. Keep event, idempotency key and original payment unchanged on retry. Attests a client declaration, not provider origin, content truth or independent observation.
| Name | Type | Req | Description |
|---|---|---|---|
| event | object | yes | Commitment-only HTTP exchange declaration built locally with the SDK. No raw URLs, headers or bodies. |
| idempotencyKey | string | yes | One stable key per purchase, saved before payment. Keep it, the event and original payment authorization unchanged on retries. |
No output schema declared.
No examples provided.
prepare_api_exchange Prepare API Exchange ~85
Free validation before buying a receipt. Supply an event built locally with the SDK from real captured bytes; never fabricate hashes. Returns the commitment without issuing a receipt or paying. Use when retaining verifiable evidence of an API response for a handoff or archive.
| Name | Type | Req | Description |
|---|---|---|---|
| event | object | yes | Commitment-only HTTP exchange declaration built locally with the SDK. No raw URLs, headers or bodies. |
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | – |
| commitment | object | yes | – |
| event | object | yes | Commitment-only HTTP exchange declaration built locally with the SDK. No raw URLs, headers or bodies. |
No examples provided.
verify_api_receipt Verify API Receipt ~121
Free signature and declaration verification. To try before buying, read datoka-api://demo-receipt or /demo/receipt.json and pass the returned JSON here. No wallet needed for public verification. Verifies issuer, scope and event commitment; compare original response bytes locally with the SDK or /verify/.
| Name | Type | Req | Description |
|---|---|---|---|
| event | object | yes | Commitment-only HTTP exchange declaration built locally with the SDK. No raw URLs, headers or bodies. |
| receipt | object | yes | Unmodified signed receipt returned by issuance or the public synthetic demo; verify against trusted issuer keys. |
| Name | Type | Req | Description |
|---|---|---|---|
| apiId | string | yes | Caller-chosen API identifier; not a certified provider identity. |
| attestation | string | yes | – |
| exchangeId | string | yes | Stable identifier for one declared HTTP exchange. |
| receiptId | string | yes | – |
| scope | string | yes | – |
| valid | boolean | yes | – |
No examples provided.
How do I install the Datoka API MCP server?
Datoka API is a hosted endpoint at https://datoka-api.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.
remote · datoka-api.bhazarstudio.workers.dev
claude mcp add --transport http dev-workers-bhazarstudio-datoka-api-api 'https://datoka-api.bhazarstudio.workers.dev/mcp'
What is the Datoka API MCP server?
Datoka API is an MCP server listed in the public MCP registry as dev.workers.bhazarstudio.datoka-api/api. Signed API declarations for agent handoffs. Free demo and verification; receipts cost 0.002 USDC. This page covers its hosted endpoint (https://datoka-api.bhazarstudio.workers.dev/mcp).
Is the Datoka API MCP server safe to use?
Datoka API scores 77 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 API MCP server expose?
Datoka API exposes 4 tools: prepare_api_exchange, issue_api_receipt, verify_api_receipt, get_api_public_keys. Their descriptions and schemas cost roughly 391 tokens of context every time the server is loaded.
Does the Datoka API MCP server require authentication?
No. We connected to Datoka API without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Datoka API MCP server still maintained?
Datoka API is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.