mcp-server-justlend
OfficialRelated Servers
Alternatives to mcp-server-justlend
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceAn MCP server for AI agents to interact with the JustLend DAO lending protocol on TRON, plus general TRON chain utilities like balances, transfers, and staking.375 npmMIT
- AlicenseBqualityCmaintenanceA comprehensive MCP server that enables AI agents to interact with the TRON blockchain, including tools for blockchain data, token transfers, smart contracts, staking, and wallet management.9739 npm24MIT
- AlicenseCqualityDmaintenanceMCP server for TRON blockchain integration, enabling AI assistants to check balances, manage transactions, interact with smart contracts, and access real-time blockchain data.331MIT
- AlicenseNot gradedqualityBmaintenanceMulti-chain wallet MCP server that enables AI agents to manage Bitcoin, Ethereum, Solana, and Tron wallets via tools for addresses, balances, transactions, and token operations.106 npmCC BY-4.0
- FlicenseAqualityDmaintenanceFirst-party MCP server for Kaskad Protocol — a DeFi lending protocol on Igra L2 (Kaspa). Enables AI agents to autonomously supply, borrow, repay, withdraw, and stake. Includes 16 tools covering live market reads, governance params, health factor monitoring, emission state, and full write access to on-chain lending operations. Compatible with Claude, OpenClaw, and any MCP-compatible client.17-
- FlicenseNot gradedqualityDmaintenanceA comprehensive MCP server providing unified access to over 144 tools for lending, trading, and staking across six major DeFi protocols on the Stacks Bitcoin Layer 2. It enables AI agents to perform complex blockchain operations and interact with the DeFi ecosystem using natural language commands.3-
TDQS
Scored across 73 tools
Many tools are explicitly disambiguated in their descriptions (e.g., get_moolah_history vs get_moolah_records), but there are still fuzzy clusters such as claim_rewards vs claim_v1_mining_period, moolah_vault_withdraw vs moolah_vault_redeem, and several overlapping vote/mining status getters. The detailed descriptions help, but the sheer number of similar-sounding getters makes misselection likely.
The server mostly follows a verb_noun snake_case pattern with useful domain prefixes like moolah_, strx_, and energy_rental. However, there are inconsistencies such as moolah_vault_deposit instead of deposit_moolah_vault, generic claim_rewards alongside claim_v1_mining_period, and unprefixed enter_market/exit_market. Overall it is predictable but not perfectly uniform.
73 tools is far beyond the well-scoped 3-15 range and even beyond the 25+ 'too many' threshold. The server bundles V1 lending, V2 Moolah, sTRX staking, energy rental, and governance, which explains the count, but an MCP surface this large is an extreme mismatch for agent usability.
The server covers many domains, but V1 JustLend is missing its core write actions: there is no supply, withdraw, or borrow tool for V1 markets, only repay, collateral entry/exit, approvals, and estimates. This is a major gap that will prevent agents from completing basic lending workflows, and governance also lacks proposal creation.