Alertio
REMOTE · WWW.ALERTIO.IO
Real-time DeFi risk data: health factors, liquidations, stablecoin pegs, utilization. No API key.
Available components
Last scanned (5 hours ago)
Scores higher than 87% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Crypto and Web3
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
- Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +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.
- 2 Nov 26 +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.
- 31 Oct 26 +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.
- 29 Oct 26 +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.
- 27 Oct 26 +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.
- 24 Oct 26 +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.
- 22 Oct 26 +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.
- 20 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://www.alertio.io/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=alertio.io | CN=YE2,O=Let's Encrypt,C=US | 18 Sept 2026 | 17 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 66bba023871bdbcfbba2d6ffe17c7b34818 |
| SANs: *.alertio.io, alertio.io | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.alertio.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| alertio.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval'; style-src 'self' 'unsafe-inline'; img-src 'self' data: https:; connect-src 'self' https: wss:; font-src 'self' data:; frame-src https://auth.privy.io https://verify.walletconnect.com https://verify.walletconnect.org; worker-src blob: 'self'; frame-ancestors 'none'; object-src 'none'; base-uri 'self'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.alertio.io/api/mcp | Verified | 200 | |
| http (plaintext) | http://www.alertio.io/api/mcp | HTTPS enforced | 308 | https://www.alertio.io/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
calculate_health_factor Calculate Health Factor ~321
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".
| Name | Type | Req | Description |
|---|---|---|---|
| collateral | array | yes | 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 | yes | Total borrowed value in USD. Zero means no debt, so no liquidation risk. |
| Name | Type | Req | Description |
|---|---|---|---|
| blendedThresholdPct | number | yes | Weighted liquidation threshold across all collateral legs |
| collateralValueUsd | number | yes | Total collateral value across every leg |
| debtUsd | number | yes | Total debt used in the calculation |
| dropToLiquidationPct | number | yes | How far the collateral can fall before the health factor reaches 1.0 |
| healthFactor | number|null | yes | Health factor, or null when there is no debt — with nothing borrowed there is no liquidation point |
| liquidationAtCollateralValueUsd | number|null | yes | Total collateral value at which liquidation begins, or null when there is no debt |
| riskAdjustedCollateralUsd | number | yes | Collateral value after each leg is discounted by its own liquidation threshold |
| riskLevel | – | yes | Risk tier, or null when there is no debt |
| simulated | object | – | Present only when a simulation was requested |
No examples provided.
get_market_utilization Aave V3 Market Utilization ~194
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?"
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| aboveOptimalCount | number | yes | Number of markets above optimal utilization |
| frozenCount | number | yes | Number of frozen markets |
| markets | array | yes | Aave V3 market utilization data |
| pausedCount | number | yes | Number of paused markets |
No examples provided.
get_stablecoin_pegs Stablecoin Peg Status ~178
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?"
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | – | Optional: filter to a single stablecoin by symbol, e.g. "USDC", "DAI", "USDT". Case-insensitive. Omit to get all top stablecoins. |
| Name | Type | Req | Description |
|---|---|---|---|
| coins | array | yes | Stablecoin peg status |
| depeggedSymbols | array | yes | Symbols currently showing a depeg signal (>0.5% deviation) |
No examples provided.
scan_solana_wallet Scan Solana Wallet ~134
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?"
| Name | Type | Req | Description |
|---|---|---|---|
| wallet | string | yes | Solana wallet address in base58 format — 32 to 44 characters using base58 alphabet (no 0, O, I, or l), e.g. 7xKX…AbCD |
| Name | Type | Req | Description |
|---|---|---|---|
| positions | array | yes | Active borrowing positions on Solana |
| totalPositions | number | yes | Total active borrowing positions found on Solana |
No examples provided.
scan_ton_wallet Scan TON Wallet ~122
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…"
| Name | Type | Req | Description |
|---|---|---|---|
| wallet | string | yes | TON wallet address in friendly format — must start with EQ or UQ and be exactly 48 characters, e.g. EQD…wxYZ |
| Name | Type | Req | Description |
|---|---|---|---|
| collateralUsd | number | yes | Collateral value in USD |
| debtUsd | number | yes | Debt value in USD |
| healthFactor | number|null | yes | Health factor, null if collateral price unavailable |
| riskLevel | – | yes | Risk tier, null if health factor could not be computed |
| totalPositions | number | yes | Number of active positions (0 or 1) |
No examples provided.
scan_wallet Scan EVM Wallet ~194
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?"
| Name | Type | Req | Description |
|---|---|---|---|
| wallet | string | yes | EVM wallet address — must start with 0x and be exactly 42 characters, e.g. 0xabc…1234 |
| Name | Type | Req | Description |
|---|---|---|---|
| positions | array | yes | Active borrowing positions per protocol and chain |
| totalPositions | number | yes | Total active borrowing positions found across all protocols |
No examples provided.
simulate_liquidation Simulate Liquidation ~210
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?"
| Name | Type | Req | Description |
|---|---|---|---|
| collateral_drop_pct | number | yes | Percentage drop in collateral value to simulate, e.g. 30 for a 30% price crash. Range: 1–80. |
| wallet | string | yes | EVM wallet address — must start with 0x and be exactly 42 characters, e.g. 0xabc…1234 |
| Name | Type | Req | Description |
|---|---|---|---|
| allSurvived | boolean | yes | True if every position survives the simulated drop |
| atRiskCount | number | yes | Positions that would move to AT RISK or DANGER tier |
| liquidatedCount | number | yes | Positions that would be liquidated (HF < 1.0) |
| positions | array | yes | Per-position simulation results |
| scenarioDropPct | number | yes | Simulated collateral price drop percentage |
No examples provided.
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.
remote · www.alertio.io
claude mcp add --transport http io-alertio-alertio 'https://www.alertio.io/api/mcp'
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.