Skip to content

Brighter MCP server

fi.brighter/brighterbrighter.fistreamable-httpv1.0.0Scanned

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

11 tools: 7 change things and 4 only read.

Tools: 0 delete, 0 irreversible, 7 write, 4 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

7 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Brighter MCP server can do

The Brighter MCP server is published by brighter.fi, a domain the MCP Registry verified. It has 11 tools. It can create or change data (7 tools: backtest_strategy, asset_history, dsl_reference, strategy_schema and 3 more), but cannot delete data. 4 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 15, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

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 4Show 4 read-only tools
  • 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.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:54 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
7
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 7 tools that change things (7 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.brighter.fi/mcp: tools/list returned 11 tools to an anonymous client, including backtest_strategy (write), asset_history (write), dsl_reference (write), strategy_schema (write), check_strategy (write) and 2 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

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
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 or a way out, 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. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as brighter. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/fi.brighter/brighter/verify?hash=14c0de75e01ff10799f67c1dcc5496523d5097d163b6f341e247c55e99555e7b" | jq -e '.changed == false'

Pinned hash 14c0de75e01f, from Nov 15, 2026, 09:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/fi.brighter/brighter/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for fi.brighter/brighter
[![Anlyon Radar](https://radar.anlyon.com/badge/fi.brighter/brighter.svg)](https://radar.anlyon.com/servers/fi.brighter/brighter)

Source: MCP Registry. Synced Oct 21, 2026, 18:12 UTC.

Brighter MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Brighter MCP server safe?

No scan can promise that. What its definitions show: 11 tools, 7 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Brighter MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Brighter MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Brighter MCP server have?

11 tools: 7 write, 4 read. backtest_strategy, asset_history, dsl_reference, strategy_schema, check_strategy, format_strategy, backtest_code, list_strategies and 3 more.

Does the Brighter MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Brighter MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Brighter MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 15, 2026.