Brighter
REMOTE · MCP.BRIGHTER.FI
Browse, backtest and write rule-based portfolios of tokenized US stocks.
Available components
Last scanned (20 hours ago)
Scores higher than 79% of remote servers
Reachable. Last reached 24 Oct 2026.
Category Finance and Payments
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. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability88
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1043 tokens (~80/item across 13 items; 11 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 24 Oct 26 +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.
- 22 Oct 26 +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.
- 20 Oct 26 +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.
- 17 Oct 26 +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.
- 15 Oct 26 +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.
- 13 Oct 26 +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.
- 12 Oct 26 +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.
- 10 Oct 26 +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.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Oct 2026 · Probed https://mcp.brighter.fi/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.brighter.fi | CN=YE1,O=Let's Encrypt,C=US | 17 Sept 2026 | 16 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 65f6f5fdb43f2cdf763ba2ecf9564849835 |
| SANs: mcp.brighter.fi | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.brighter.fi. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| fi. | present | 18073 | 13 | Verified |
| brighter.fi. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.brighter.fi/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.brighter.fi/mcp | HTTPS enforced | 301 | https://mcp.brighter.fi/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
asset_history ~54
Daily closing prices for one asset over a calendar year, for checking a rule's premise against what actually happened.
| Name | Type | Req | Description |
|---|---|---|---|
| ticker | string | yes | Asset ticker, as find_assets returns it. |
| year | integer | yes | Calendar year. |
No output schema declared.
No examples provided.
backtest_code ~87
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.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The strategy, in Brighter's language. |
| range | string | – | Window to test over. |
No output schema declared.
No examples provided.
backtest_strategy ~106
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | 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. |
No output schema declared.
No examples provided.
check_strategy ~73
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.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The strategy, in Brighter's language. |
No output schema declared.
No examples provided.
dsl_reference ~94
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
find_assets ~88
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
format_strategy ~54
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.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The strategy, in Brighter's language. |
No output schema declared.
No examples provided.
get_allocation ~65
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Strategy id. |
| params | object | – | Parameter values by key. Omitted keys use their default. |
No output schema declared.
No examples provided.
get_strategy ~65
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Strategy id, as list_strategies returns it. |
No output schema declared.
No examples provided.
list_strategies ~175
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
strategy_schema ~47
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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.
remote · mcp.brighter.fi
claude mcp add --transport http fi-brighter-brighter 'https://mcp.brighter.fi/mcp'
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.