DePix App MCP
NPM · @DEPIXAPP/MCP · 2 COMPONENTS · SCANNED SEP 20
One MCP: hosted Pix receive + dated charges (26 tools), or local npx non-custodial wallet (62).
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
- Known CVEs were checked across the 179 of 183 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Dependency health was assessed across the 179 of 183 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency71
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Cryptographically verified build provenance (signed, bound to depixapp/depix-mcp). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 15 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability70
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 11460 tokens (~184/item across 62 items; 62 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 83% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety96
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 5 of 6 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "revoke_key" implies "revoke" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Partial
- An AI judge read all 63 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 DePix App MCP server?
DePix App MCP runs locally as an npm package, launched with npx -y @depixapp/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @depixapp/mcp
claude mcp add depixapp-depix-mcp -- npx -y @depixapp/mcp
{
"mcpServers": {
"depixapp-depix-mcp": {
"command": "npx",
"args": [
"-y",
"@depixapp/mcp"
]
}
}
} {
"servers": {
"depixapp-depix-mcp": {
"command": "npx",
"args": [
"-y",
"@depixapp/mcp"
]
}
}
} codex mcp add depixapp-depix-mcp -- npx -y @depixapp/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"depixapp-depix-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@depixapp/mcp"
],
"enabled": true
}
}
} openclaw mcp add depixapp-depix-mcp --command npx --arg -y --arg @depixapp/mcp
mcp_servers:
depixapp-depix-mcp:
command: "npx"
args: ["-y", "@depixapp/mcp"] {
"McpServers": {
"depixapp-depix-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@depixapp/mcp"
]
}
}
} assistant mcp add depixapp-depix-mcp -t stdio -c npx -a -y @depixapp/mcp
{
"mcpServers": {
"depixapp-depix-mcp": {
"command": "npx",
"args": [
"-y",
"@depixapp/mcp"
]
}
}
} 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
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.
- 18 Sept 26 −2
- Stability: pass → 0.90 functional
- 17 Sept 26 +1
- Stability: 0.97 → pass security
- 15 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.
- 13 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.
- 11 Sept 26 −3
- Stability: pass → 0.80 functional
- 10 Sept 26 +1
- Stability: 0.97 → pass security
- 9 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
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/@depixapp/mcp@2.8.7
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | depixapp/depix-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/depixapp/depix-mcp/.github/workflows/publish-mcp.yml@refs/tags/v2.8.7 |
| Rekor log index | 2712424620 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:f58d883453368f6c5112d2098b70cb928ce01dadcf46a6f8a3e424659cdb44d5b89d782d0f78bc834cede55d95d9e0dfb27b8668925f6346b58a756c1 |
Background: How many MCP packages publish verified provenance →
Dependencies 179 packages
| Packages resolved | 179 |
|---|---|
| Stale | 62 |
| No linked repository | 1 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
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 →
wallet_giftcard_price Price a custom gift-card value ~163
Quote the BTC cost (in sats) of a CUSTOM value for a DYNAMIC (range) product before buying — GET /v4/products/price. Use for is_dynamic products (from wallet_list_giftcard_products) whose value you choose within min..max; fixed products already carry their `price_sats`. Gated on giftcardEnabled. Read-only, moves no money.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_name | string | yes | Brand/family name of a RANGE (dynamic) product. |
| country_code | string | – | ISO 3166-1 alpha-2. Defaults to the shop config country. |
| face_value | string|number | yes | The custom face value to quote (within the product's min..max), in the product's fiat currency. |
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string|null | yes | Fiat currency code, when the price response carries it (else null). |
| price_sats | integer | yes | BTC cost in sats for the requested custom value. |
No examples provided.
wallet_list_giftcard_orders List gift-card orders ~53
List the locally tracked gift-card orders (newest first): order id, brand, denomination, beneficiary, amounts and last-known phase. Read-only — no network, no config gate. Moves no money.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| orders | array | yes | Locally tracked gift-card orders, newest first. |
No examples provided.
wallet_list_giftcard_products List a brand's denominations/products ~171
List a brand's products/denominations so you can complete the selection: each entry says whether it is a FIXED denomination (buy with its exact `denomination` string; `price_sats` is the BTC cost) or a DYNAMIC range product (is_dynamic:true — buy with denomination "range" + a `product_value` within `min`..`max`; quote a specific value with wallet_giftcard_price). Returns the FULL list (fixed AND range). Gated on giftcardEnabled. Read-only, moves no money.
| Name | Type | Req | Description |
|---|---|---|---|
| brand_name | string | yes | Brand/family name from wallet_list_giftcards (e.g. "Amazon"). |
| country_code | string | – | ISO 3166-1 alpha-2. Defaults to the shop config country. |
| Name | Type | Req | Description |
|---|---|---|---|
| products | array | yes | The brand's products/denominations — FIXED (pick a denomination) AND range (pick a value in min..max). |
No examples provided.
wallet_list_giftcards List gift-card brands (catalog) ~176
Browse the CryptoRefills catalog for a country: the fulfillable brands (gift cards + mobile top-ups), filtered by `query` (brand/family name) and/or `category`, in-stock first, plus the popular picks and the category keys. The first step of a purchase (brand discovery) — feed a brand into wallet_list_giftcard_products. Gated on the operator's giftcardEnabled toggle (GIFTCARDS_DISABLED when off). Read-only, moves no money.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter by category key (e.g. "streaming"). |
| country_code | string | – | ISO 3166-1 alpha-2 (e.g. BR). Defaults to the shop config country. |
| query | string | – | Filter by brand/family name (case- + accent-insensitive). |
| Name | Type | Req | Description |
|---|---|---|---|
| brands | array | yes | Fulfillable brands (gift cards + mobile recharge), filtered, in-stock first. |
| categories | array | yes | Distinct category keys for further filtering. |
| country_code | string | yes | – |
| popular_brands | array | yes | The operator's popular picks for the country. |
No examples provided.
wallet_list_transactions List transactions ~42
Return the wallet's transaction history (txid, height, timestamp, type, network fee and per-asset balance deltas in base units). Moves no money.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| stale | boolean | – | true when the balance refresh (sync) before this read/spend FAILED and the result reflects the last persisted snapshot — the on-chain state may be newer. Reads never fail on a provider outage; they s… |
| transactions | array | yes | Wallet transaction history, newest-first as LWK returns it. |
No examples provided.
wallet_list_utxos List unspent outputs (UTXOs) ~83
Return the wallet's unspent outputs — per UTXO: asset, amount (base units), the funding txid:vout, the holding address, block height and confirmations. Read-only: signs nothing, spends nothing, reserves nothing. Syncs before reading so the view is current (serves the last snapshot with stale:true if a provider is down).
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| stale | boolean | – | true when the balance refresh (sync) before this read/spend FAILED and the result reflects the last persisted snapshot — the on-chain state may be newer. Reads never fail on a provider outage; they s… |
| utxos | array | yes | The wallet's unspent outputs (read-only view; signs and moves nothing). |
No examples provided.
wallet_pay_lightning_invoice Pay a Lightning invoice ~161
Pay a BOLT11 Lightning invoice by locking L-BTC via a Boltz submarine swap (NON-custodial; L-BTC only, never DePix). MOVES MONEY: the L-BTC lockup passes through the owner's guardrails (value caps; the Lightning payee is checked against the allowlist when it is enabled) BEFORE signing. Returns once the lockup is broadcast; Boltz then pays the invoice, or the lockup auto-refunds on failure (watched in the background, cancelled cleanly on shutdown). Amounts are base units (sats).
| Name | Type | Req | Description |
|---|---|---|---|
| invoice | string | yes | A BOLT11 Lightning invoice (bolt11 / lnbc…). Must carry an amount — zero-amount invoices are rejected. |
| Name | Type | Req | Description |
|---|---|---|---|
| expected_amount_sats | integer | yes | L-BTC locked for the swap (base units). |
| invoice | string | yes | The BOLT11 invoice that was paid. |
| invoice_sats | integer | yes | The decoded BOLT11 amount (sats). |
| lockup_txid | string | yes | The broadcast L-BTC lockup transaction id. |
| post_sync_failed | boolean | – | true when the balance refresh (sync) AFTER this money-moving call failed. The money already moved (see the txid); the next balance read reflects it. This is never a failure of the operation itself. |
| stale | boolean | – | true when the balance refresh (sync) before this read/spend FAILED and the result reflects the last persisted snapshot — the on-chain state may be newer. Reads never fail on a provider outage; they s… |
| swap_id | string | yes | Boltz submarine swap id — track it, and used for refund on failure. |
No examples provided.
wallet_pending List everything in flight ~93
List everything currently IN FLIGHT across the wallet's four durable stores: pending Pix withdrawals, in-flight Boltz swaps (Lightning send/receive and stablecoin), the tracked SideSwap peg-in, and non-terminal SideShift shifts. Each item carries rail, id, state and rail-specific fields. Read-only and local (no network, no signing) — use wallet_recover to re-drive these items. Moves no money.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| pending | array | yes | Everything currently in flight across the four durable stores, newest data as stored. Empty when nothing is pending. |
No examples provided.
wallet_quote Quote conversion routes ~321
Enumerate EVERY candidate conversion route for an intent — from/to asset (DEPIX, USDT, LBTC, BTC, USDC) plus destination network — with per-leg fee/receipt estimates, single-hop AND multi-hop, custodial legs flagged. The SDK never ranks or picks: compare the candidates and pass your chosen route id to wallet_convert (the primary conversion surface). amount_sats is the FROM asset's BASE UNITS. Estimates are best-effort (null + a note when a leg cannot be pre-estimated). Opens short-lived provider quote streams but signs nothing — moves no money.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_sats | string | yes | Amount in the asset's BASE UNITS (sats), as a decimal integer STRING. 1 DePix cent = 1,000,000 sats. Never pass a BRL value here. |
| from | string | yes | Asset to convert FROM: DEPIX, USDT, LBTC (L-BTC), BTC or USDC. |
| from_network | string | – | ORIGIN network of `from`. Liquid assets default to liquid (this wallet's holdings); set it for external inflows (BTC: bitcoin | lightning; inbound USDT: its source network). |
| network | string | – | DESTINATION network of `to` (default liquid). e.g. lightning for a BOLT11 payout, ethereum/tron/… for an external stablecoin delivery. |
| to | string | yes | Asset to convert TO: DEPIX, USDT, LBTC (L-BTC), BTC or USDC. |
| Name | Type | Req | Description |
|---|---|---|---|
| routes | array | yes | EVERY candidate route with chained estimates — the agent compares and chooses; the SDK never ranks. |
No examples provided.
wallet_receive_lightning Receive over Lightning ~129
Receive over Lightning INTO this wallet via a Boltz reverse swap (NON-custodial). Returns a BOLT11 invoice for a payer to pay; once paid, the L-BTC is claimed into your wallet in the background (watched, cancelled cleanly on shutdown). An INFLOW — no guardrail. amount_sats is base units.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_sats | string | yes | Amount in the asset's BASE UNITS (sats), as a decimal integer STRING. 1 DePix cent = 1,000,000 sats. Never pass a BRL value here. |
| Name | Type | Req | Description |
|---|---|---|---|
| amount_sats | string | yes | L-BTC to be received into the wallet (base units). |
| invoice | string | yes | The BOLT11 invoice for the PAYER to pay. Once paid, the L-BTC is claimed into this wallet. |
| lockup_address | string | yes | The Liquid lockup address Boltz will fund. |
| swap_id | string | yes | Boltz reverse swap id. |
No examples provided.
wallet_recover Recover everything pending ~137
Re-run crash recovery for EVERYTHING pending, across all rails: re-broadcast/re-POST pending Pix withdrawals (SAME signed bytes / SAME Idempotency-Key — never a double-pay), reconcile in-flight Boltz swaps (re-attach the watch, claim, or refund the L-BTC lockup), reconcile the tracked SideSwap peg-in, and refresh non-terminal SideShift shifts. Idempotent and safe to call repeatedly; it also runs automatically at boot. It only completes or refunds PREVIOUSLY authorized operations — it never starts a new payment. Returns per-rail counts; see wallet_pending for what is currently in flight.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| boltz | – | yes | Boltz swaps reconciled (re-attach watch / claim / refund), or null when the wallet has no seed. |
| pegin | object | yes | Tracked SideSwap peg-in reconciliation (§5.2). |
| plans | object | yes | Multi-hop conversion plans resumed from the last completed leg (PR-C) — a started leg is never re-executed. |
| sideshift | object | yes | Non-terminal SideShift shifts refreshed into the local log (§5.4). |
| withdrawals | object | yes | Pix withdrawals re-driven (§3.2.9): re-broadcast SAME bytes / re-POST same Idempotency-Key — never a double-pay. |
No examples provided.
wallet_send Send Liquid asset ~174
Sign and broadcast a Liquid send of DePix/L-BTC/USDt to an address. amount_sats is BASE UNITS. MOVES MONEY: passes through the owner's guardrails (per-tx + rolling-24h BRL caps; allowlist if enabled) BEFORE signing. Irreversible once broadcast.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Destination Liquid address (lq1…/ex1…/VJL…/Q…). |
| amount_sats | string | yes | Amount in the asset's BASE UNITS (sats), as a decimal integer STRING. 1 DePix cent = 1,000,000 sats. Never pass a BRL value here. |
| asset | string | yes | Which Liquid asset to send: DEPIX, LBTC (L-BTC) or USDT (USDt). |
| Name | Type | Req | Description |
|---|---|---|---|
| post_sync_failed | boolean | – | true when the balance refresh (sync) AFTER this money-moving call failed. The money already moved (see the txid); the next balance read reflects it. This is never a failure of the operation itself. |
| stale | boolean | – | true when the balance refresh (sync) before this read/spend FAILED and the result reflects the last persisted snapshot — the on-chain state may be newer. Reads never fail on a provider outage; they s… |
| txid | string | yes | The broadcast Liquid transaction id. |
No examples provided.
wallet_shift_usdt Shift USDt cross-network (SideShift — CUSTODIAL) ~351
Send USDt from Liquid to another network (Ethereum, Tron, BNB Smart Chain, Polygon, Solana) via SideShift. *** CUSTODIAL ***: this is the ONE flow where funds LEAVE the non-custodial sphere — you send USDt to SideShift's deposit address and THEY pay out from their reserve on the target network (escrow states, possible review/refund). MOVES MONEY: the USDt send passes through the owner's guardrails (value caps; with the allowlist on, BOTH the destination settle_address AND the refund_address must be opted in) BEFORE signing. amount_sats is USDt BASE UNITS. Irreversible once broadcast; the result carries custodial:true.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_sats | string | yes | Amount in the asset's BASE UNITS (sats), as a decimal integer STRING. 1 DePix cent = 1,000,000 sats. Never pass a BRL value here. |
| network | string | yes | Target network to send USDt to: ethereum, tron (TRC-20), bsc (BEP-20), polygon, or solana (SPL). A Liquid→Liquid USDt move needs no shift — use wallet_send for that. |
| refund_address | string | – | Optional Liquid address SideShift refunds the USDt to if the shift fails. Checked against allowlist.sideshiftRefundAddresses when the allowlist is enabled (§4.3). |
| settle_address | string | yes | FINAL destination address on `network` (0x… for EVM, T… for Tron, base58 for Solana). Checked against the destination allowlist when it is enabled (§4.3). |
| Name | Type | Req | Description |
|---|---|---|---|
| brl_cents | integer | yes | The USDt sent valued in BRL cents — what was counted against the guardrail (§4.3). |
| custodial | boolean | yes | Always true — SideShift is CUSTODIAL: once sent, the funds are in SideShift's custody, not yours. |
| deposit_address | string | yes | SideShift's Liquid deposit address the USDt was sent to — CUSTODIAL: this address is theirs. |
| deposit_amount_sats | string | yes | USDt sent from the wallet (base units, as a decimal string). |
| network | string | yes | The target network the USDt was shifted to. |
| post_sync_failed | boolean | – | true when the balance refresh (sync) AFTER this money-moving call failed. The money already moved (see the txid); the next balance read reflects it. This is never a failure of the operation itself. |
| refund_address | string|null | yes | The refund address, or null when none was set. |
| settle_address | string | yes | The FINAL destination address on the target network. |
| settle_amount | string|null | yes | USDt that will land on the target network (decimal), when quoted. |
| shift_id | string | yes | SideShift shift id — track it at sideshift.ai/orders/<id>. |
| stale | boolean | – | true when the balance refresh (sync) before this read/spend FAILED and the result reflects the last persisted snapshot — the on-chain state may be newer. Reads never fail on a provider outage; they s… |
| status | string | yes | SideShift shift status at creation (waiting/pending/…). |
| txid | string | yes | The broadcast Liquid txid of the USDt send. |
No examples provided.
wallet_status Wallet status ~82
Read wallet operational status: key mode (live/test, derived locally from the sk_ prefix — no API call), whether an API key is configured, whether the seed backup is confirmed, the current guardrail budget (rolling-24h + per-tx caps and usage), and the crash-resume summaries from boot (pending withdrawals + pending conversions). Moves no money.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key_configured | boolean | yes | Whether an API key is set (deposit/withdraw need one). |
| backup_confirmed | boolean | yes | Whether the seed backup was confirmed — receive is gated until true (§2.9). |
| guardrails | object | yes | – |
| mode | string | yes | Key mode, derived LOCALLY from the sk_live_/sk_test_ prefix — no API call (§6.2). |
| pending_conversions | object | yes | Conversion crash-recovery summary from boot (§5): Boltz swaps reconciled, peg-in reconciled, SideShift shifts refreshed. |
| pending_withdrawals | object | yes | Crash-recovery summary from boot (§3.2.9): auto-resumed/re-broadcast/discarded records. |
No examples provided.
wallet_swap_execute Execute a SideSwap quote ~112
Execute a quote from wallet_swap_quote by its swap_quote_id (must run before the quote expires). MOVES MONEY: validates the swap PSET pays your own receive address, signs, and lets SideSwap broadcast. Passes the SENT side through the owner's value guardrails BEFORE signing (market swaps are allowlist-exempt — funds return to your wallet). Irreversible once broadcast.
| Name | Type | Req | Description |
|---|---|---|---|
| swap_quote_id | string | yes | The swap_quote_id returned by wallet_swap_quote. Single-use; execute before it expires. |
| Name | Type | Req | Description |
|---|---|---|---|
| brl_cents | integer | yes | The SENT side valued in BRL cents — what was counted against the guardrail (§4.3). |
| from | string | yes | The asset sold. |
| post_sync_failed | boolean | – | true when the balance refresh (sync) AFTER this money-moving call failed. The money already moved (see the txid); the next balance read reflects it. This is never a failure of the operation itself. |
| recv_amount_sats | string | yes | Base units of `to` received. |
| send_amount_sats | string | yes | Base units of `from` that left the wallet. |
| stale | boolean | – | true when the balance refresh (sync) before this read/spend FAILED and the result reflects the last persisted snapshot — the on-chain state may be newer. Reads never fail on a provider outage; they s… |
| to | string | yes | The asset bought. |
| txid | string | yes | The broadcast Liquid swap transaction id. |
No examples provided.
wallet_swap_quote Quote a SideSwap market swap ~245
Get a live SideSwap market-swap quote between DePix, L-BTC and USDt (NON-custodial — the swap pays back into your OWN wallet). Returns a single-use swap_quote_id to pass to wallet_swap_execute before expires_at_ms. amount_sats and the quoted amounts are BASE UNITS. Opens a short-lived quote socket held server-side until you execute, it expires, or the server shuts down. Moves no money by itself.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_sats | string | yes | Amount in the asset's BASE UNITS (sats), as a decimal integer STRING. 1 DePix cent = 1,000,000 sats. Never pass a BRL value here. |
| from | string | yes | A Liquid asset: DEPIX (BRL-pegged), LBTC (L-BTC) or USDT (USDt). |
| timeout_seconds | integer | – | How long to wait for the first quote tick, in seconds (default 20, hard ceiling 60). |
| to | string | yes | A Liquid asset: DEPIX (BRL-pegged), LBTC (L-BTC) or USDT (USDt). |
| Name | Type | Req | Description |
|---|---|---|---|
| expires_at_ms | integer | yes | Absolute epoch-ms deadline; wallet_swap_execute refuses within a few seconds of it. |
| fee_asset | string|null | yes | Liquid asset id the fee is charged in, or null. |
| fixed_fee_sats | string | yes | SideSwap fixed (network) fee, base units. |
| from | string | yes | The asset being sold. |
| recv_amount_sats | string | yes | Base units of `to` that will be RECEIVED (validated against the PSET on execute). |
| send_amount_sats | string | yes | Base units of `from` that will LEAVE the wallet (dealer-quoted send side). |
| server_fee_sats | string | yes | SideSwap server fee, base units. |
| swap_quote_id | string | yes | Single-use handle — pass to wallet_swap_execute BEFORE expires_at_ms. Bound to a live quote socket. |
| to | string | yes | The asset being bought. |
| ttl_ms | integer | yes | Quote time-to-live in milliseconds from issuance. |
No examples provided.
wallet_sync Sync the wallet ~178
Refresh on-chain state EXPLICITLY. You rarely need this — every balance read and every spend already syncs on your behalf (a received payment shows up on the next wallet_get_balances without a manual sync). Call it with rescan:true for a DEEP cold re-scan from zero when balances look desynchronized (missing transactions, stale amounts): that can take several MINUTES. The default incremental sync is ~seconds when warm. Signs nothing, moves no money.
| Name | Type | Req | Description |
|---|---|---|---|
| rescan | boolean | – | false (default) = fast incremental sync (~seconds warm). true = DEEP cold re-scan from zero — drops the cached update-chain and rebuilds LWK state; use when balances look desynchronized (missing txs,… |
| Name | Type | Req | Description |
|---|---|---|---|
| rescan | boolean | yes | Whether this ran the deep cold re-scan (true) or the incremental sync (false). |
| stale | boolean | – | true when the balance refresh (sync) before this read/spend FAILED and the result reflects the last persisted snapshot — the on-chain state may be newer. Reads never fail on a provider outage; they s… |
| updated | boolean | yes | Whether the scan produced any new on-chain state since the last sync. |
No examples provided.
wallet_to_stablecoin Convert L-BTC to USDC/USDT ~299
Convert L-BTC to USDC/USDT delivered to an external EVM or Tron address via a Boltz chain swap (NON-custodial on the Liquid side; the L-BTC lockup is refundable). MOVES MONEY: the L-BTC lockup passes through the owner's guardrails (value caps; the destination claim_address is checked against the allowlist when it is enabled) BEFORE signing. The EVM legs run in the background after funding. amount_sats is L-BTC base units.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_sats | string | yes | Amount in the asset's BASE UNITS (sats), as a decimal integer STRING. 1 DePix cent = 1,000,000 sats. Never pass a BRL value here. |
| asset | string | yes | Which stablecoin to receive: USDC or USDT. |
| claim_address | string | yes | FINAL recipient address the stablecoin is delivered to: a 0x… EVM address, or a T… Tron (TRC-20) address for network_id=tron. Checked against the destination allowlist when it is enabled (§4.3). |
| network_id | string | yes | Destination network for the stablecoin. EVM: polygon, ethereum, arbitrum, optimism, base. Tron (TRC-20): tron (USDT only). USDC is not available on tron; USDC is not on base for USDT. |
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | The stablecoin being delivered (USDC/USDT). |
| claim_address | string | yes | The FINAL recipient address the stablecoin is delivered to. |
| lock_amount_sats | integer | yes | L-BTC locked for the swap (base units). |
| lockup_txid | string | yes | The broadcast L-BTC lockup transaction id. |
| network_id | string | yes | The destination network. |
| post_sync_failed | boolean | – | true when the balance refresh (sync) AFTER this money-moving call failed. The money already moved (see the txid); the next balance read reflects it. This is never a failure of the operation itself. |
| stale | boolean | – | true when the balance refresh (sync) before this read/spend FAILED and the result reflects the last persisted snapshot — the on-chain state may be newer. Reads never fail on a provider outage; they s… |
| swap_id | string | yes | Boltz chain-swap id. |
No examples provided.
wallet_wait_deposit Wait for deposit ~107
Poll a deposit until it reaches a terminal status (success is depix_sent). Bounded by timeout_seconds (default 300, hard ceiling 900). Moves no money.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The deposit/withdrawal id returned by the matching create tool. |
| interval_seconds | integer | – | Poll spacing in seconds (default 5, min 3). |
| timeout_seconds | integer | – | Give up after this many seconds (default 300, hard ceiling 900). |
| Name | Type | Req | Description |
|---|---|---|---|
| amount_cents | – | – | – |
| created_at | string | – | – |
| id | string | yes | – |
| liquid_txid | string | – | – |
| post_sync_failed | boolean | – | true when the balance refresh (sync) AFTER this money-moving call failed. The money already moved (see the txid); the next balance read reflects it. This is never a failure of the operation itself. |
| rejection_reasons | array | – | – |
| sandbox | boolean | – | – |
| status | string | yes | – |
| type | string | – | – |
| updated_at | string | – | – |
No examples provided.
wallet_wait_withdrawal Wait for withdrawal ~106
Poll a withdrawal until terminal (success is sent; sandbox is confirmed). Bounded by timeout_seconds (default 300, hard ceiling 900). Moves no money.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The deposit/withdrawal id returned by the matching create tool. |
| interval_seconds | integer | – | Poll spacing in seconds (default 5, min 3). |
| timeout_seconds | integer | – | Give up after this many seconds (default 300, hard ceiling 900). |
| Name | Type | Req | Description |
|---|---|---|---|
| amount_cents | – | – | – |
| created_at | string | – | – |
| id | string | yes | – |
| liquid_txid | string | – | – |
| post_sync_failed | boolean | – | true when the balance refresh (sync) AFTER this money-moving call failed. The money already moved (see the txid); the next balance read reflects it. This is never a failure of the operation itself. |
| rejection_reasons | array | – | – |
| sandbox | boolean | – | – |
| status | string | yes | – |
| type | string | – | – |
| updated_at | string | – | – |
No examples provided.
What is the DePix App MCP server?
DePix App MCP is listed in the public MCP registry as io.github.depixapp/depix-mcp. One MCP: hosted Pix receive + dated charges (26 tools), or local npx non-custodial wallet (62). This page covers its npm package (@depixapp/mcp).
Is the DePix App MCP server safe to use?
DePix App MCP scores 87 out of 100 on VerifyMCP. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 DePix App MCP server expose?
DePix App MCP exposes 62 tools: create_checkout, get_checkout, list_checkouts, simulate_checkout_payment, wait_for_checkout, and 57 more. Their descriptions and schemas cost roughly 10,608 tokens of context every time the server is loaded.
Is the DePix App MCP server still maintained?
DePix App MCP 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 DePix App MCP server under?
DePix App MCP 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.