# io.github.codespar/mcp-transak (npm · @codespar/mcp-transak)

MCP server for Transak — fiat-to-crypto on/off-ramp across ~170 countries (Partner API)

- Trust score: 69/100 (medium)
- Change this week: +24
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- npm · `@codespar/mcp-transak`: 69/100 (this document), [markdown](https://verifymcp.io/servers/codespar-mcp-transak/codespar-mcp-transak.md), [page](https://verifymcp.io/servers/codespar-mcp-transak/codespar-mcp-transak)

## Channel facts

- Registry: `npm`
- Package: `@codespar/mcp-transak`
- Version: `0.2.0-alpha.3`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Supply Chain Security**: 86/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 41 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2316 tokens (~128/item across 18 items; 18 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add codespar-mcp-transak -- npx -y @codespar/mcp-transak
```

### Codex

```bash
codex mcp add codespar-mcp-transak -- npx -y @codespar/mcp-transak
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "codespar-mcp-transak": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@codespar/mcp-transak"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add codespar-mcp-transak --command npx --arg -y --arg @codespar/mcp-transak
```

### Hermes

```yaml
mcp_servers:
  codespar-mcp-transak:
    command: "npx"
    args: ["-y", "@codespar/mcp-transak"]
```

### Other

```json
{
  "mcpServers": {
    "codespar-mcp-transak": {
      "command": "npx",
      "args": [
        "-y",
        "@codespar/mcp-transak"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 69, +4)

- [functional improvement] Stability: unverified → 0.27

### 2026-08-02 (score 65, +45)

- [security regression] Provenance: unverified → fail
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Install scripts: unverified → pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional improvement] Schema quality: unverified → excellent
- [functional improvement] License: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Tool coverage: unverified → 100
- [functional] Licence: MIT

### 2026-08-01 (score 20, +14)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-31 (score 6, −39)

- [security regression] Malware scan: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-07-27 (score 45)

First indexed and scored.

## MCP tools (18)

### `create_order` (~383 tokens)

Create a Transak order. Use isBuyOrSell='BUY' to onramp (fiat→crypto, funds delivered to walletAddress) or 'SELL' to offramp (crypto→fiat, payout to the linked bank account). Returns the order object with status, a widget/redirect URL if required, and the partner-side id.

Input parameters:

- `cryptoAmount` (number): Crypto amount. Either fiatAmount or cryptoAmount must be set.
- `cryptoCurrency` (string, required): Crypto ticker (ETH, USDC, USDT, BTC, SOL, MATIC, etc)
- `email` (string, required): Buyer email (used for KYC + receipt)
- `fiatAmount` (number): Fiat amount in major units. Either fiatAmount or cryptoAmount must be set.
- `fiatCurrency` (string, required): ISO-4217 fiat currency code (USD, EUR, BRL, GBP, INR, etc)
- `isBuyOrSell` (string, required): BUY = fiat→crypto onramp; SELL = crypto→fiat offramp
- `network` (string, required): Blockchain network (ethereum, polygon, bsc, solana, bitcoin, arbitrum, optimism, base, etc)
- `partnerCustomerId` (string): Merchant-side stable user id (for returning users)
- `partnerOrderId` (string, required): Merchant-side stable order id (echoed back on webhooks)
- `paymentMethod` (string): Method id from list_payment_methods (credit_debit_card, apple_pay, google_pay, sepa_bank_transfer, pix, upi, etc)
- `redirectURL` (string): URL Transak redirects to after the hosted flow completes
- `themeColor` (string): Optional hex color (no #) for hosted widget branding
- `walletAddress` (string, required): Destination (BUY) or source (SELL) crypto wallet address

### `get_order` (~55 tokens)

Get a Transak order by its Transak order id. Returns full status, fiat/crypto amounts, fees, tx hash (once on-chain), and current state.

Input parameters:

- `id` (string, required): Transak order id (UUID)

### `list_orders` (~215 tokens)

List Transak orders for the partner account. Filter by status, walletAddress, partnerOrderId, isBuyOrSell, or createdAt date range. Use this to reconcile webhook-driven state, run sweeps on pending orders, or pull a partner-period statement.

Input parameters:

- `endDate` (string): ISO-8601 upper bound (createdAt)
- `isBuyOrSell` (string): Filter to BUY (onramp) or SELL (offramp) orders only
- `limit` (number): Max rows to return
- `partnerOrderId` (string): Filter by merchant-side order id
- `startDate` (string): ISO-8601 lower bound (createdAt)
- `status` (string): Filter by status (AWAITING_PAYMENT_FROM_USER, PAYMENT_DONE_MARKED_BY_USER, PROCESSING, COMPLETED, CANCELLED, FAILED, EXPIRED, REFUNDED, ON_HOLD_PENDING_DELIVERY_FROM_TRANSAK)
- `walletAddress` (string): Filter by destination/source wallet address

### `update_order` (~180 tokens)

Update a Transak order after creation. Used for partner-side post-creation actions such as marking a SELL crypto deposit transaction hash, attaching/changing the partnerCustomerId, refreshing the redirectURL, or correcting the buyer email before KYC. Only mutable fields are accepted; immutable fields (amount, currency, network) require a fresh order.

Input parameters:

- `email` (string): Updated buyer email (only before KYC submission)
- `id` (string, required): Transak order id to update
- `partnerCustomerId` (string): New/corrected merchant-side user id
- `redirectURL` (string): Updated post-flow redirect URL
- `status` (string): Partner-set status when applicable (e.g. PAYMENT_DONE_MARKED_BY_USER)
- `transactionHash` (string): On-chain tx hash for SELL orders (buyer's crypto deposit to Transak)

### `cancel_order` (~56 tokens)

Cancel a Transak order. Only works while the order is in a cancellable state (awaiting payment / pending). Completed or in-flight on-chain orders cannot be cancelled.

Input parameters:

- `id` (string, required): Transak order id to cancel

### `get_quote` (~195 tokens)

Get a fiat↔crypto price quote (public, no auth). Returns the rate, fees, min/max, delivery network, and the exact cryptoAmount the buyer receives for a given fiatAmount (or vice versa). Use this before calling create_order to show the user a price they can confirm.

Input parameters:

- `cryptoAmount` (number): Crypto amount. Either fiatAmount or cryptoAmount.
- `cryptoCurrency` (string, required): Crypto ticker (ETH, USDC, BTC, SOL, ...)
- `fiatAmount` (number): Fiat amount. Either fiatAmount or cryptoAmount.
- `fiatCurrency` (string, required): ISO-4217 fiat code (USD, EUR, BRL, GBP, INR, ...)
- `isBuyOrSell` (string, required): BUY or SELL
- `network` (string, required): Blockchain network (ethereum, polygon, solana, ...)
- `paymentMethod` (string): Optional payment method id to price that specific rail

### `get_order_limits` (~193 tokens)

Get the min and max trade amount for a fiat+crypto+country combination — what's the smallest USD a US buyer can spend on USDC/Polygon, and what's the cap before extra KYC kicks in? Public endpoint. Pair with get_quote so you can prevalidate amount before opening the widget.

Input parameters:

- `countryCode` (string): ISO 3166-1 alpha-2 country code (US, GB, BR, IN, ...)
- `cryptoCurrency` (string, required): Crypto ticker (ETH, USDC, BTC, ...)
- `fiatCurrency` (string, required): ISO-4217 fiat code (USD, EUR, BRL, ...)
- `isBuyOrSell` (string, required): BUY or SELL — limits differ between onramp and offramp
- `network` (string): Blockchain network (ethereum, polygon, solana, ...)
- `paymentMethod` (string): Optional payment method id for rail-specific limits

### `list_fiat_currencies` (~52 tokens)

List all fiat currencies Transak supports, with per-currency payment methods, limits, and country restrictions. Public endpoint — safe to call without credentials. Use as a discovery step before rendering a funding flow.

### `list_crypto_currencies` (~43 tokens)

List all crypto assets Transak supports, including network, decimals, pay-in/pay-out eligibility, and jurisdictional restrictions (US state blocklists etc). Public endpoint.

### `list_payment_methods` (~83 tokens)

List payment methods available for a given fiat currency (card, Apple Pay, Google Pay, SEPA, UPI, Pix, wire, etc) with min/max amounts and processing time. Public endpoint. Use to dynamically build a funding-method picker per corridor.

Input parameters:

- `fiatCurrency` (string, required): ISO-4217 fiat code (USD, EUR, BRL, ...)

### `list_countries` (~84 tokens)

List the countries Transak serves, with allowed fiat currencies, payment methods, and KYC requirements per country. Optionally filter by fiatCurrency to see only countries where that fiat is supported. Public endpoint — call this as a discovery step before showing a country picker.

Input parameters:

- `fiatCurrency` (string): Optional ISO-4217 fiat code to restrict to countries supporting that fiat

### `list_network_fees` (~100 tokens)

List the network/gas fees Transak charges (or estimates) per crypto+network combination. Useful for showing buyers the all-in landed cost or for choosing the cheapest network when an asset is multi-chain (e.g. USDC on Polygon vs Ethereum). Public endpoint.

Input parameters:

- `cryptoCurrency` (string): Optional crypto ticker filter (USDC, ETH, ...)
- `network` (string): Optional network filter (ethereum, polygon, solana, ...)

### `get_partner_account` (~41 tokens)

Get the authenticated partner's account profile (name, api key info, configured webhooks, default currencies). Useful for debugging which partner credentials the server is using.

### `get_partner_balance` (~67 tokens)

Get the partner's settlement balance(s) — Transak holds partner liquidity per fiat to fund SELL payouts and reserves earned commissions until they settle. Returns balances broken down by currency, available vs pending, and last-settlement timestamp. Use this to monitor funding levels before promoting a high-volume corridor.

### `refresh_access_token` (~67 tokens)

Mint a fresh short-lived access-token from the partner api-secret. Some Partner API tiers require this token (sent as the access-token header) on order/user endpoints. The token is short-lived (~minutes); cache it and refresh on 401. Returns { accessToken, expiresAt }.

### `get_kyc_status` (~120 tokens)

Get the KYC status of a buyer the partner has previously sent through Transak. Look up by partnerCustomerId (preferred — your stable id) or email. Returns kycStatus (NOT_SUBMITTED, IN_REVIEW, APPROVED, REJECTED, EXPIRED), tier, country, and the timestamps. Use this to skip re-KYC for returning buyers and unlock higher limits.

Input parameters:

- `email` (string): Buyer email (alternative to partnerCustomerId)
- `partnerCustomerId` (string): Your merchant-side stable user id

### `get_user_limits` (~122 tokens)

Get the current per-user transaction limits granted by Transak based on the user's KYC tier and country (daily, weekly, monthly, lifetime caps in fiat). Look up by partnerCustomerId or email. Use before quoting big-ticket purchases so you can warn a buyer they'll need a tier-up flow first.

Input parameters:

- `email` (string): Buyer email (alternative to partnerCustomerId)
- `fiatCurrency` (string): Optional fiat to denominate the limits in (defaults to user's home fiat)
- `partnerCustomerId` (string): Your merchant-side stable user id

### `verify_webhook_signature` (~193 tokens)

Locally verify the HMAC-SHA256 signature on a Transak webhook delivery. Transak signs the raw request body with the partner api-secret as the HMAC key; the signature is delivered in the x-transak-signature header (sometimes also `signature`). Pass the raw body string + the header value and this returns { valid: boolean }. Does NOT call Transak — pure local crypto. Always use this before trusting webhook contents.

Input parameters:

- `rawBody` (string, required): The raw, unparsed webhook request body (bytes-as-utf8 string). Must be the EXACT bytes Transak sent — do not JSON.parse-then-stringify, or the signature will mismatch.
- `secret` (string): Optional override for the partner api-secret (defaults to TRANSAK_API_SECRET env var)
- `signature` (string, required): Hex-encoded signature from the x-transak-signature (or `signature`) header

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/codespar-mcp-transak/codespar-mcp-transak#diagnostics

## Score history

- 2026-08-03: 69
- 2026-08-02: 65
- 2026-08-01: 20
- 2026-07-31: 6
- 2026-07-30: 45
- 2026-07-28: 45
- 2026-07-27: 45

## Links

- npm package: https://www.npmjs.com/package/@codespar/mcp-transak
- Socket report: https://socket.dev/npm/package/@codespar/mcp-transak
- Repository: https://github.com/codespar/mcp-dev-latam
- Changelog RSS feed: https://verifymcp.io/servers/codespar-mcp-transak/codespar-mcp-transak/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/codespar-mcp-transak/codespar-mcp-transak/changelog.json
- HTML version of this page: https://verifymcp.io/servers/codespar-mcp-transak/codespar-mcp-transak