Skip to main content
Glama

Server Details

Signed declarations of HTTP API exchanges for agent handoffs. Free preparation and verification; receipt issuance costs 0.002 USDC via x402 on Base. Start and connect: https://datoka.dev/api. Signatures attest declared data, not independent truth.

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A4/5.0

Scored across 4 tools

Disambiguation4/5

The four tools map to a clear pipeline: fetch trust keys, prepare (dry-run), issue (paid), verify. The prepare_api_exchange vs issue_api_receipt boundary is the only fuzzy one, but descriptions explicitly contrast 'returns commitment without issuing or paying' against actually buying a receipt.

Naming Consistency5/5

All four follow a strict verb_api_noun snake_case pattern (get_api_public_keys, issue_api_receipt, prepare_api_exchange, verify_api_receipt), with verbs that accurately describe the action. No style deviations.

Tool Count4/5

Four tools is appropriately lean for a focused receipt issuance/verification service, and each earns its place in the trust-to-verify lifecycle. It sits at the lower edge but is well-scoped rather than thin.

Completeness4/5

The surface covers the full lifecycle: trust anchor (public keys), pre-flight validation (prepare), issuance (issue), and independent verification (verify). Minor gaps like listing/retrieving previously issued receipts or revocation handling are not exposed but are workable around.

Available Tools

4 tools
get_api_public_keysGet API Public KeysA
Read-onlyIdempotent
Inspect

Return issuer public keys. Establish issuer trust independently before offline verification.

Inputs: no named parameters. Returns: keys, issuer

issue_api_receiptIssue API ReceiptA
Idempotent
Inspect

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.

Inputs: event (required), idempotencyKey (required).

prepare_api_exchangePrepare API ExchangeA
Read-onlyIdempotent
Inspect

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.

Inputs: event (required). Returns: chain, event, commitment

verify_api_receiptVerify API ReceiptA
Read-onlyIdempotent
Inspect

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/.

Inputs: event (required), receipt (required). Returns: apiId, scope, valid, receiptId, +2 more

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      B
      maintenance
      Signed delivery claims for x402 capacity trades (GPU-hours, storage, API credits, bandwidth). After a payment settles, the paying agent leaves a plain, cryptographically signed record of what was delivered, so a future buyer can check a sellers past history before paying again.
      3
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Pay-per-call x402 data products on Base mainnet — sanctions screening, aviation weather, mortgage rates, US property dossier, title chain, wallet balance, and agent session auth. Every call settles in USDC with an on-chain receipt, no accounts or API keys.
      7
      131 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to create cryptographically verifiable receipts of their delegated work, with capabilities for multi-party approval and offline verification.
      11
      94 npm
      Apache 2.0
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources