Kustodia Escrow

io.github.rodrigojillePublished by GitHub account rodrigojillev2.0.0Updated Oct 30, 2026

Agentic escrow payments — fiat + crypto, 36 MCP tools, 10 chains, FHE privacy

VerifiedSTDIODesktop onlyFinance

Overview

AI-generated overview

Kustodia Escrow gives an assistant tools to create and manage escrow payments in fiat and crypto across 10 chains, with FHE-based privacy.

What you can do
  • Create and manage escrow payment transactions in fiat and cryptocurrency
  • Work across 10 supported blockchains
  • Use 36 MCP tools covering the escrow payment lifecycle
  • Rely on fully homomorphic encryption (FHE) for privacy of payment data
When to use it
When an assistant needs to set up or track escrow payments between parties, in fiat or crypto, as part of an agentic workflow.
Requirements
Runs as a local process over stdio (npm package @kustodia_app/node, SSE transport). Requires a Kustodia API key supplied via the KUSTODIA_API_KEY environment variable, obtained by registering at the Kustodia site. Desktop only.
Before you install
The server handles real money movements in fiat and crypto through escrow, so tools may create, fund, release or change payment state; review actions before approving. It requires a Kustodia API key (KUSTODIA_API_KEY), a secret that should be kept out of logs and shared configs. Payment and party details are sent to the Kustodia service and the relevant chains.

Installation

In SourceWeft

  1. Open Kustodia Escrow in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v2.0.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.