Yault AESP
NPM · @YAULT/AESP · SCANNED AUG 3
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 →
Supply Chain Security86
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency19
- 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 143 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
- 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 Management23
- Stability observed for 7 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · @yault/aesp
claude mcp add xyz-yault-aesp -- npx -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": {
"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.
- 3 Aug 26 +3
- Stability: unverified → 0.23 ▲ functional
- 2 Aug 26 +35
- Provenance: fail → unverified ▼ security
- Install scripts: pass → unverified ▼ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- License: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Maintenance: pass → unverified ▼ functional
- Schema quality: unverified → good ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Licence: Apache-2.0 functional
- 1 Aug 26 +8
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- License: unverified → pass ▲ functional
- Maintenance: unverified → pass ▲ functional
- Licence: Apache-2.0 functional
- 31 Jul 26 −2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −22
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 27 Jul 26 40
First indexed and scored.
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 3 Aug 2026 · Analysed npm/@yault/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 94 packages
94 packages in the resolved dependency tree · 94 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
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.