Sentinel Aleph

Last 30 days

Uptime

100%

Response time

247 ms typical, 257 ms slowest 5%

Last check

4 h ago

Next check

in 2 h

How to call it

Add it to any MCP client that supports remote servers.

{
  "mcpServers": {
    "sentinel-aleph": {
      "type": "http",
      "url": "https://ribqa.com/api/v1/mcp"
    }
  }
}

16 tools

• get_open_signals

  Lists published signals that are still open (no outcome yet), newest first: entry, stop loss, take-profit levels, planned reward:risk, market (spot or futures), confidence and combo. live_state says whether the entry has filled (awaiting_entry, in_position, stop_at_entry) and fla

• get_signal_ledger

  Summarises the public ledger's track record. matured_book is the settled record: one row per Zurich month past the 96-hour maturity guard, with published, entered, take-profit and stop-loss counts, net P&L after the market-aware cost model for every entered position (BTC veto clo

• get_vetoed_signals

  Lists signals the BTC regime veto cancelled in the last 7 days, newest first, with the veto reason, the BTC state that triggered it, and, once scored, how the position actually closed (exit_type, pnl_percent): at the veto price, or at its target or stop if one was reached first.

• get_market_snapshot

  Returns the most recent 4h candles for one scanned symbol, a summary of those inside the last 24h, and the scanner's status. Use it when you need the candle series or data freshness (data_age_seconds); for just the price and window statistics, get_ticker is lighter. limit counts

• get_ticker

  Returns the last price and open, high, low, close, volume and change % over a window for one scanned symbol. Use it for a quick price check; for the candles themselves or the scanner's freshness, use get_market_snapshot. window_hours is counted in whole 4h candles from the scanne

• get_btc_chart_read

  Returns the latest scheduled BTC chart read: an experimental AI read of the BTCUSDT charts (direction, structure, levels) with no measured skill so far, and a rule-based direction beside it. track.scorecard puts the AI's hit rate at +4h/+12h/+24h beside the hit rate a reader with

• get_news

  Returns recent crypto headlines from a fixed list of public feeds, and the latest digest. Use it for context on what is being reported; news is never an input to any signal, so it does not explain why a signal was published (get_open_signals and get_signal_ledger carry the signal

• get_my_bots

  Lists up to 100 Special Bots on the API key's account with status and counters: candidates seen, matched, vetoed, signals produced, last result and last evaluation time. Use it to monitor your own bots; for saved strategies use get_my_strategies, for published signals get_open_si

• get_my_strategies

  Lists the saved strategies on the API key's account, newest first, archived ones included (active false): id, mode, engines, minimum confidence, direction and symbols. Use it to pick the strategy_id that run_backtest, update_strategy and delete_strategy take; for live bot activit

• run_backtest

  Replays one of your saved strategies on historical candles and returns the summary: trade count, win rate, profit factor, drawdown, return and data coverage. Use it to test a strategy from get_my_strategies on past data; it is research, not a forecast, and places no orders. To re

• get_strategy

  Returns one of your saved strategies with the two fields get_my_strategies omits: timeframe (4h when never set) and description. Use it to check a strategy before run_backtest or update_strategy; to browse them all, use get_my_strategies. strategy_id is the uuid create_strategy r

• create_strategy

  Saves a new strategy on the API key's account and returns it with its id. Use it to set up a strategy to test with run_backtest; to change one use update_strategy. Only name is required (defaults: hybrid, min_confidence 60, direction all, 4h); engines take ids from the schema's l

• update_strategy

  Changes fields of one of your saved strategies and returns the updated strategy. Use it to adjust a strategy between run_backtest runs; to make a new one use create_strategy. Only the fields you pass change; engines and symbols replace the whole list. The same tier rules as creat

• delete_strategy

  Archives one of your strategies, as Delete does on the website: it turns inactive, stops counting toward the tier limit, and cannot be reactivated here. Use it to retire a strategy; to change one use update_strategy. strategy_id comes from get_my_strategies, which keeps listing t

• get_my_backtests

  Lists the backtest runs on the API key's account, newest first: id, where it ran (web or mcp), symbol, timeframe, date range, the strategy settings used and the summary stats, without trades. Use it to find a backtest_id for get_backtest or to compare earlier runs; to start a new

• get_backtest

  Returns one of your stored backtest runs with the trades get_my_backtests leaves out: up to the first 100, each with entry and exit time and price, direction, P&L percent and exit type, plus trades_total. Use it to see why a run won or lost after run_backtest or get_my_backtests;

Security scan

• No findings. We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks