# Brighter (remote · mcp.brighter.fi)

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

- Trust score: 78/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-24

## Components

- remote · `mcp.brighter.fi`: 78/100 (this document), [markdown](https://verifymcp.io/servers/fi-brighter-brighter/mcp.md), [page](https://verifymcp.io/servers/fi-brighter-brighter/mcp)

## Channel facts

- Endpoint: `https://mcp.brighter.fi/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-24.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 11 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 88/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1043 tokens (~80/item across 13 items; 11 tools + 2 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Brighter MCP server?

Brighter is a hosted endpoint at https://mcp.brighter.fi/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

```json
{
  "mcpServers": {
    "fi-brighter-brighter": {
      "url": "https://mcp.brighter.fi/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "fi-brighter-brighter": {
      "type": "http",
      "url": "https://mcp.brighter.fi/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.fi-brighter-brighter]
url = "https://mcp.brighter.fi/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "fi-brighter-brighter": {
      "type": "remote",
      "url": "https://mcp.brighter.fi/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add fi-brighter-brighter --url 'https://mcp.brighter.fi/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  fi-brighter-brighter:
    url: "https://mcp.brighter.fi/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "fi-brighter-brighter": {
      "Transport": "http",
      "Url": "https://mcp.brighter.fi/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add fi-brighter-brighter -t streamable-http -u 'https://mcp.brighter.fi/mcp'
```

### Other

```json
{
  "mcpServers": {
    "fi-brighter-brighter": {
      "type": "http",
      "url": "https://mcp.brighter.fi/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-24 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-22 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-20 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-17 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-15 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-13 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-12 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 40. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-10 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 33. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (11)

### `list_strategies` (~175 tokens)

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.

Input parameters:

- `assets` (array): Only strategies that can hold any of these tickers.
- `beatsBenchmark` (boolean): Only strategies ahead of their benchmark over the period.
- `cadence` (array): Only these rebalance cadences.
- `leveraged` (boolean): Include strategies that can hold leveraged or inverse funds. Off by default.
- `limit` (integer): How many to return.
- `offset` (integer): Where to start, for paging.
- `period` (string): Window the returns cover.
- `sort` (string): Order of the list.

### `get_strategy` (~65 tokens)

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.

Input parameters:

- `id` (string, required): Strategy id, as list_strategies returns it.

### `backtest_strategy` (~106 tokens)

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.

Input parameters:

- `id` (string, required): Strategy id.
- `params` (object): Parameter values by key, from get_strategy. Omitted keys use their default.
- `range` (string): Backtest window. Only these are kept warm; anything else is refused.

### `get_allocation` (~65 tokens)

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.

Input parameters:

- `id` (string, required): Strategy id.
- `params` (object): Parameter values by key. Omitted keys use their default.

### `find_assets` (~88 tokens)

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.

Input parameters:

- `limit` (integer): How many to return.
- `offset` (integer): Where to start.
- `query` (string): Match against ticker or company name.
- `tickers` (array): Look up these exact tickers.

### `asset_history` (~54 tokens)

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

Input parameters:

- `ticker` (string, required): Asset ticker, as find_assets returns it.
- `year` (integer, required): Calendar year.

### `dsl_reference` (~94 tokens)

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.

Input parameters:

- `indicators` (boolean): Include the full indicator table with every measure's syntax. Off by default; the reference already names them.
- `limits` (boolean): Include the numeric limits a rule must stay inside.

### `strategy_schema` (~47 tokens)

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.

### `check_strategy` (~73 tokens)

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.

Input parameters:

- `code` (string, required): The strategy, in Brighter's language.

### `format_strategy` (~54 tokens)

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.

Input parameters:

- `code` (string, required): The strategy, in Brighter's language.

### `backtest_code` (~87 tokens)

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.

Input parameters:

- `code` (string, required): The strategy, in Brighter's language.
- `range` (string): Window to test over.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/fi-brighter-brighter/mcp#diagnostics

## Score history

- 2026-10-24: 78
- 2026-10-23: 77
- 2026-10-22: 77
- 2026-10-21: 76
- 2026-10-20: 76
- 2026-10-19: 75
- 2026-10-18: 75
- 2026-10-17: 75
- 2026-10-16: 74
- 2026-10-15: 74
- 2026-10-14: 73
- 2026-10-13: 73
- 2026-10-12: 72
- 2026-10-10: 71
- 2026-10-07: 70
- 2026-10-04: 68
- 2026-10-03: 58
- 2026-10-02: 68
- 2026-10-01: 67
- 2026-09-30: 67

## Common questions

### What is the Brighter MCP server?

Brighter is an MCP server listed in the public MCP registry as fi.brighter/brighter. Browse, backtest and write rule-based portfolios of tokenized US stocks. This page covers its hosted endpoint (https://mcp.brighter.fi/mcp).

### Is the Brighter MCP server safe to use?

Brighter scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Brighter MCP server expose?

Brighter exposes 11 tools: list_strategies, get_strategy, backtest_strategy, get_allocation, find_assets, and 6 more. Their descriptions and schemas cost roughly 908 tokens of context every time the server is loaded.

### Does the Brighter MCP server require authentication?

No. We connected to Brighter without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Brighter MCP server still maintained?

Brighter is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.brighter.fi/mcp
- Website: https://brighter.fi/
- Changelog RSS feed: https://verifymcp.io/servers/fi-brighter-brighter/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/fi-brighter-brighter/mcp.json
- HTML version of this page: https://verifymcp.io/servers/fi-brighter-brighter/mcp