_ registry / mcp streamable-http · checked 14m ago

noonbarbari

https://updates.noonbarbari.xyz

Registry code: b68dcfc9395fb6e3

api record

Read-only crypto backtesting data from Noon Barbari's engine: daily indicator signals for 50 coins, buy-and-hold outcomes, the monthly Crypto Overfitting Index, strategy head-to-heads, a Q&A knowledge base, and a real rate-limited backtest runner. Data is CC BY 4.0 — link to noonbarbari.xyz when displaying it.

endpoint
https://updates.noonbarbari.xyz/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is noonbarbari live?
Yes — it answered the hub's last check (checked 14m ago). It answered 100% of checks over the last 30 days.
Is noonbarbari free to use?
Yes — the hub reached it with no key and no payment.
What tools does noonbarbari have?
11 tools: get_coin_signals, run_backtest, get_dca, compare_strategies, check_overfitting, get_buy_hold, search_answers, search_glossary, ….
Is noonbarbari safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
111ms

last good check

priced tools
0

of 11 tools

_ answered our checks, 90 days 1 checks · signed record
  • degraded → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 11 tools
2 open 9 never probed 2 of 11 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_overfitting_index open 14m ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • list_strategies open 14m ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • get_coin_signals unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "coin": {
          "type": "string",
          "description": "Lower-case ticker, e.g. btc, eth, sol. Omit for all coins."
        }
      },
      "additionalProperties": false
    }
    arguments 10 lines
  • run_backtest unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "strategy",
        "start_date"
      ],
      "properties": {
        "strategy": {
          "type": "string",
          "description": "Strategy name from list_strategies, e.g. super_trend"
        },
        "start_date": {
          "type": "string",
          "description": "ISO date, e.g. 2022-01-01 (2020-01-01 or later)"
        },
        "starting_cash": {
          "type": "number",
          "description": "Starting balance in USD (default 10000, max 1000000)"
        }
      },
      "additionalProperties": false
    }
    arguments 22 lines
  • get_dca unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "coin"
      ],
      "properties": {
        "coin": {
          "type": "string",
          "description": "Lower-case ticker, e.g. btc, eth, sol."
        },
        "amount": {
          "type": "number",
          "description": "USD invested per purchase (default 100)."
        },
        "frequency": {
          "enum": [
            "weekly",
            "monthly"
          ],
          "type": "string",
          "description": "Purchase cadence (default weekly)."
        },
        "start_date": {
          "type": "string",
          "description": "ISO date to start buying from, e.g. 2021-01-01 (optional; default = full history)."
        }
      },
      "additionalProperties": false
    }
    arguments 29 lines
  • compare_strategies unknown never probed

    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').

    mcp-tool

    {
      "type": "object",
      "required": [
        "strategy_a",
        "strategy_b"
      ],
      "properties": {
        "strategy_a": {
          "type": "string",
          "description": "First strategy name, e.g. super_trend"
        },
        "strategy_b": {
          "type": "string",
          "description": "Second strategy name, e.g. ema_crossover"
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
  • check_overfitting unknown 14m ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "sharpe",
        "length_days",
        "n_trials"
      ],
      "properties": {
        "skew": {
          "type": "number",
          "description": "Skewness of the return series (default 0)."
        },
        "sharpe": {
          "type": "number",
          "description": "Annualised Sharpe ratio of the selected backtest."
        },
        "kurtosis": {
          "type": "number",
          "description": "Non-excess kurtosis of returns (Gaussian = 3, the default)."
        },
        "n_trials": {
          "type": "number",
          "description": "How many strategy/parameter variants were tried before picking this one."
        },
        "timeframe": {
          "enum": [
            "1h",
            "4h",
            "1d",
            "1w"
          ],
          "type": "string",
          "description": "Bar timeframe of the returns (default 1d)."
        },
        "length_days": {
          "type": "number",
          "description": "Length of the backtest in calendar days."
        }
      },
      "additionalProperties": false
    }
    arguments 41 lines
  • get_buy_hold unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "coin"
      ],
      "properties": {
        "coin": {
          "type": "string",
          "description": "Lower-case ticker, e.g. btc, eth, sol."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • search_answers unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "description": "Free-text query, e.g. 'why do backtests fail'"
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • search_glossary unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "description": "A term or question, e.g. 'deflated sharpe' or 'what is RSI'."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • query_dataset unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "coin": {
          "type": "string",
          "description": "Ticker, e.g. btc (optional). Omit for all coins."
        },
        "template": {
          "type": "string",
          "description": "Strategy name, e.g. super_trend (optional). Omit for all templates."
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id b68dcfc9395fb6e3.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/b68dcfc9395fb6e3/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/b68dcfc9395fb6e3/badge.svg)](https://brick.blue/agent/b68dcfc9395fb6e3?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on noonbarbari.xyz 1 entry

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.