mcpbeat

Noon Barbari Backtesting MCP Server

xyz.noonbarbari/backtesting
answering

Noon Barbari Backtesting is answering right now. Last checked 12 min ago. It exposes 11 tools.

Crypto backtesting tools: real backtests with robustness verdicts, daily signals and market data.

Uptime history 39 hours of history
39 hours agonow
100.0%
Uptime 24h
91 of 91 checks
11
Tools
read from the server
176 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

run in your terminal
claude mcp add backtesting --transport http https://noonbarbari.xyz/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "backtesting": {
      "url": "https://noonbarbari.xyz/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.backtesting]
url = "https://noonbarbari.xyz/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "backtesting": {
      "url": "https://noonbarbari.xyz/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "backtesting": {
      "url": "https://noonbarbari.xyz/mcp"
    }
  }
}

Available tools 11

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

overfitting
check_overfitting
Compute the Deflated Sharpe Ratio (Bailey & Lopez de Prado 2014) for YOUR OWN backtest: given its annualised Sharpe, length, and how many strategy variants you tried before selecting it, returns the probability the result is real skill rather than selection luck, the luck bar it must clear, and a plain verdict. Works on any backtest, not just ours.
get_overfitting_index
The Crypto Overfitting Index: the monthly share (%) of default-parameter strategy configurations (10 templates × 50 coins) whose out-of-sample Sharpe turned negative — how much of what backtests promise fails on unseen data. Returns the current reading and full history.
answers
search_answers
Search Noon Barbari's Q&A knowledge base of direct, data-grounded answers about backtesting, overfitting, validation, indicators, risk management and crypto markets. Returns the top matching questions with their full answers.
backtest
run_backtest
Run a real backtest of a strategy template on BTC/USDT from a start date (public what-if engine; may take up to a minute on a cache miss; rate-limited). Returns net return, max drawdown, trade count, a robustness score with an overfitting verdict, and a shareable result URL.
buy
get_buy_hold
What a $1,000 buy of a coin on Jan 1 of each available year would be worth today — ROI, peak value and date, and the maximum drawdown endured along the way. Real Binance data, refreshed daily.
coin
get_coin_signals
Today's daily-bar indicator readings for crypto coins, computed by a real backtesting engine from Binance closes: price, RSI-14, MACD state, SMA 50/200 posture, SuperTrend, Bollinger position, ATR volatility, 52-week range. Pass a coin ticker (e.g. 'btc') for one coin, or omit for the whole 50-coin board.
compare
compare_strategies
Head-to-head comparison of two strategy templates from real monthly engine runs across ~50 coins: per-coin win count, median out-of-sample Sharpe, survival counts, median return and drawdown. Use strategy names from list_strategies (e.g. 'super_trend', 'ema_crossover').
dataset
query_dataset
Query our open 11,440-run curve-fitting study (10 strategy templates x 20 coins, 70/30 in-sample/out-of-sample split). Returns the headline overfitting stats and the tuned picks matching an optional template and/or coin filter — each with in-sample vs out-of-sample Sharpe, the Sharpe haircut, and the in-sample-to-out-of-sample parameter rank correlation.
dca
get_dca
Dollar-cost-averaging outcome for a coin: what buying a fixed dollar amount on a schedule (weekly or monthly) since a start date would be worth today — total invested, units, average cost, current value and ROI — plus the lump-sum comparison and the worst drawdown endured. Real Binance closes, refreshed daily.
glossary
search_glossary
Search Noon Barbari's trading glossary for a plain-language definition of an indicator, metric or concept (RSI, MACD, Sharpe ratio, drawdown, walk-forward, overfitting, and 60+ more). Returns the top matching terms with a short definition, the full explanation, and a link.
strategies
list_strategies
List the strategy templates available for backtesting and comparison (name, title, one-line description). Use the returned `name` value as the strategy identifier in other tools.

Endpoints

URLTransportStateLatencyChecked
https://noonbarbari.xyz/mcp streamable-http answering 182 ms 12 min ago

Noon Barbari Backtesting — questions

Answers built from our own checks of this server.

What can Noon Barbari Backtesting do?
It exposes 11 tools, read directly from the server on our last check. Among them: check_overfitting, compare_strategies, get_buy_hold, get_coin_signals, get_dca, get_overfitting_index and 5 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Noon Barbari Backtesting working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 176 ms. The bar chart above shows every period we have measured.
How do I connect Noon Barbari Backtesting?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Noon Barbari Backtesting need an API key?
No. Noon Barbari Backtesting completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 11 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Noon Barbari Backtesting?
It answers our handshake in 176 ms on average, which is faster than 67% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.