Depixapp MCP Server

@depixapp/mcp npm v2.8.7 Source verified

Published by depixapp — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

DePix App MCP server — agent-facing interface for the DePix App payment gateway. Pure client of the public DePix API (api.depixapp.com): receive Pix payments (checkouts/products) and read transaction status. Non-custodial, holds zero critical credentials.

Trust grade
A
94/100
Last scanned get badge →
Trust
A · 94/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 94/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 6 = 94. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 3

high Shell/command execution in server code (dist/owner-deps.js)MTC-SRC-002

In the server's implementation (`dist/owner-deps.js:68`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: } = await import("node:child_process"); const [command, args] = process.platform === "darwin" ? ["open", [u

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/owner-deps.js

high Shell/command execution in server code (dist/wallet-engine/mcp/host-register.js)MTC-SRC-002

In the server's implementation (`dist/wallet-engine/mcp/host-register.js:168`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: } = await import("node:child_process"); return new Promise((resolve) => { const child = spawn(comma

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/wallet-engine/mcp/host-register.js

high Shell/command execution in server code (dist/wallet-engine/store/unlock-store.js)MTC-SRC-002

In the server's implementation (`dist/wallet-engine/store/unlock-store.js:36`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: } = await import("node:child_process"); return new Promise((resolve) => { const child = spawn(command, [...

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/wallet-engine/store/unlock-store.js

Tools 62

Each tool and what it can reach — statically extracted from the published source.

  • get_checkoutingests untrusted input
  • get_productingests untrusted input
  • get_support_ticketingests untrusted input
  • wallet_list_giftcardsingests untrusted input
  • activate_keyno sensitive capability
  • activate_productno sensitive capability
  • agent_statusno sensitive capability
  • attach_support_ticket_fileno sensitive capability
  • close_support_ticketno sensitive capability
  • configure_depix_railno sensitive capability
Show 52 more tools ↓
  • create_checkoutno sensitive capability
  • create_keyno sensitive capability
  • create_productno sensitive capability
  • deactivate_productno sensitive capability
  • get_accountno sensitive capability
  • get_deposit_statusno sensitive capability
  • get_onboarding_statusno sensitive capability
  • get_vault_statusno sensitive capability
  • get_withdrawal_statusno sensitive capability
  • list_checkoutsno sensitive capability
  • list_product_checkoutsno sensitive capability
  • list_productsno sensitive capability
  • list_support_ticketsno sensitive capability
  • list_webhook_logsno sensitive capability
  • open_support_ticketno sensitive capability
  • register_accountno sensitive capability
  • reply_support_ticketno sensitive capability
  • revoke_keyno sensitive capability
  • set_featured_productsno sensitive capability
  • simulate_checkout_paymentno sensitive capability
  • update_merchant_profileno sensitive capability
  • update_productno sensitive capability
  • verify_domainno sensitive capability
  • wait_for_checkoutno sensitive capability
  • wallet_buy_giftcardno sensitive capability
  • wallet_convertno sensitive capability
  • wallet_create_depositno sensitive capability
  • wallet_create_withdrawalno sensitive capability
  • wallet_diagnosticsno sensitive capability
  • wallet_get_addressno sensitive capability
  • wallet_get_balancesno sensitive capability
  • wallet_get_giftcard_order_statusno sensitive capability
  • wallet_get_guardrailsno sensitive capability
  • wallet_giftcard_priceno sensitive capability
  • wallet_list_giftcard_ordersno sensitive capability
  • wallet_list_giftcard_productsno sensitive capability
  • wallet_list_transactionsno sensitive capability
  • wallet_list_utxosno sensitive capability
  • wallet_pay_lightning_invoiceno sensitive capability
  • wallet_pendingno sensitive capability
  • wallet_quoteno sensitive capability
  • wallet_receive_lightningno sensitive capability
  • wallet_recoverno sensitive capability
  • wallet_sendno sensitive capability
  • wallet_shift_usdtno sensitive capability
  • wallet_statusno sensitive capability
  • wallet_swap_executeno sensitive capability
  • wallet_swap_quoteno sensitive capability
  • wallet_syncno sensitive capability
  • wallet_to_stablecoinno sensitive capability
  • wallet_wait_depositno sensitive capability
  • wallet_wait_withdrawalno sensitive capability

What this scan could not see

Versions 9

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v2.8.7 latest A 94/100 3 1.13.0 2026-09-07
v2.8.6 A 94/100 3 1.13.0 2026-09-04
v2.8.3 A 94/100 3 1.13.0 2026-09-01
v2.7.0 A 94/100 2 1.13.0 2026-08-28
v2.3.1 A 97/100 0 1.13.0 2026-08-27
Show 4 more versions ↓
v2.2.1 A 97/100 0 1.12.1 2026-08-22
v2.2.0 A 97/100 0 1.12.1 2026-08-10
v1.2.0 A 97/100 0 1.12.1 2026-07-29
v1.0.0 A 100/100 0 1.5.0 2026-07-22

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 94/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/depixapp-mcp/badge.svg)](https://mcptrustchecker.com/registry/depixapp-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/depixapp-mcp"><img src="https://mcptrustchecker.com/registry/depixapp-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/depixapp-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @depixapp/mcp --online

Use the free API → How scoring works

More in Finance & Commerce