Datoka Agent
REMOTE · DATOKA-AGENT.BHAZARSTUDIO.WORKERS.DEV
Signed agent execution declarations. Free verification; issuance 0.002 USDC via x402 on Base.
Available components
Last scanned (15 hours ago)
Scores higher than 71% 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 Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 563 tokens (~112/item across 5 items; 5 tools + 0 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, 1 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 (80% 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 5 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.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 41 to 44.
- 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 +5
- Schema quality: 83 → 112 ▼ functional
- Tool coverage: 67% → 80% ▲ functional
- Tool coverage: 46% → 100% ▲ functional
- Schema quality: good → excellent functional
- 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 +2
- Stability: 0.13 → fail ▼ security
- HSTS header: fail → pass ▲ security
- Schema quality: 72 → 83 ▼ functional
- Tool coverage: 100% → 67% ▼ functional
- Tool “issue_agent_receipt” dropped its output schema ▼ functional
- Tool “issue_proof_receipt” dropped its output schema ▼ functional
- Tool coverage: 0% → 46% ▲ functional
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- Server version: 0.8.1 → 0.8.3 functional
- 3 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Oct 26 0
- Server version: 0.8.0 → 0.8.1 functional
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-agent.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-agent.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-agent.bhazarstudio.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://datoka-agent.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_agent_public_keys Get Agent Public Keys ~27
Return public keys of this issuer. The operator must establish trust in this issuer independently.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| issuer | string | yes | – |
| keys | array | yes | – |
No examples provided.
issue_agent_receipt Issue Agent Receipt ~98
Persist a signed execution declaration receipt. Public price: 0.002 USDC via x402 on the advertised network. Preserve event, idempotencyKey and payment authorization on retries. Signed declarations do not independently prove execution.
| Name | Type | Req | Description |
|---|---|---|---|
| event | object | yes | Commitment-only declaration of one execution step. |
| idempotencyKey | string | yes | Persist this unique key before purchase. Reuse unchanged with the same input and payment authorization after interruption. |
No output schema declared.
No examples provided.
prepare_agent_event Prepare Agent Event ~80
Free validation of a locally built execution declaration before issuance. Hash exact input and output bytes locally; supply identifiers and UTC timestamps with milliseconds. Returns the validated event, commitment and logical chain without creating or purchasing a receipt. Use issue_agent_receipt only if a portable signed declaration is needed.
| Name | Type | Req | Description |
|---|---|---|---|
| event | object | yes | Commitment-only declaration of one execution step. |
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | yes | – |
| commitment | object | yes | – |
| event | object | yes | Commitment-only declaration of one execution step. |
No examples provided.
verify_agent_receipt Verify Agent Receipt ~104
Free verification of an execution event and its unchanged receipt returned by issue_agent_receipt. Checks signature, scope and event commitment against this issuer. No wallet or new issuance required. Use verify_proof_receipt for the distinct common proof-envelope format. A valid signature does not independently prove execution; compare original bytes locally.
| Name | Type | Req | Description |
|---|---|---|---|
| event | object | yes | Commitment-only declaration of one execution step. |
| receipt | object | yes | Signed Datoka receipt; verify against independently trusted keys. |
| Name | Type | Req | Description |
|---|---|---|---|
| agentId | string | yes | Identifier of the declaring agent, not an independently verified identity. |
| attestation | string | yes | – |
| receiptId | string | yes | – |
| runId | string | yes | Stable identifier for this execution run. |
| scope | string | yes | – |
| stepId | string | yes | Stable identifier of the step within the run. |
| valid | boolean | yes | – |
No examples provided.
verify_proof_receipt Verify Proof Receipt ~182
Free verification of a common Datoka proof against an independently obtained caller-supplied public trust registry and explicit issuer/scope/chain. Send only the proof, never raw documents. receiptVerified concerns signature, context and dates; status remains incomplete because the artifact is checked locally. No payment, factual accuracy or parent signatures are verified.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | Optional expected logical chain identifier. Omit only when no chain restriction is required. |
| issuer | string | yes | Expected trusted issuer identifier; must match the trust registry and proof. |
| proof | object | yes | Unmodified common Datoka proof envelope; do not send its raw artifact. |
| scope | string | yes | Expected scope authorized by the caller-supplied trust registry. |
| trust | object | yes | Public trust registry obtained independently from a trusted source, not accepted merely because it accompanies this proof. |
| Name | Type | Req | Description |
|---|---|---|---|
| artifactHandling | string | yes | – |
| checks | object | yes | – |
| code | string | – | – |
| receiptId | string | – | – |
| receiptVerified | boolean | yes | – |
| status | string | yes | – |
| trustSource | string | yes | – |
No examples provided.
How do I install the Datoka Agent MCP server?
Datoka Agent is a hosted endpoint at https://datoka-agent.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-agent.bhazarstudio.workers.dev
claude mcp add --transport http dev-workers-bhazarstudio-datoka-agent-agent 'https://datoka-agent.bhazarstudio.workers.dev/mcp'
What is the Datoka Agent MCP server?
Datoka Agent is an MCP server listed in the public MCP registry as dev.workers.bhazarstudio.datoka-agent/agent. Signed agent execution declarations. Free verification; issuance 0.002 USDC via x402 on Base. This page covers its hosted endpoint (https://datoka-agent.bhazarstudio.workers.dev/mcp).
Is the Datoka Agent MCP server safe to use?
Datoka Agent scores 76 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 Agent MCP server expose?
Datoka Agent exposes 5 tools: verify_proof_receipt, prepare_agent_event, issue_agent_receipt, verify_agent_receipt, get_agent_public_keys. Their descriptions and schemas cost roughly 491 tokens of context every time the server is loaded.
Does the Datoka Agent MCP server require authentication?
No. We connected to Datoka Agent without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Datoka Agent MCP server still maintained?
Datoka Agent 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.