LabscoMCP early access ↗
kaginetaiMCP SERVER

Kaginet - Bitcoin Escrow for AI Agents

Bitcoin escrow an agent can open, fund and release by tool call — the issuer key is destroyed before funding, so nobody holds the coins.

by kaginetai ↗Wallets, Signing & Transaction ExecutionCommunity

LABSCO SUMMARY

This moves real money on mainnet, and that is the first thing to plan around.

The custody claim is structural rather than contractual — the issuer key is destroyed before funding, so Bitcoin consensus rather than policy is what stops anyone from taking the coins, and the TDX attestation is there to show the code that destroyed it. Two practical consequences: call kagikai_fee_estimate before creating anything, because the platform fee plus two on-chain transactions makes very small escrows uneconomic, and give a failed instrument to kagikai_recycle_instrument rather than abandoning it.

What it is

A hosted MCP server for escrowed Bitcoin payments between agents. It creates an instrument with a funding address, holds the payment until evidence is submitted and evaluated, then sweeps to the payee. The service runs inside an Intel TDX confidential VM, and the attestation for any instrument can be fetched and checked.

What you get

  • Escrow in five calls — kagikai_escrow_create returns a funding address and a BIP-21 payment URI, kagikai_escrow_status tracks the funding, forwarding and sweep transactions, kagikai_escrow_release submits evidence to trigger evaluation and payout, kagikai_escrow_cancel rejects, and kagikai_set_destination changes where the sweep goes
  • kagikai_fee_estimate prices an escrow before you commit — platform fee, mining fees and net amount, with no state change
  • Recovery for money that got stuck: kagikai_list_available finds expired or rejected instruments, kagikai_recycle_instrument reuses one with new terms and no on-chain transaction, kagikai_refund_instrument sweeps back to the funding source
  • Optimistic settlement with a dispute path — kagikai_dispute_instrument posts a bond during the dispute window, kagikai_resolve_dispute settles it as uphold, reject or refund
  • Verification you can run yourself — kagikai_verify_address does dual-node UTXO checks, kagikai_get_attestation returns the TDX document, kagikai_verify_tdx_quote checks the quote header, vendor ID and code hash
  • Agent identity and reputation — kagikai_get_agent, kagikai_update_agent, kagikai_get_reputation and kagikai_get_agent_card for a Google A2A-compatible card
  • Two resource templates, kagikai://instrument/{instrument_id} and kagikai://attestation/{instrument_id}

Requirements

An API key from the Kaginet cloud console, sent as a bearer token. The hosted server is at https://mcp.kaginet.com/sse, added to a client config as a URL with an Authorization header — nothing to install. LangChain and CrewAI toolkits wrap the same 29 tools for agents that are not MCP clients. Costs are real: the platform fee is 50 basis points of the amount with a floor of 10 sats and a cap of 100,000 sats, plus Bitcoin mining fees for the two on-chain transactions per escrow.

Setup effort

Paste a URL with a key — add the endpoint to your client