mcpdirectory.dev
9,129 servers · updated 23 Sept

Fibx MCP server

community Active last commit 17 d
{
  "mcpServers": {
    "fibrous-fibx": {
      "command": "npx",
      "args": [
        "-y",
        "fibx@latest"
      ],
      "env": {
        "FIBX_SESSION_SECRET": "<fibx_session_secret>",
        "FIBX_WC_PROJECT_ID": "<fibx_wc_project_id>"
      }
    }
  }
}
file .mcp.json (in your project root)install npx -y fibxversion 0.10.1

What it does

FibX is an MCP server for DeFi operations on Base, HyperEVM, and Monad chains. It supports token swaps via Fibrous aggregation, portfolio tracking, transfers, and Aave V3 lending on Base, with signing options via WalletConnect, Privy server wallets, or imported private keys.

  • Execute token swaps across Base, HyperEVM, and Monad with optimal routing and auto-slippage management.
  • View cross-chain portfolio balances and DeFi positions with USD valuations.
  • Supply, borrow, repay, and withdraw from Aave V3 markets on Base with transaction simulation before execution.

Tools this server exposes

ToolDoes
quoteGet a price quote for a token swap pair on a specified chain.
tradeExecute a token swap transaction.
balanceCheck wallet balances across connected chains.
portfolioView cross-chain portfolio overview with USD valuations and DeFi positions.
transferSend ETH or any ERC-20 token.
auth_connectPair FibX with an existing wallet via WalletConnect for transaction signing.
auth_loginAuthenticate with email for Privy server wallet signing.
auth_importImport a private key for local wallet signing with encryption.
aave_supplySupply an asset to Aave V3 on Base.
aave_borrowBorrow an asset from Aave V3 on Base.
aave_repayRepay a borrowed asset on Aave V3 on Base.
aave_withdrawWithdraw a supplied asset from Aave V3 on Base.
aave_marketsBrowse available Aave V3 markets on Base.
open_fibxOpen the FibX app UI in hosts that render MCP Apps, showing wallet, balances, signing policy, and swap form.
statusCheck the current authentication and connection status.

Before you enable it

An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.