Fraxlend Mcp Server

Created By
IQAIcoma year ago
This is a Model Context Protocol (MCP) server to interact with the Fraxlend platform. It allows MCP-compatible clients (like AI assistants, IDE extensions, or custom applications) to access Fraxlend functionalities such as viewing lending statistics, lending, borrowing, adding/removing collateral, repaying and withdrawing.
Overview

what is Fraxlend Mcp Server?

Fraxlend Mcp Server is a Model Context Protocol (MCP) server designed to interact with the Fraxlend platform, enabling MCP-compatible clients to access various lending functionalities.

how to use Fraxlend Mcp Server?

To use the server, set up your environment with the required WALLET_PRIVATE_KEY and utilize the provided commands to interact with the Fraxlend functionalities.

key features of Fraxlend Mcp Server?

  • Fetch lending statistics for specific pairs.
  • Lend and borrow assets from Fraxlend pairs.
  • Add or remove collateral for specific pairs.
  • Repay borrowed assets and withdraw lent assets.
  • Retrieve pair addresses for collateral and borrowed tokens.

use cases of Fraxlend Mcp Server?

  1. Accessing real-time lending statistics for decision-making.
  2. Facilitating asset lending and borrowing in decentralized finance.
  3. Managing collateral for loans in a secure manner.
  4. Automating lending processes through custom applications.

FAQ from Fraxlend Mcp Server?

  • What is required to use the Fraxlend Mcp Server?

You need to set the WALLET_PRIVATE_KEY in your environment to interact with the server.

  • Can I use this server for any Fraxlend pair?

Yes, the server supports any MCP-compatible Fraxlend pair.

  • Is there a cost associated with using the Fraxlend Mcp Server?

The server itself is free to use, but transaction fees may apply depending on the blockchain.

Server Config

{
  "mcpServers": {
    "fraxlend-server": {
      "command": "pnpm",
      "args": [
        "dlx",
        "@iqai/mcp-fraxlend"
      ],
      "env": {
        "WALLET_PRIVATE_KEY": "your_wallet_private_key_here"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
IQAIcom
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago