Yault AESP runs on your own machine — the client starts it, so there is no endpoint to ping. 41 installs a week from npm. Last commit 15 Apr 2026.
Crypto payments for the agent economy — policy-gated vault operations under human control
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 9 August 2026. No other catalogue keeps this.
We read the source, 4 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
этот файл ставится пользователю, но в репозитории его нет
const ret = new Function(getStringFromWasm0(arg0, arg1));
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add aesp -e 'YAULT_API_KEY=<YAULT_API_KEY>' -- npx -y @yault/aesp
{
"mcpServers": {
"aesp": {
"command": "npx",
"args": [
"-y",
"@yault/aesp"
],
"env": {
"YAULT_API_KEY": "<YAULT_API_KEY>"
}
}
}
}
[mcp_servers.aesp]
command = "npx"
args = ["-y", "@yault/aesp"]
env = { YAULT_API_KEY = "<YAULT_API_KEY>" }
{
"mcpServers": {
"aesp": {
"command": "npx",
"args": [
"-y",
"@yault/aesp"
],
"env": {
"YAULT_API_KEY": "<YAULT_API_KEY>"
}
}
}
}
{
"servers": {
"aesp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@yault/aesp"
],
"env": {
"YAULT_API_KEY": "<YAULT_API_KEY>"
}
}
}
}
Put your own value in place of
<YAULT_API_KEY> (Your Yault API key (obtain from https://yault.xyz). Format: sk-yault-*).
The author’s registry entry marks it as required.
Optional settings from the registry entry, left out of the block above:
YAULT_API_URL (Yault backend base URL).
Verified ROKI Connect payments contract for coding agents: operations, schemas, validator.
S3-compatible European object storage for AI agents. GDPR-compliant, EU-hosted, crypto payments.
AI agent payments with human approval. Local-first, encrypted credentials, budget controls.
Allow, ask, or veto — a policy decision point your agent consults before signing any payment
Budget, payment and audit controls for AI agent API calls and MCP tool calls.
Encrypted, pay-per-use persistent memory storage for AI agents, gated by x402 payments on Base.
Crypto wallet for AI agents: balances, payments, swaps and trading with owner controls.
Decentralized agent memory for the Lightning economy. Nostr identity, L402 payments.
Answers built from our own checks of this server.