Skip to content
Alertio logo

Alertio MCP server

Which servers in the official MCP registry are Alertio's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-21

← Back to Alertio

Whose server it is
  • Registry nameio.alertio/alertioverified in the MCP registry

The registry name sits under alertio.io. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-21
  • Stateanswerschecked 2026-10-21
  • Tools7
  • Server calls itselfAlertio
  • Server version1.2.0
  • Protocol version2025-06-18

On 2026-10-21 the server answered initialize and tools/list without a sign-in. First answer in 177 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.
  • Checked on 2 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 2, the first on 2026-10-21
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
  • Answeredmeasuring2 of the 7 daily checks it takes to print a share
  • Median first answer1372 ms
  • Space in an agent's context≈ 1,920 tokensthe definitions of all its tools (7), which an agent carries on every turn
  • Tool definitionsA · 100 of 100
  • Typed results7 of 7 toolsdeclared outputSchema: results come typed, read once
  • Every tool passes all six checks.

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers7 tools · read 2026-10-21
  • scan_wallet

    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…

  • scan_solana_wallet

    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…

  • scan_ton_wallet

    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…

  • simulate_liquidation

    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…

  • calculate_health_factor

    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…

  • get_stablecoin_pegs

    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…

  • get_market_utilization

    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…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "alertio": {
      "type": "http",
      "url": "https://www.alertio.io/api/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

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

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://www.alertio.io/api/mcp as a custom connector in the settings.

OpenAPI spec

20 paths, read 2026-10-21. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.