SwapWallet

What SwapWallet MCP server does

The SwapWallet MCP server exposes a remote interface to a user’s SwapWallet account. Read operations cover total portfolio value, individual token balances, account and verification details, deposit addresses, realized and unrealized profit and loss, transaction history, saved contacts, verified IBANs, and the state of action requests.

It also lets an assistant create requests for token swaps, transfers to saved SwapWallet contacts, crypto withdrawals to external addresses, and toman withdrawals to verified bank accounts. These tools create approval requests rather than directly moving funds.

How it works

The service is hosted at https://swapwallet.app/mcp and uses Streamable HTTP with JSON responses. It is stateless and does not use sessions, server-sent events, or batched requests. An MCP client connects to the endpoint and completes OAuth 2.1 authorization with dynamic client registration and PKCE.

After a user signs in with a phone number and SMS code, they review the requested scopes and grant only the access they want. The server exposes tools permitted by those scopes and checks authorization on every call. Access tokens last one hour; refresh tokens remain valid until the user revokes access.

For actions that can move money, the server prices or prepares the request and sends a preview to the user in Telegram. The user can approve or cancel it there. The assistant should use get_action_request to verify the final state and should treat only EXECUTED as completed.

Setup and configuration

There is no local package or process to install. Add the remote URL to an MCP client that supports remote servers, authenticate through the SwapWallet consent flow, and select the required scopes. The repository documents connection commands and configurations for Claude, Claude Code, Cursor, VS Code, Windsurf, Gemini CLI, and Codex CLI.

A SwapWallet account is required. Trading and withdrawals require identity verification, while request tools also require a linked Telegram account. OAuth public clients do not need a client secret or API key.

Tools and capabilities

The read-oriented tools can:

• Return total holdings or selected token balances.
• Show profile, verification, limits, and settings.
• Create or retrieve a token deposit address for a network.
• Report portfolio P&L and filtered transaction history.
• List saved contacts, verified IBANs, and action-request status.

The request tools support swaps, contact transfers, crypto withdrawals, and IRT withdrawals. Their available inputs and token or network values are defined by each tool schema in the server card.

Limitations and notes

There is no permission that allows an agent to execute withdrawals without user approval. With two-factor authentication enabled, crypto withdrawals and transfers cannot be requested through MCP and must be performed in the app. Unanswered Telegram requests expire after 15 minutes.

Crypto and fiat withdrawal requests are described as open-world actions, so applications should handle their inputs carefully. Amounts use decimal strings, and token and network values are schema-defined enums. A pending action means the user has not finished approval; it is not evidence that funds moved.