Yault AESP
NPM · @YAULT/AESP · SCANNED SEP 20
Crypto payments for the agent economy — policy-gated vault operations under human control
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency22
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 191 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 411 tokens (~58/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "yault_transfer" implies "transfer" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Yault AESP MCP server?
Yault AESP runs locally as an npm package, launched with npx -y @yault/aesp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @yault/aesp
claude mcp add xyz-yault-aesp -- npx -y @yault/aesp
{
"mcpServers": {
"xyz-yault-aesp": {
"command": "npx",
"args": [
"-y",
"@yault/aesp"
]
}
}
} {
"servers": {
"xyz-yault-aesp": {
"command": "npx",
"args": [
"-y",
"@yault/aesp"
]
}
}
} codex mcp add xyz-yault-aesp -- npx -y @yault/aesp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"xyz-yault-aesp": {
"type": "local",
"command": [
"npx",
"-y",
"@yault/aesp"
],
"enabled": true
}
}
} openclaw mcp add xyz-yault-aesp --command npx --arg -y --arg @yault/aesp
mcp_servers:
xyz-yault-aesp:
command: "npx"
args: ["-y", "@yault/aesp"] {
"McpServers": {
"xyz-yault-aesp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@yault/aesp"
]
}
}
} assistant mcp add xyz-yault-aesp -t stdio -c npx -a -y @yault/aesp
{
"mcpServers": {
"xyz-yault-aesp": {
"command": "npx",
"args": [
"-y",
"@yault/aesp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
- Security disclosure: unverified → pass ▲ functional
- 18 Sept 26 0
- Security disclosure: pass → unverified ▼ functional
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −3
- Stability: pass → 0.80 functional
- 9 Sept 26 +1
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/@yault/aesp@0.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
yault_check_authorization ~27
Check agent authorization status: operator address, on-chain allowances, and chain config
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
yault_check_balance ~38
Check the vault balance for a wallet address
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Wallet address (hex, with or without 0x prefix) |
No output schema declared.
No examples provided.
yault_deposit ~67
Deposit assets into a Yault ERC-4626 vault for yield generation
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Agent wallet address (must match the API key owner) |
| amount | string | yes | Amount to deposit in underlying asset units (e.g., "100.5" USDC) |
No output schema declared.
No examples provided.
yault_get_balances ~34
Get comprehensive balance breakdown including vault shares, underlying assets, and yield
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Wallet address |
No output schema declared.
No examples provided.
yault_redeem ~63
Redeem shares from a Yault vault to get underlying assets back
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Agent wallet address (must match the API key owner) |
| shares | string | yes | Number of vault shares to redeem (use "max" to redeem all) |
No output schema declared.
No examples provided.
yault_send_payment ~94
Send tokens from a wallet to an arbitrary recipient address (direct ERC-20 transfer)
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Amount to send in underlying asset units (e.g., "0.1" WETH) |
| from_address | string | yes | Sender wallet address (must match API key owner) |
| memo | string | – | Optional memo/note for the payment |
| to_address | string | yes | Recipient wallet address |
No output schema declared.
No examples provided.
yault_transfer ~88
Transfer vault shares from one account to another (must be parent→sub-account)
| Name | Type | Req | Description |
|---|---|---|---|
| amount | string | yes | Amount to transfer in underlying asset units |
| currency | string | – | Currency (default: "USDC") |
| from_address | string | yes | Sender wallet address (must match API key owner) |
| to_address | string | yes | Recipient wallet address (must be an active sub-account) |
No output schema declared.
No examples provided.
What is the Yault AESP MCP server?
Yault AESP is an MCP server listed in the public MCP registry as xyz.yault/aesp. Crypto payments for the agent economy, policy-gated vault operations under human control. This page covers its npm package (@yault/aesp).
Is the Yault AESP MCP server safe to use?
Yault AESP scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Yault AESP MCP server expose?
Yault AESP exposes 7 tools: yault_check_balance, yault_deposit, yault_redeem, yault_transfer, yault_check_authorization, and 2 more. Their descriptions and schemas cost roughly 411 tokens of context every time the server is loaded.
Is the Yault AESP MCP server still maintained?
Yault AESP is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Yault AESP MCP server under?
Yault AESP declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.