
Mcp Transak
io.github.codesparPublished by GitHub account codesparv0.2.0-alpha.3Updated Oct 24, 2026
MCP server for Transak — fiat-to-crypto on/off-ramp across ~170 countries (Partner API)
Overview
Transak Partner API MCP server that lets an assistant quote, create, track and cancel fiat-to-crypto on/off-ramp orders across about 170 countries.
- What you can do
- Quote and price: get fiat-to-crypto quotes, order limits, and network fees
- Create and manage orders: create, update, cancel, list and fetch Transak orders
- Look up coverage: list fiat and crypto currencies, payment methods, countries and their KYC requirements
- Partner account: read account profile and settlement balances, refresh the access token
- Buyer checks: get KYC status and per-user transaction limits
- Webhooks: verify the HMAC-SHA256 signature on a webhook delivery locally
- When to use it
- Use it when an assistant needs to drive a fiat on/off-ramp flow through Transak: comparing corridors and fees, creating or cancelling orders, checking KYC and limits, or reconciling webhooks. It suits agent-commerce setups that route payments across providers rather than pinning to one.
- Requirements
- Runs locally as an npm package over stdio (or an HTTP mode on localhost). Needs Node.js and the environment variables TRANSAK_API_KEY and TRANSAK_API_SECRET from a Transak partner dashboard; TRANSAK_ACCESS_TOKEN is optional and TRANSAK_ENV selects staging (default) or production. Network access to Transak's API is required.
Installation
In SourceWeft
- Open Mcp Transak in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
@codespar/mcp-transak
MCP server for Transak — fiat↔crypto on/off-ramp across ~170 countries with multi-chain coverage (Ethereum, Solana, Polygon, BSC, Bitcoin, Arbitrum, Optimism, Base, and more).
Transak is the natural peer to MoonPay: both solve the same problem (turn local fiat into on-chain crypto, and back), but each has its own partner list, country coverage, and pricing curve. Bundling both lets an agent-commerce flow pick the best route per corridor instead of pinning to one provider.
Why both MoonPay and Transak
- Coverage: MoonPay lists ~160 countries, Transak ~170. The overlaps are large but the edges are meaningful — certain LatAm, MENA, and APAC corridors are stronger on one side than the other.
- Partners: each has a distinct roster of DEX/wallet/dapp partners, which changes KYC reuse and custody posture for a given buyer.
- Pricing: fees, FX spread, and min/max vary per corridor. An agent can call
get_quoteon both, compare, and route. - Redundancy: if one provider rate-limits, de-risks a country, or throws a KYC hold, the other keeps the flow alive.
This MCP server focuses on the Partner API (server-to-server), not the widget. Agents create orders directly, poll status, and reconcile via webhooks.
Status
0.1.0-alpha.1. The public currency, payment-method, and quote endpoints were verified live against api-stg.transak.com. The partner-order endpoint paths (/api/v2/orders, /api/v2/orders/{id}, /cancel, /api/v2/partner/me) follow the documented conventions but a few are only fully visible inside Transak's partner dashboard — expect minor tweaks once you pair this against a real key.
Tools (18)
Environment
Install
Run (stdio)
Run (HTTP)
Docs
- Transak: https://docs.transak.com
- CodeSpar catalog: https://github.com/codespar/mcp-dev-latam
Enterprise
Need governance, budget limits, and audit trails for agent payments? CodeSpar Enterprise adds policy engine, payment routing, and compliance templates on top of these MCP servers.
Authentication
Set these environment variables before launching the server:
TRANSAK_API_KEY(required) — Transak partner API key (from partner dashboard). Used as partnerApiKey query param on public quote endpoint and bundled with api-secret to mint the access-token for Partner API calls.TRANSAK_API_SECRET(required, secret) — Transak partner API secret. Sent as the api-secret header to endpoints that require server-to-server authentication (and used to mint access tokens for order endpoints).TRANSAK_ENV— Environment selector: 'staging' (default) targets https://api-stg.transak.com; 'production' targets https://api.transak.com.
Issue credentials at the provider's developer portal: https://docs.transak.com.
License
MIT
Source: packages/crypto/transak/README.md at commit d0a519a
Tools
0Version history
1- v0.2.0-alpha.3LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts