kagikai_escrow_createLABSCO 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_createreturns a funding address and a BIP-21 payment URI,kagikai_escrow_statustracks the funding, forwarding and sweep transactions,kagikai_escrow_releasesubmits evidence to trigger evaluation and payout,kagikai_escrow_cancelrejects, andkagikai_set_destinationchanges where the sweep goes kagikai_fee_estimateprices an escrow before you commit — platform fee, mining fees and net amount, with no state change- Recovery for money that got stuck:
kagikai_list_availablefinds expired or rejected instruments,kagikai_recycle_instrumentreuses one with new terms and no on-chain transaction,kagikai_refund_instrumentsweeps back to the funding source - Optimistic settlement with a dispute path —
kagikai_dispute_instrumentposts a bond during the dispute window,kagikai_resolve_disputesettles it as uphold, reject or refund - Verification you can run yourself —
kagikai_verify_addressdoes dual-node UTXO checks,kagikai_get_attestationreturns the TDX document,kagikai_verify_tdx_quotechecks the quote header, vendor ID and code hash - Agent identity and reputation —
kagikai_get_agent,kagikai_update_agent,kagikai_get_reputationandkagikai_get_agent_cardfor a Google A2A-compatible card - Two resource templates,
kagikai://instrument/{instrument_id}andkagikai://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
USE CASES
Paying another agent only on delivery
Create the escrow, hand over the funding address, and release when the evidence passes evaluation.
Knowing the cost before committing funds
Price the platform fee, mining fees and net payout without creating anything on chain.
Recovering funds from an escrow that expired
Find the stuck instruments, then either reuse one with new terms or sweep it back to the source.
Contesting a release you disagree with
Post a bond inside the dispute window and let the resolution path decide it.
Checking the service rather than trusting it
Fetch the hardware attestation for an instrument and verify the quote structurally yourself.
29 tools
Listed in project docs. Your client may show a different list.
kagikai_escrow_statuskagikai_escrow_releasekagikai_escrow_cancelkagikai_set_destinationkagikai_fee_estimatekagikai_list_availablekagikai_recycle_instrumentkagikai_refund_instrumentkagikai_dispute_instrumentkagikai_resolve_disputekagikai_create_instrumentkagikai_confirm_instrumentkagikai_get_statuskagikai_submit_instrumentkagikai_complete_instrumentkagikai_reject_instrumentkagikai_batch_createkagikai_batch_statuskagikai_healthkagikai_verify_addresskagikai_get_attestationkagikai_verify_tdx_quotekagikai_get_agentkagikai_update_agentkagikai_get_agent_cardkagikai_get_reputationkagikai_watch_receiptkagikai_delete_watchBEFORE YOU INSTALL
What to know first
Tools you get
29 tools named in the project's documentation.
Requires
A client that can reach a remote MCP server over HTTP
Where it runs
Both documented clients connect to a hosted endpoint.
INSTALLATION
Connect your client
Add the endpoint to your client.
Server setup
https://mcp.kaginet.com/sseMCP Clients
Cursor
{
"mcpServers": {
"kagikai": {
"url": "https://mcp.kaginet.com/sse",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}Windsurf
{
"mcpServers": {
"kagikai": {
"serverUrl": "https://mcp.kaginet.com/sse",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}