Skip to content

Alertio

by alertio.io · remote · no sign-in to list tools · v1.2.0 · published by io.alertio

Real-time DeFi risk data: health factors, liquidations, stablecoin pegs, utilization. No API key.

Changes · 5

7 tools: 5 change things and 2 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http alertio https://www.alertio.io/api/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

7 tools

Changes things 5Claude Code: ask
  • calculate_health_factorCalculates a lending health factor from position inputs, with no wallet or on-chain lookup required.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Calculates a lending health factor from position inputs, with no wallet or on-chain lookup required. Give it collateral (one or more assets, each with its own liquidation threshold) and the debt, and it returns the health factor, the blended threshold, the collateral drop that would trigger liquidation, and the collateral value at which liquidation begins. Optionally simulates a collateral price drop and a change in the borrowed asset's price. Formula: HF = (Σ collateral value × liquidation threshold) ÷ debt. Works for Aave, Morpho, Spark, Kamino and any protocol using the standard formula. Use this when asked: "What is my health factor if I supply 5 ETH at 80% and borrow $6,500?", "How far can ETH fall before I get liquidated?", "What happens to my HF if I add collateral or repay?", "Work out the health factor for this position".

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • scan_solana_walletScans a Solana wallet address for Kamino lending positions and returns active borrowing positions with health factors and liquidation risk.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Scans a Solana wallet address for Kamino lending positions and returns active borrowing positions with health factors and liquidation risk. Health factor < 1.0 means the position is liquidatable. Use this when asked: "Check Kamino health for this Solana wallet", "Is this Solana address at risk of liquidation?", "What is this wallet borrowing on Solana?"

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • scan_ton_walletScans a TON wallet address on the EVAA lending protocol and returns the active borrowing position with health factor and liquidation risk.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Scans a TON wallet address on the EVAA lending protocol and returns the active borrowing position with health factor and liquidation risk. Health factor < 1.0 means the position is liquidatable. Use this when asked: "What is the EVAA health factor for this TON wallet?", "Is this TON address at risk on EVAA?", "Check lending risk for EQ…"

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • scan_walletScans an EVM wallet address across all supported lending protocols and returns every active borrowing position with health factors and liquidation risk.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Scans an EVM wallet address across all supported lending protocols and returns every active borrowing position with health factors and liquidation risk. Covers Aave V3 (7 chains: Ethereum, Base, Arbitrum, Polygon, Optimism, Avalanche, Scroll), Aave V4 (Ethereum Core/Prime/Plus), Spark (Ethereum), Morpho (Ethereum, Base, Arbitrum), Euler (Ethereum, Monad), and Moonwell (Base, Optimism). Health factor < 1.0 means the position is liquidatable. Use this when asked: "Is this wallet at risk of liquidation?", "Show all lending positions for 0x…", "Which protocols is this wallet borrowing from?", "Which of these wallets is closest to liquidation?"

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • simulate_liquidationSimulates the impact of a collateral price drop on all active EVM lending positions for a wallet (Aave V3/V4, Spark, Morpho, Euler, Moonwell).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Simulates the impact of a collateral price drop on all active EVM lending positions for a wallet (Aave V3/V4, Spark, Morpho, Euler, Moonwell). Formula: newHF = currentHF × (1 − drop%). Shows per-position health factor changes and flags which positions would move to AT RISK, DANGER, or LIQUIDATED. Use this when asked: "What happens to this wallet if ETH drops 30%?", "Would this wallet survive a 40% market crash?", "Stress-test this address at -20% collateral", "Which positions are closest to liquidation if the market drops?"

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 2Claude Code: allow
  • get_market_utilizationReturns Aave V3 lending market utilization rates, supply APY, and borrow APY across 7 chains (Ethereum, Base, Arbitrum, Polygon, Optimism, Avalanche, Scroll).No findings

    Why it is in this group

    • The name "get_market_utilization" says "get": a word for reading.
    Description, as the server wrote it
    Returns Aave V3 lending market utilization rates, supply APY, and borrow APY across 7 chains (Ethereum, Base, Arbitrum, Polygon, Optimism, Avalanche, Scroll). High utilization above the optimal rate causes borrow APY to spike sharply. Also shows if a market is frozen or paused. Use this when asked: "What is the USDC utilization on Aave Ethereum?", "Is there room to borrow WETH on Base?", "Which Aave markets are above optimal utilization?", "What is the current borrow rate for USDC on Arbitrum?", "Are any Aave markets frozen?"

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_stablecoin_pegsReturns real-time USD peg data for the top stablecoins (USDT, USDC, DAI, FRAX, crvUSD, USDS, GHO, and more) sourced from DeFiLlama.No findings

    Why it is in this group

    • The name "get_stablecoin_pegs" says "get": a word for reading.
    Description, as the server wrote it
    Returns real-time USD peg data for the top stablecoins (USDT, USDC, DAI, FRAX, crvUSD, USDS, GHO, and more) sourced from DeFiLlama. Shows current price, deviation from $1.00, and market cap. Flags any coin deviating more than 0.5% as a depeg signal. Use this when asked: "Is USDC currently depegged?", "Which stablecoins are showing depeg signals right now?", "What is DAI trading at?", "Are any stablecoins losing their peg?"

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.2.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http alertio https://www.alertio.io/api/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__alertio__get_stablecoin_pegs",
      "mcp__alertio__get_market_utilization"
    ],
    "ask": [
      "mcp__alertio__scan_wallet",
      "mcp__alertio__scan_solana_wallet",
      "mcp__alertio__scan_ton_wallet",
      "mcp__alertio__simulate_liquidation",
      "mcp__alertio__calculate_health_factor"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as alertio. Review it before you use it.