Teller MCP – Borrow USDC & Altcoins (no margin calls)
PassAudited by ClawScan on May 10, 2026.
Overview
This appears to be a coherent Teller MCP server, but it can generate DeFi transaction calldata and sends wallet-related query details to Teller, so users should review outputs before using them with a wallet.
Install only if you are comfortable running a Node-based MCP server from this publisher. Treat generated borrow or repay transactions as financial actions: verify the endpoint, review all calldata and amounts, and require explicit wallet confirmation before signing anything.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If generated transactions are signed, they could approve tokens, open a loan, or repay a loan.
The tool can produce transaction calldata for approvals, borrowing, and repayment. This is disclosed and central to the skill, but becomes high-impact if another tool or user submits it on-chain.
Borrow transaction builder – returns the full set of encoded transactions (approvals + borrow call) ready to submit on-chain.
Do not auto-submit generated calldata. Review the `to`, `data`, `value`, chain, token, amount, and loan terms in a wallet or block explorer before signing.
Teller or any configured replacement API endpoint can see the wallet address and requested loan/repayment parameters.
The MCP tool sends wallet addresses and transaction-building parameters to the configured Teller API provider.
return this.request<BorrowTransactionsResponse>('/borrow-tx', { walletAddress: params.walletAddress, collateralTokenAddress: params.collateralTokenAddress, chainId: params.chainId, poolAddress: params.poolAddress, collateralAmount: params.collateralAmount, principalAmount: params.principalAmount, loanDuration: params.loanDuration });Use the default Teller endpoint only if you trust it, and treat custom `TELLER_API_BASE_URL` values as trusted infrastructure because they can shape returned transaction data.
Compromised or unexpectedly changed dependencies could affect the MCP server runtime.
Installing and running the server relies on npm packages. This is expected for a Node MCP server, and a package-lock is present, but users still inherit normal npm supply-chain risk.
"dependencies": { "@modelcontextprotocol/sdk": "^1.26.0", "zod": "^4.3.6" }, "devDependencies": { "@types/node": "^25.2.3", "tsx": "^4.21.0", "typescript": "^5.9.3" }Install from a trusted copy of the skill, keep the lockfile, and review dependency changes before updating.