Skip to content

Brighter

by brighter.fi · remote · no sign-in to list tools · v1.0.0 · published by fi.brighter

Browse, backtest and write rule-based portfolios of tokenized US stocks.

Changes · 7
CompareRegistry entry

11 tools: 7 change things and 4 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http brighter https://mcp.brighter.fi/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

11 tools

Changes things 7Claude Code: ask
  • asset_historyDaily closing prices for one asset over a calendar year, for checking a rule's premise against what actually happened.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Daily closing prices for one asset over a calendar year, for checking a rule's premise against what actually happened.
  • backtest_codeRun a strategy you have written against real market history and return its figures.No findings

    Why it is in this group

    • The description's first verb is "run": a word for a change.
    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    Description, as the server wrote it
    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 it deliberately, after check_strategy passes. Returns metrics only, never the curve.
  • backtest_strategyRun a published strategy over real market history with parameters of your choosing.No findings

    Why it is in this group

    • The description's first verb is "run": a word for a change.
    Description, as the server wrote it
    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 it. This is a real backtest, so make each one count.
  • check_strategyCheck a strategy written in Brighter's language: syntax, semantics, and whether every ticker it names is one Brighter can actually trade.No findings

    Why it is in this group

    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    Description, as the server wrote it
    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 column. Costs nothing and calls nothing upstream — check before you backtest.
  • dsl_referenceHow to write a Brighter strategy: the language's blocks, indentation rules, indicators and limits.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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 guessing its syntax wastes a turn.
  • format_strategyRewrite a strategy in the language's canonical form — the spelling Studio's editor shows.No findings

    Why it is in this group

    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    Description, as the server wrote it
    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.
  • strategy_schemaThe JSON schema for a strategy as an object, for when you would rather build the rule tree than write the text.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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 easier.
Only reads 4Claude Code: allow
  • find_assetsSearch the assets a Brighter strategy can hold — tokenized US stocks, ETFs and T-bills.No findings

    Why it is in this group

    • The name "find_assets" says "find": a word for reading.
    Description, as the server wrote it
    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.
  • get_allocationWhat a published strategy's rule holds right now, in basis points of the portfolio.No findings

    Why it is in this group

    • The name "get_allocation" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • get_strategyOne 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.No findings

    Why it is in this group

    • The name "get_strategy" says "get": a word for reading.
    Description, as the server wrote it
    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 backtest_strategy.
  • list_strategiesList the strategies published on brighter.fi, newest or best-performing first.No findings

    Why it is in this group

    • The name "list_strategies" says "list": a word for reading.
    Description, as the server wrote it
    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 against its benchmark. Strategies that can hold leveraged or inverse funds are excluded unless asked for.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http brighter https://mcp.brighter.fi/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__brighter__list_strategies",
      "mcp__brighter__get_strategy",
      "mcp__brighter__get_allocation",
      "mcp__brighter__find_assets"
    ],
    "ask": [
      "mcp__brighter__backtest_strategy",
      "mcp__brighter__asset_history",
      "mcp__brighter__dsl_reference",
      "mcp__brighter__strategy_schema",
      "mcp__brighter__check_strategy",
      "mcp__brighter__format_strategy",
      "mcp__brighter__backtest_code"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as brighter. Review it before you use it.