Labsco
MCP SERVER

Lend Fraxswap LP tokens to a BAMM contract, borrow against collateral, and move the position — add, remove, repay — from the agent.

Wallets, Signing & Transaction ExecutionVerified
Summary
It holds a wallet private key, which makes it the most consequential entry in a config rather than one more integration.

WALLET_PRIVATE_KEY is the only credential, and LEND, BORROW, REPAY, ADD_COLLATERAL and REMOVE_COLLATERAL each move value with it. There is no confirm flag, no simulation tool and no read-only mode anywhere in this set. The reading side is thin against that: GET_POSITIONS for what you hold and POOL_STATS for the pools, which is enough to decide with but not enough to preview a transaction before it is signed. Treat the descriptions as the whole documentation on offer — each is a single line, so slippage, gas and failure behaviour are simply not covered.

What it is

A BAMM lending client with seven tools covering lending, borrowing, collateral in both directions, repayment, position listing and pool statistics.

What you get
  • Supplying: LEND lends Fraxswap LP tokens to a BAMM contract by address and amount.
  • Borrowing and returning: BORROW takes an amount with a borrow token and its symbol against a BAMM address, and REPAY returns borrowed tokens to that position.
  • Collateral in both directions: ADD_COLLATERAL and REMOVE_COLLATERAL take an amount with a collateral token and its symbol against a BAMM address.
  • Reading state: GET_POSITIONS returns your active BAMM positions, and POOL_STATS returns statistics across the BAMM pools.
Requirements

A funded wallet whose private key is supplied as WALLET_PRIVATE_KEY, since every write here is an on-chain transaction signed with it.

Setup effort

One command plus a key — npx @iqai/mcp-bamm, then supply credentials