# Alertio (remote · www.alertio.io)

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

- Trust score: 83/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `www.alertio.io`: 83/100 (this document), [markdown](https://verifymcp.io/servers/io-alertio-alertio/api-mcp.md), [page](https://verifymcp.io/servers/io-alertio-alertio/api-mcp)

## Channel facts

- Endpoint: `https://www.alertio.io/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 84/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2262 tokens (~141/item across 16 items; 7 tools + 9 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Alertio MCP server?

Alertio is a hosted endpoint at https://www.alertio.io/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

```json
{
  "mcpServers": {
    "io-alertio-alertio": {
      "url": "https://www.alertio.io/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-alertio-alertio": {
      "type": "http",
      "url": "https://www.alertio.io/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-alertio-alertio]
url = "https://www.alertio.io/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-alertio-alertio": {
      "type": "remote",
      "url": "https://www.alertio.io/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-alertio-alertio --url 'https://www.alertio.io/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-alertio-alertio:
    url: "https://www.alertio.io/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-alertio-alertio": {
      "Transport": "http",
      "Url": "https://www.alertio.io/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-alertio-alertio -t streamable-http -u 'https://www.alertio.io/api/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 83, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-31 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-24 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-22 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-20 (score 76, +1)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (7)

### `scan_wallet` (~194 tokens)

Scan EVM 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, 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?"

Input parameters:

- `wallet` (string, required): EVM wallet address — must start with 0x and be exactly 42 characters, e.g. 0xabc…1234

Output parameters:

- `positions` (array): Active borrowing positions per protocol and chain
- `totalPositions` (number): Total active borrowing positions found across all protocols

### `scan_solana_wallet` (~134 tokens)

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 for this Solana wallet", "Is this Solana address at risk of liquidation?", "What is this wallet borrowing on Solana?"

Input parameters:

- `wallet` (string, required): Solana wallet address in base58 format — 32 to 44 characters using base58 alphabet (no 0, O, I, or l), e.g. 7xKX…AbCD

Output parameters:

- `positions` (array): Active borrowing positions on Solana
- `totalPositions` (number): Total active borrowing positions found on Solana

### `scan_ton_wallet` (~122 tokens)

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 health factor for this TON wallet?", "Is this TON address at risk on EVAA?", "Check lending risk for EQ…"

Input parameters:

- `wallet` (string, required): TON wallet address in friendly format — must start with EQ or UQ and be exactly 48 characters, e.g. EQD…wxYZ

Output parameters:

- `collateralUsd` (number): Collateral value in USD
- `debtUsd` (number): Debt value in USD
- `healthFactor` (number|null): Health factor, null if collateral price unavailable
- `riskLevel`: Risk tier, null if health factor could not be computed
- `totalPositions` (number): Number of active positions (0 or 1)

### `simulate_liquidation` (~210 tokens)

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 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?"

Input parameters:

- `collateral_drop_pct` (number, required): Percentage drop in collateral value to simulate, e.g. 30 for a 30% price crash. Range: 1–80.
- `wallet` (string, required): EVM wallet address — must start with 0x and be exactly 42 characters, e.g. 0xabc…1234

Output parameters:

- `allSurvived` (boolean): True if every position survives the simulated drop
- `atRiskCount` (number): Positions that would move to AT RISK or DANGER tier
- `liquidatedCount` (number): Positions that would be liquidated (HF < 1.0)
- `positions` (array): Per-position simulation results
- `scenarioDropPct` (number): Simulated collateral price drop percentage

### `calculate_health_factor` (~321 tokens)

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 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".

Input parameters:

- `collateral` (array, required): Collateral legs. Pass one entry per supplied asset; each keeps its own liquidation threshold and the blended figure is derived.
- `collateral_drop_pct` (number): Optional: simulate the collateral falling by this percentage, e.g. 30 for a 30% crash.
- `debt_change_pct` (number): Optional: simulate the borrowed asset's price moving by this percentage. Positive grows the debt and pushes HF down (borrowing a volatile asset); 0 or omitted is stablecoin debt.
- `debt_usd` (number, required): Total borrowed value in USD. Zero means no debt, so no liquidation risk.

Output parameters:

- `blendedThresholdPct` (number): Weighted liquidation threshold across all collateral legs
- `collateralValueUsd` (number): Total collateral value across every leg
- `debtUsd` (number): Total debt used in the calculation
- `dropToLiquidationPct` (number): How far the collateral can fall before the health factor reaches 1.0
- `healthFactor` (number|null): Health factor, or null when there is no debt — with nothing borrowed there is no liquidation point
- `liquidationAtCollateralValueUsd` (number|null): Total collateral value at which liquidation begins, or null when there is no debt
- `riskAdjustedCollateralUsd` (number): Collateral value after each leg is discounted by its own liquidation threshold
- `riskLevel`: Risk tier, or null when there is no debt
- `simulated` (object): Present only when a simulation was requested

### `get_stablecoin_pegs` (~178 tokens)

Stablecoin Peg Status

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?"

Input parameters:

- `symbol` (string): Optional: filter to a single stablecoin by symbol, e.g. "USDC", "DAI", "USDT". Case-insensitive. Omit to get all top stablecoins.

Output parameters:

- `coins` (array): Stablecoin peg status
- `depeggedSymbols` (array): Symbols currently showing a depeg signal (>0.5% deviation)

### `get_market_utilization` (~194 tokens)

Aave V3 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. 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?"

Input parameters:

- `asset` (string): Optional: filter by asset symbol, e.g. "USDC" or "WETH". Case-insensitive. Omit for all assets across all chains.
- `chain` (string): Optional: filter by chain name. Omit for all 7 chains.

Output parameters:

- `aboveOptimalCount` (number): Number of markets above optimal utilization
- `frozenCount` (number): Number of frozen markets
- `markets` (array): Aave V3 market utilization data
- `pausedCount` (number): Number of paused markets

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-alertio-alertio/api-mcp#diagnostics

## Score history

- 2026-11-05: 83
- 2026-11-04: 83
- 2026-11-03: 82
- 2026-11-02: 82
- 2026-11-01: 81
- 2026-10-31: 81
- 2026-10-30: 80
- 2026-10-29: 80
- 2026-10-28: 79
- 2026-10-27: 79
- 2026-10-26: 78
- 2026-10-25: 78
- 2026-10-24: 78
- 2026-10-23: 77
- 2026-10-22: 77
- 2026-10-21: 76
- 2026-10-20: 76
- 2026-10-19: 75

## Common questions

### What is the Alertio MCP server?

Alertio is an MCP server listed in the public MCP registry as io.alertio/alertio. Real-time DeFi risk data: health factors, liquidations, stablecoin pegs, utilization. No API key. This page covers its hosted endpoint (https://www.alertio.io/api/mcp).

### Is the Alertio MCP server safe to use?

Alertio scores 83 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Alertio MCP server expose?

Alertio exposes 7 tools: scan_wallet, scan_solana_wallet, scan_ton_wallet, simulate_liquidation, calculate_health_factor, and 2 more. Their descriptions and schemas cost roughly 1,353 tokens of context every time the server is loaded.

### Does the Alertio MCP server require authentication?

No. We connected to Alertio without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Alertio MCP server still maintained?

Alertio is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://www.alertio.io/api/mcp
- Repository: https://github.com/alertio/alertio-mcp
- Website: https://www.alertio.io/
- Changelog RSS feed: https://verifymcp.io/servers/io-alertio-alertio/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-alertio-alertio/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/io-alertio-alertio/api-mcp