Wise MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 107 installs a week from npm. Last commit 16 Oct 2026.
Wise balances, card payments, transfers and recipients, plus transfers you approve twice.
We read the source, 4 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
res.type(type).sendFile(path.join(PUBLIC_DIR, file));
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add wise-mcp -e 'WISE_API_TOKEN=<WISE_API_TOKEN>' -- npx -y @blanketbyte/wise-mcp
{
"mcpServers": {
"wise-mcp": {
"command": "npx",
"args": [
"-y",
"@blanketbyte/wise-mcp"
],
"env": {
"WISE_API_TOKEN": "<WISE_API_TOKEN>"
}
}
}
}
[mcp_servers.wise-mcp]
command = "npx"
args = ["-y", "@blanketbyte/wise-mcp"]
env = { WISE_API_TOKEN = "<WISE_API_TOKEN>" }
{
"mcpServers": {
"wise-mcp": {
"command": "npx",
"args": [
"-y",
"@blanketbyte/wise-mcp"
],
"env": {
"WISE_API_TOKEN": "<WISE_API_TOKEN>"
}
}
}
}
{
"servers": {
"wise-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@blanketbyte/wise-mcp"
],
"env": {
"WISE_API_TOKEN": "<WISE_API_TOKEN>"
}
}
}
}
Put your own value in place of
<WISE_API_TOKEN> (Wise personal API token (Wise → Settings → API tokens). Full access to prepare transfers, Read only for answers).
The author’s registry entry marks it as required.
Optional settings from the registry entry, left out of the block above:
WRITES_ENABLED (Set to false for read-only. Writes are always two-step and transfers are paid by you in the Wise app), MAX_TRANSFER_AMOUNT (Optional max amount per transfer, in the source currency).
Xendit payment APIs for AI agents. Payment links, payouts, balances, and transactions.
MCP server for Interswitch APIs: payments, transfers, Verve cards, airtime, and paycodes.
Crypto wallet: balances, P&L, history. Swaps, transfers and withdrawals need Telegram approval.
Give an AI agent its own blockchain wallet: balances, USDC transfers, x402 payments under policy.
Read splose patients, appointments, invoices, cases; book and cancel appointments, record payments.
Your AI pays with a TunaPay prepaid card. You approve each payment in Telegram or on tunapay.ai.
Authorize and prove autonomous x402/AP2 agent payments with cryptographic receipts.
Crypto wallet for AI agents: balances, payments, swaps and trading with owner controls.
Answers built from our own checks of this server.