Skip to main content
Glama
Kaskad-Lending

Kaskad Protocol MCP Server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
supplyA

Supply (deposit) an asset into the Kaskad Protocol lending pool. Earns supply APY. Trust boundary: max 10% of wallet balance per asset per action. Testnet only.

borrowA

Borrow an asset from the Kaskad Protocol lending pool. Requires sufficient collateral. Uses variable rate by default. Trust boundary: max 10% of available borrows per action. Testnet only.

repayA

Repay a borrowed asset on Kaskad Protocol. Pass amount=-1 to repay full debt. Testnet only.

withdrawA

Withdraw a supplied asset from the Kaskad Protocol lending pool. Pass amount=-1 to withdraw all. Testnet only.

setCollateralA

Enable or disable an asset as collateral for the connected wallet on Kaskad Protocol. Required to switch between isolated (WiKAS/IKAS) and standard collateral modes. In Aave v3 isolation mode, only one isolated asset can be active as collateral at a time — disable other collaterals first before enabling an isolated asset.

getMarketsA

Returns the current state of all Kaskad Protocol lending markets on the Igra Galleon Testnet. Includes supply/borrow APY, total supply/borrow in USD, utilization rate, and available liquidity for each asset.

getPositionB

Returns a wallet's current lending/borrowing position on Kaskad Protocol. Includes total collateral, total debt, available borrows, health factor, and per-asset breakdown.

getGovernanceParamsA

Returns live DAO-voted governance parameters from KaskadGovernor (last finalized epoch). Includes: EMISSION_SUPPLIERS_SHARE_BPS (supplier vs borrower KSKD split), eligibility thresholds, treasury allocation ratios, and undistributed emission recycling rate. ALWAYS call this before strategizing positions — these params directly affect KSKD emission yield.

getProtocolInfoA

Returns static metadata about Kaskad Protocol: network info, contract addresses, supported assets, documentation links, and the full AGENTS.md integration guide (includes emission schedule, eligibility rules, gas requirements, and strategy context).

getHistoryB

Returns historical data from the Kaskad Protocol subgraph: recent liquidations, current market APY snapshots, and optionally a user's transaction history (supplies, borrows, repays) and active positions over time. Pass an address to get user-specific history.

getEmissionsA

Returns KSKD emission state: current epoch, emission vault balance (remaining vs total), epoch timing, supplier/borrower split, and TWAL TVL from activity tracker. Use this to understand current emission APY context and vault depletion trajectory.

getUserRewardsA

Returns claimable KSKD rewards for a wallet address. Shows accrued and claimable amounts from emission incentives. Eligibility requires meeting uptime and minimum position thresholds.

stakeKSKDA

Stake KSKD tokens into the stKSKD vault (1:1). Grants governance eligibility (isEligibleSupplier / isEligibleBorrower). Requires MCP_WALLET_KEY.

unstakeKSKDA

Unstake stKSKD shares back to KSKD (1:1). Warning: if balance drops to 0, governance eligibility resets. Requires MCP_WALLET_KEY.

getStakingInfoA

Get stKSKD vault state for a wallet: stKSKD balance, KSKD wallet balance, holding duration.

claimRewardsA

Claim all accrued KSKD rewards for the MCP wallet from the RewardsController. Checks claimable balance first - skips the transaction if nothing to claim. Rewards are earned by meeting epoch uptime and minimum position thresholds.

checkHealthFactorA

Check a wallet's health factor against a threshold. Returns alert:true if HF is below threshold. Use in agent monitoring loops: call on a cron interval and trigger repay() or supply() when alert:true. Alert levels: safe | warning (below threshold) | danger (HF < 1.2) | critical (HF < 1.05, liquidation imminent).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 17 tools

Disambiguation4/5

Each tool targets a distinct operation or data query, and pairs like getUserRewards/claimRewards or getPosition/checkHealthFactor are clearly separated by action versus state or threshold alerting. No true duplicates exist, though a few overlapping data points (APY, health factor) appear in multiple tools.

Naming Consistency3/5

Most names follow a verbNoun camelCase pattern, but the verb style is inconsistent: core lending actions use bare verbs (supply, borrow, repay, withdraw), while queries use get*, monitoring uses check*, and staking tools embed the asset name (stakeKSKD) unlike the lending verbs. The pattern is readable but not uniform enough for a higher score.

Tool Count5/5

17 tools is on the higher end of the ideal range but is well-scoped for a lending protocol that also includes staking, emissions, governance parameters, and rewards. Each tool covers a distinct part of the domain and none feels redundant or gratuitous.

Completeness5/5

The tool surface covers the full lending lifecycle—supply, borrow, repay, withdraw, collateral management—plus health factor monitoring, rewards claiming, staking, and protocol context. There are no obvious missing operations that would prevent an agent from executing or monitoring core protocol flows.

Maintenance

ActivityInactive
ResponsivenessNo issues