Sentinel Aleph
com.ribqa/sentinel-aleph · 2.0.3
Crypto signals, public ledger, BTC chart read, news, your strategies and backtests. No trading.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 60 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 15 of 15 | The registry entry declares a key or a token. |
| Latest connection test reached it | 20 of 20 | The latest test had its handshake answered. |
Where it answers
https://ribqa.com/api/v1/mcpstreamable-httpAuthorizationoptional, secret: Bearer <API key from the ribqa.com account page>. Only get_my_bots, get_my_strategies, get_strategy, create_strategy, update_strategy, delete_strategy, run_backtest, get_my_backtests and get_backtest
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 16 tools.
- Protocol
- 2025-06-18
- Calls itself
- sentinel-aleph 2.0.0
- Handshake time
- 343 ms
- HTTP status
- 200
The tools it lists (16, as of 20 hours ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
get_open_signalsLists published signals that are still open (no outcome yet), newest first, from the current stats epoch: entry, stop loss, take-profit levels, planned reward:risk, market (spot or futures), confidence and combo. Use it to see what is live now; for settled results and win rates use get_signal_ledger, and for signals the BTC regime veto cancelled use get_vetoed_signals. symbol and direction filter before limit is applied, so count can be below total_open; a symbol outside the scanned universe returns an error. No key needed (30 calls a minute per IP). Signals are decision inputs, not instructio
get_signal_ledgerSummarises the public ledger's track record: published and open counts, wins, losses and win rate over matured decisive outcomes, per-engine rows, and net P&L after the published cost model. Use it to judge how signals have performed; for what is open now use get_open_signals, and for vetoed signals use get_vetoed_signals. win_rate is null until n reaches 20 (the same floor per engine), and P&L is percentage points summed per trade, not an account return; vetoed and scratched signals are not in the win rate. recent_limit adds that many latest settled outcomes (0 skips them; the full history is
get_vetoed_signalsLists 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. It is not what the signal would have done without the veto. Use it to audit the veto; these signals never appear in get_open_signals and never count in get_signal_ledger's win rate. symbol filters before limit; a symbol outside the scanned universe returns an error. No key needed.
get_market_snapshotReturns 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 candles back from the newest (100 is about 16 days); the summary covers only returned candles within 24h, so a small limit narrows it. Read from the scanner's in-memory buffer, not a live exchange call: a symbol outside the scanned universe returns an error, and one whose candles are not loaded yet (e.g. just after a r
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
com.ribqa/sentinel-aleph, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 8 days ago. The registry entry · ribqa.com