MCP serverfi.brighter/brighter

Daily closing prices for one asset over a calendar year, for checking a rule's premise against what actually happened.

Run a strategy you have written against real market history and return its figures. This is a real backtest against real prices — not a simulation and not cached per call — so run

Run a published strategy over real market history with parameters of your choosing. Returns its figures against its benchmark. Values outside a parameter's range are snapped into i

Check a strategy written in Brighter's language: syntax, semantics, and whether every ticker it names is one Brighter can actually trade. Returns the faults with their line and col

How to write a Brighter strategy: the language's blocks, indentation rules, indicators and limits. Read this before writing any rule — the language is small and specific, and guess

Search the assets a Brighter strategy can hold — tokenized US stocks, ETFs and T-bills. A rule may only name a ticker that appears here.

Rewrite a strategy in the language's canonical form — the spelling Studio's editor shows. Useful for checking that what you wrote means what you think it means.

What a published strategy's rule holds right now, in basis points of the portfolio. This is the live target, computed from the latest close.

One strategy in full: what its rule does, the parameters you can tune with their ranges and defaults, every asset it can hold, and its benchmark. Use the parameter keys with backte

List the strategies published on brighter.fi, newest or best-performing first. Each carries its rebalance cadence, the assets it can hold, and its return over the chosen period aga

The JSON schema for a strategy as an object, for when you would rather build the rule tree than write the text. check_strategy and backtest_code both accept text, which is usually