This agent monitors a Venus lending position on BNB Chain, stress-tests it against collateral price falls, and repays the minimum amount needed to restore a safe health factor before liquidation. Health factor = (collateral value x each market's liquidation threshold) / debt value. Liquidation becomes possible at 1.0. Bands: SAFE above 1.50, WARNING 1.20 to 1.50, CRITICAL at or below 1.20. An account can hold positions in several Venus pools — Core and the Isolated Pools — and they are SEPARATE RISK SILOS. Collateral in one does not back a borrow in another, so health factors are per pool and never blended; `get_pools` shows them all. Only the Core pool is actionable by this agent. Two risk levels are reported and they mean different things. `risk` is the band of the CURRENT health factor. `effective_risk` also accounts for the stress test, so a position that is WARNING now but CRITICAL after a routine 15% fall reports CRITICAL there. Only `risk` can trigger automatic action. Every tool here is read-only, except `pause`. You CANNOT execute a protection through this interface — `simulate_protection` shows what the agent would do, and only a human can make it do it. You can read ANY address with the `account` argument. The agent can only PROTECT the position it holds the keys for; `get_status` reports that as `protectable`. Useful order: `get_status` for the current picture, `get_stress_test` for what a price fall would do, `simulate_protection` for the repayment that wou
9 verified, 0 failed, 0 observed risk, 1 not checked, on 22 November 2026. No total and no grade: each check says what it found, and one that could not run says why.
No x402 catalogue entry we hold names an address this server takes payment at, so we cannot attribute any income to it. That is a gap in what we can attribute, not evidence that it earns nothing.
13 tools on the last day the list was read, fingerprint 151da63cbb47f9595bd.
Network, block height, gas price, BNB price, and how far the Venus oracle and PancakeSwap spot disagree.
Takes no parameters.
1 agent registrations name this server. A registration is a claim by whoever wrote it, which is why the server itself is asked.
A day counts as answered only when every timed run that day got every request answered; the hourly runs began 6 November 2026. Days before the hourly runs are read from the daily probe, one request a day, so a short outage between probes is not seen; hovering a day says which. Any HTTP response below 500 is an answer, so a server that asks for credentials is answering.
| Day | State | Timed runs | From |
|---|---|---|---|
| 2026-11-22 | Answered | 14 | hourly runs |
| 2026-11-21 | Some runs failed | 23 | hourly runs |
| 2026-11-20 | Answered | 24 | hourly runs |
| 2026-11-19 | Answered | 23 | hourly runs |
| 2026-11-18 | Some runs failed | 24 | hourly runs |
| 2026-11-17 | Answered | 23 | hourly runs |
| 2026-11-16 | Answered | 24 | hourly runs |
| 2026-11-15 | Answered | 23 | hourly runs |
| 2026-11-14 | Some runs failed | 24 | hourly runs |
| 2026-11-13 | Answered | 23 | hourly runs |
| 2026-11-12 | Answered | 23 | hourly runs |
| 2026-11-11 | Answered | 23 | hourly runs |
| 2026-11-10 | Answered | 24 | hourly runs |
| 2026-11-09 | Some runs failed | 23 | hourly runs |
| 2026-11-08 | Answered | 24 | hourly runs |
| 2026-11-07 | Answered | 18 | hourly runs |
| 2026-11-06 | Answered | 15 | hourly runs |
| 2026-11-05 | No answer | 0 | daily probe |
| 2026-11-04 | Answered | 0 | daily probe |
| 2026-11-03 | No answer | 0 | daily probe |
| 2026-11-02 | No answer | 0 | daily probe |
| 2026-11-01 | Answered | 0 | daily probe |
| 2026-10-31 | No answer | 0 | daily probe |
| 2026-10-30 | No answer | 0 | daily probe |
| 2026-10-29 | No answer | 0 | daily probe |
| 2026-10-28 | No answer | 0 | daily probe |
| 2026-10-27 | No answer | 0 | daily probe |
| 2026-10-26 | No answer | 0 | daily probe |
| 2026-10-25 | No answer | 0 | daily probe |
| 2026-10-24 | Answered | 0 | daily probe |
| 2026-10-23 | Answered | 0 | daily probe |
| 2026-10-22 | Answered | 0 | daily probe |
| 2026-10-21 | Answered | 0 | daily probe |
| 2026-10-20 | Answered | 0 | daily probe |
| 2026-10-19 | No answer | 0 | daily probe |
| 2026-10-18 | Answered | 0 | daily probe |
| 2026-10-17 | Answered | 0 | daily probe |
| 2026-10-16 | Answered | 0 | daily probe |
| 2026-10-15 | No answer | 0 | daily probe |
| 2026-10-14 | Answered | 0 | daily probe |
| 2026-10-13 | Answered | 0 | daily probe |
| 2026-10-12 | Answered | 0 | daily probe |
| 2026-10-11 | Answered | 0 | daily probe |
| 2026-10-10 | Answered | 0 | daily probe |
| 2026-10-07 | Answered | 0 | daily probe |
| 2026-10-06 | Answered | 0 | daily probe |
| 2026-10-04 | Answered | 0 | daily probe |
| 2026-10-03 | Answered | 0 | daily probe |
| 2026-10-02 | Answered | 0 | daily probe |
| 2026-10-01 | Answered | 0 | daily probe |
| 2026-09-30 | Answered | 0 | daily probe |
| 2026-09-29 | Answered | 0 | daily probe |
| 2026-09-28 | Answered | 0 | daily probe |
| 2026-09-27 | Answered | 0 | daily probe |
| 2026-09-26 | Answered | 0 | daily probe |
| 2026-09-25 | Answered | 0 | daily probe |
| 2026-09-24 | Answered | 0 | daily probe |
| 2026-09-23 | Answered | 0 | daily probe |
| 2026-09-22 | Answered | 0 | daily probe |
| 2026-09-21 | Answered | 0 | daily probe |
Each day: the median of that day’s runs’ p50 (the line) and of their p95 (the top of the band), in milliseconds, from our server in Europe to the response headers of an MCP initialize request. An observation, not a threshold.
| Day | p50 ms | p95 ms | Runs |
|---|---|---|---|
| 2026-11-22 | 361 | 1253 | 14 |
| 2026-11-21 | 604 | 1096 | 22 |
| 2026-11-20 | 520 | 1193 | 24 |
| 2026-11-19 | 347 | 1075 | 23 |
| 2026-11-18 | 271 | 1036 | 23 |
| 2026-11-17 | 342 | 1029 | 23 |
| 2026-11-16 | 345 | 835 | 24 |
| 2026-11-15 | 262 | 793 | 23 |
| 2026-11-14 | 346 | 1121 | 24 |
| 2026-11-13 | 347 | 1086 | 23 |
| 2026-11-12 | 345 | 1083 | 23 |
| 2026-11-11 | 344 | 1097 | 23 |
| 2026-11-10 | 343 | 1058 | 24 |
| 2026-11-09 | 343 | 840 | 22 |
| 2026-11-08 | 348 | 1064 | 24 |
| 2026-11-07 | 339 | 1031 | 18 |
| 2026-11-06 | 285 | 1051 | 15 |
Each hour: the median p50 of that hour’s runs, times in UTC; the shaded last hour is not complete. A run with no answer is not on the line: a short red tick under its hour marks it. Latest run 22 November 2026, 13:38 UTC: 5 of 5 requests answered, p50 396 ms, p95 1446 ms.
| Hour (UTC) | p50 ms | Runs | With no answer |
|---|---|---|---|
| 2026-11-22 14:00 (now) | — | 0 | 0 |
| 2026-11-22 13:00 | 396 | 1 | 0 |
| 2026-11-22 12:00 | 361 | 1 | 0 |
| 2026-11-22 11:00 | 352 | 1 | 0 |
| 2026-11-22 10:00 | 348 | 1 | 0 |
| 2026-11-22 09:00 | 391 | 1 | 0 |
| 2026-11-22 08:00 | 959 | 1 | 0 |
| 2026-11-22 07:00 | 735 | 1 | 0 |
| 2026-11-22 06:00 | 446 | 1 | 0 |
| 2026-11-22 05:00 | 701 | 1 | 0 |
| 2026-11-22 04:00 | 343 | 1 | 0 |
| 2026-11-22 03:00 | 343 | 1 | 0 |
| 2026-11-22 02:00 | 346 | 1 | 0 |
| 2026-11-22 01:00 | 369 | 1 | 0 |
| 2026-11-22 00:00 | 350 | 1 | 0 |
| 2026-11-21 23:00 | 349 | 1 | 0 |
| 2026-11-21 22:00 | 338 | 1 | 0 |
| 2026-11-21 21:00 | 351 | 1 | 0 |
| 2026-11-21 20:00 | 342 | 1 | 0 |
| 2026-11-21 19:00 | 268 | 1 | 0 |
| 2026-11-21 18:00 | 602 | 1 | 0 |
| 2026-11-21 17:00 | 347 | 1 | 0 |
| 2026-11-21 16:00 | 604 | 1 | 0 |
| 2026-11-21 15:00 | — | 1 | 1 |