Skip to content

Folionomiq MCP server

com.folionomiq/folionomiqfolionomiq.comstreamable-httpv1.6.1Scanned

Measures a portfolio from price history: independent bets, what funds own, past crises. No advice.

22 tools: 19 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 19 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

19 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 Folionomiq MCP server can do

The Folionomiq MCP server is published by folionomiq.com, a domain the MCP Registry verified. It has 22 tools. It can create or change data (19 tools: measure_portfolio, test_a_change, portfolio_structure, look_through and 15 more), but cannot delete data. 3 tools only read.

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

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 10, 2026, version 1.6.1.

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.

22 tools

Changes things 19Claude Code: ask
  • asset_infoOne fund or share on its own: name, type, exchange, yearly cost when published, measured return, volatility and worst fall, and for a fund its largest holdings and sectors.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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    One fund or share on its own: name, type, exchange, yearly cost when published, measured return, volatility and worst fall, and for a fund its largest holdings and sectors. Typical questions: 'What is EQQQ.DE?'; 'Tell me about this ETF before I add it.'; 'What's inside VXUS?'. Instead: for a whole portfolio's companies, look_through. Non-US listings need the exchange suffix (VWCE.DE, IWDA.AS); search_symbols finds it. It does not recommend, predict or calculate tax.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: One fund or share: what it is and holds
  • check_before_you_buyBefore adding one new holding to a portfolio: how much of it is already owned through the current funds, whether it adds an independent bet, what past crises would have done with i…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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Before adding one new holding to a portfolio: how much of it is already owned through the current funds, whether it adds an independent bet, what past crises would have done with it, and a decision sheet with three columns: now, the same money kept as cash, the money in the new holding. Typical questions: 'I'm thinking of adding $10,000 of QQQ with new cash: what changes versus keeping it in cash?'; 'Check before I buy SCHD.'; 'Test adding an ETF to my portfolio.'. Instead: for selling, reweighting or several changes at once, test_a_change. The 'after' portfolio was never held; it never says whether to buy. It does not recommend, predict or calculate tax.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Check before you buy
  • currency_effectFor a portfolio held in one currency but priced partly in others: how much is outside the base currency, and what exchange rates added to growth, volatility and the worst fall, aga…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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    For a portfolio held in one currency but priced partly in others: how much is outside the base currency, and what exchange rates added to growth, volatility and the worst fall, against the same holdings currency-hedged. Typical questions: 'I'm in euros but hold US funds: what did the dollar do to me?'; 'How much currency risk is in this?'; 'Hedged or not, what was the difference?'. Limits: Only when some holdings are priced in another currency than the holder's. base must be set to the holder's currency. It does not recommend, predict or calculate tax.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: What exchange rates did to it
  • factor_exposureHow a portfolio's daily moves line up with four common patterns: the market, small versus large, value versus growth, momentum.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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    How a portfolio's daily moves line up with four common patterns: the market, small versus large, value versus growth, momentum. Out: each sensitivity, whether it can be told from zero, and how much of the movement the four explain. Typical questions: 'Am I a growth investor without knowing it?'; 'What style is my portfolio really exposed to?'; 'Is this tilted to small caps?'. Instead: for the number of independent bets, portfolio_structure. It does not recommend, predict or calculate tax.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Sensitivity to common return patterns
  • health_axesOne portfolio read along three separate questions: what its risk is built from, how it behaved when markets broke, and what it returned for the risk taken, each with its own figure…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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    One portfolio read along three separate questions: what its risk is built from, how it behaved when markets broke, and what it returned for the risk taken, each with its own figures and no overall score. Typical questions: 'Is anything off in how my portfolio is built?'; 'How did this hold up in bad markets, and was the return worth the swings?'; 'Check the construction of this portfolio.'. Instead: for the full measurement, measure_portfolio. An axis without enough history comes back without a reading. It does not recommend, predict or calculate tax.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: The portfolio along separate axes
  • last_priceThe latest daily close for each ticker, in its own currency and in the base currency, with the date.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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    The latest daily close for each ticker, in its own currency and in the base currency, with the date. Typical questions: 'What's the last price of VWCE?'; 'Turn 120 shares of VTI into dollars.'; 'Latest close for these tickers.'. Instead: for history and figures of one asset, asset_info. One price per ticker, no history. It does not recommend, predict or calculate tax.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Latest close
  • living_off_itA yearly withdrawal, raised with real inflation, replayed from every start month the history allows: how many starts lasted the full span, how many ran out and when, the lowest poi…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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    A yearly withdrawal, raised with real inflation, replayed from every start month the history allows: how many starts lasted the full span, how many ran out and when, the lowest point from the worst start, and the highest yearly rate that ran out from no start in the record. Typical questions: 'Can I live off $1M taking $40,000 a year for 30 years?'; 'Would a 4% withdrawal have lasted on this portfolio?'; 'How long would this money have lasted in retirement?'. Instead: for money put in every month instead, monthly_plan. A count of past starts, never a probability. It does not recommend, predict or calculate tax.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Living off it: withdrawals replayed
  • look_throughThe companies a portfolio owns through its funds, added up across funds.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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    The companies a portfolio owns through its funds, added up across funds. In: holdings. Out: the largest companies with their share of the whole portfolio, companies reached through more than one fund, the part of the money that buys a company a second time, sectors, and how much of the money could be named. Typical questions: 'How much do my ETFs overlap?'; 'What companies do I really own through VTI, QQQ and VXUS?'; 'How much NVIDIA do I hold through my funds?'. Instead: for one fund on its own, asset_info. Figures are minimums where a fund shows only its largest holdings; the answer says how much of the money is named. It does not recommend, predict or calculate tax.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: What the funds hold underneath
  • measure_portfolioThe full measurement of one portfolio in one call.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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    The full measurement of one portfolio in one call. In: holdings as weights or money amounts. Out: how many independent bets they make, each holding's share of the risk beside its share of the money, the companies owned through the funds, what past crises did and how long recovery took, and the numbered report. Typical questions: 'Analyze my portfolio: 60% VTI, 30% VXUS, 10% BND.'; 'What should I know about what I hold?'; 'Give me the full picture of this portfolio.'. Instead: for one narrow question use the narrower tool: portfolio_structure (spread of risk), look_through (companies), past_crises (crashes). For a quotable text with numbered figures, portfolio_report. For the shortest answer, plain_findings. It does not recommend, predict or calculate tax.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Measure a portfolio
  • monthly_planThe same amount bought on the first trading day of each month, replayed on a portfolio's own history with dividends reinvested: what it became against what was put in, the deepest …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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    The same amount bought on the first trading day of each month, replayed on a portfolio's own history with dividends reinvested: what it became against what was put in, the deepest point below the money put in, and the same plan from every possible starting January. Typical questions: 'If I put $500 a month into these, what would it have become?'; 'Dollar-cost averaging into VTI since 2007?'; 'Monthly investing: what was the hardest stretch?'. Instead: for withdrawals, living_off_it. For the record itself, return_history. Before taxes and fees. It does not recommend, predict or calculate tax.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Money in every month, replayed
  • past_crisesWhat past crises did to one portfolio held as it is today: 2008, 2020, 2022 and the others inside its price history.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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    What past crises did to one portfolio held as it is today: 2008, 2020, 2022 and the others inside its price history. In: holdings. Out: for each crisis the deepest fall, the worst day and the days until the previous high came back; crises before a holding existed are named as not tested. Typical questions: 'How much would 2008 have cost me with 60% VTI, 20% VXUS, 20% BND?'; 'What did the 2020 crash do to this mix?'; 'Simulate a market crash on my portfolio.'. Instead: for a loss chosen by the reader ('what would it take to lose 30%?'), reverse_stress. For the whole record, return_history. Holdings in money give each fall in money; in percentages the falls are percentages. It does not recommend, predict or calculate tax.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: What past crises did to this mix
  • plain_findingsThree or four plain sentences about one portfolio, how its risk is built and its worst historical fall, each with its window.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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Three or four plain sentences about one portfolio, how its risk is built and its worst historical fall, each with its window. Typical questions: 'Explain my portfolio simply.'; 'In plain words, what should I know?'; 'I'm new to investing: what does this portfolio look like?'. Instead: for the figures in full, measure_portfolio. For a quotable numbered report, portfolio_report. It does not recommend, predict or calculate tax.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: The findings in plain words
  • portfolio_reportThe written report on one portfolio, every figure numbered F1, F2… beside its method and window.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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    The written report on one portfolio, every figure numbered F1, F2… beside its method and window. In: holdings. Out: a text to quote or keep. Typical questions: 'Write me a report on this portfolio I can keep.'; 'Give me the numbers with their sources.'; 'A citable summary of my portfolio, please.'. Instead: for the full structured measurement, measure_portfolio (which includes this report). For a few plain sentences, plain_findings. It does not recommend, predict or calculate tax.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: The numbered report
  • portfolio_structureHow many independent bets a portfolio's holdings make, from how their prices moved together rather than how many tickers there are, and each holding's share of the risk beside its …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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    How many independent bets a portfolio's holdings make, from how their prices moved together rather than how many tickers there are, and each holding's share of the risk beside its share of the money, over the full record and recent years. Shares of the risk are Euler contributions and add up to 100%. Typical questions: 'Am I really diversified?'; 'Which of my holdings is behind most of the risk?'; 'Do my four funds move as one?'. Instead: for the companies inside the funds, look_through. For everything at once, measure_portfolio. It does not recommend, predict or calculate tax.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: How many independent bets, and where the risk sits
  • return_historyWhat one portfolio returned over its record: growth per year before and after inflation, best and worst months and years, every 12-month stretch, returns by month and year, and wei…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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    What one portfolio returned over its record: growth per year before and after inflation, best and worst months and years, every 12-month stretch, returns by month and year, and weight drift between rebalances. Typical questions: 'How did this portfolio do over the years?'; 'What was its worst year?'; 'Returns after inflation, please.'. Instead: for crises only, past_crises. For money put in every month, monthly_plan. Past record, not a forecast. It does not recommend, predict or calculate tax.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: The record, month by month
  • reverse_stressStarts from a loss the reader names and finds the least extreme combination of market moves that would cause it on this portfolio, beside the worst each move actually did in the re…1 finding

    Why it is in this group

    • The description's first verb is "start": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "reverse_stress" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "start": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Starts from a loss the reader names and finds the least extreme combination of market moves that would cause it on this portfolio, beside the worst each move actually did in the record; also each single company on its own. Typical questions: 'What would it take to lose 30%?'; 'A third of my portfolio is my employer's stock: what would a crash in it take from me?'; 'How bad would markets have to get for me to lose a quarter?'. Instead: for what past crises actually did, past_crises. No probability is computed: it says how large the moves would be, not how likely. It does not recommend, predict or calculate tax.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: What it would take to lose that much
  • sweep_holdingOne holding already in the portfolio, measured at every weight from none to all, the rest of the money shared out in proportion: volatility, its share of the risk and the number of…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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    One holding already in the portfolio, measured at every weight from none to all, the rest of the money shared out in proportion: volatility, its share of the risk and the number of independent bets at each point. Typical questions: 'How much BND does it take to change anything?'; 'Show me my portfolio with 0% to 100% QQQ.'; 'At what weight does gold start to matter here?'. Instead: for one specific change, test_a_change. For a holding not yet owned, check_before_you_buy. It never says which weight to hold. It does not recommend, predict or calculate tax.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: One holding across its whole range
  • test_a_changeAny change to one portfolio, measured before it is made: current and proposed holdings side by side on the same prices.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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Any change to one portfolio, measured before it is made: current and proposed holdings side by side on the same prices. In: two sets of holdings. Out: structure, share of the risk, falls in past crises, and what the change adds or removes; the figures are in the structured result. Typical questions: 'What happens if I sell half my QQQ and buy BND?'; 'Compare my portfolio now with this rebalanced version.'; 'I want to swap VXUS for VWO: before and after?'. Instead: for adding ONE new holding (how much of it is already owned, and a 'kept as cash' column) use check_before_you_buy. For one holding at every weight, sweep_holding. For separate unrelated portfolios, compare_portfolios. It does not recommend, predict or calculate tax.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Before and after a proposed change
  • walk_forwardWhether re-optimising an allocation would have helped: fit on the years before each date, hold on prices not yet seen, repeat, and compare with the portfolio held and with equal we…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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Whether re-optimising an allocation would have helped: fit on the years before each date, hold on prices not yet seen, repeat, and compare with the portfolio held and with equal weights. Typical questions: 'Would an optimiser have beaten my portfolio?'; 'Test max-Sharpe out of sample on these funds.'; 'Does rebalancing to an optimised mix help?'. Limits: Only for that question; it is not for choosing weights and returns no allocation to hold. It does not recommend, predict or calculate tax.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Would refitting have helped? (out of sample)
Only reads 3Show 3 read-only tools
  • compare_portfoliosTwo to eight separate portfolios on one shared window of prices.No findings

    Why it is in this group

    • The name "compare_portfolios" says "compare": a word for reading.
    Description, as the server wrote it
    Two to eight separate portfolios on one shared window of prices. In: {label: {ticker: weight}}. Out: growth, volatility, worst fall, and how each moved against the others. Typical questions: 'Compare 60/40 with an all-world fund.'; 'Which of these three mixes fell less in 2022?'; 'Put my portfolio next to the S&P 500.'. Instead: for one portfolio before and after a change, test_a_change or check_before_you_buy. It does not recommend, predict or calculate tax.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Compare portfolios side by side
  • search_symbolsFinds tickers from a name, part of a ticker or an ISIN, with the exchange of each listing.No findings

    Why it is in this group

    • The name "search_symbols" says "search": a word for reading.
    Description, as the server wrote it
    Finds tickers from a name, part of a ticker or an ISIN, with the exchange of each listing. In: one search phrase. Out: up to ten listings, those not yet checked marked as such. Typical questions: 'What's the ticker for Vanguard FTSE All-World?'; 'Find IE00BK5BQT80.'; 'Is there a euro listing of the Nasdaq 100 ETF?'. Instead: when the tickers are already written down, validate_symbols. A bare US-style symbol can name a different fund than a European one with the same letters (EQQQ is a US ProShares fund; the Invesco UCITS fund is EQQQ.DE / EQQQ.L): give the exchange suffix. It does not recommend, predict or calculate tax.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Find a ticker by name
  • validate_symbolsChecks tickers before a measurement.No findings

    Why it is in this group

    • The name "validate_symbols" says "validate": a word for reading.
    Description, as the server wrote it
    Checks tickers before a measurement. In: up to 150 tickers. Out: which have usable price history, their trading currency, and the closest listings for those that do not. Typical questions: 'Check these tickers before you measure: VWCE, EQQQ, CSPX.'; 'Are VTI and BND valid?'; 'Which of these symbols can you price?'. Instead: when only a name is known, search_symbols. It measures nothing. It does not recommend, predict or calculate tax.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Check symbols before measuring

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:38 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
19
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 19 tools that change things (19 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://folionomiq.com/mcp: tools/list returned 22 tools to an anonymous client, including measure_portfolio (write), test_a_change (write), portfolio_structure (write), look_through (write), past_crises (write) and 14 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "reverse_stress" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "start": a word for a change.

    What this check looks for

History

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

  1. Tools22 changed.~22 changedView diff

Install

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

claude mcp add --transport http folionomiq https://folionomiq.com/mcp
claude mcp add --transport http folionomiq https://folionomiq.com/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__folionomiq__compare_portfolios",
      "mcp__folionomiq__search_symbols",
      "mcp__folionomiq__validate_symbols"
    ],
    "ask": [
      "mcp__folionomiq__measure_portfolio",
      "mcp__folionomiq__test_a_change",
      "mcp__folionomiq__portfolio_structure",
      "mcp__folionomiq__look_through",
      "mcp__folionomiq__past_crises",
      "mcp__folionomiq__portfolio_report",
      "mcp__folionomiq__factor_exposure",
      "mcp__folionomiq__currency_effect",
      "mcp__folionomiq__health_axes",
      "mcp__folionomiq__sweep_holding",
      "mcp__folionomiq__reverse_stress",
      "mcp__folionomiq__return_history",
      "mcp__folionomiq__plain_findings",
      "mcp__folionomiq__last_price",
      "mcp__folionomiq__asset_info",
      "mcp__folionomiq__monthly_plan",
      "mcp__folionomiq__walk_forward",
      "mcp__folionomiq__check_before_you_buy",
      "mcp__folionomiq__living_off_it"
    ],
    "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 folionomiq. 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/com.folionomiq/folionomiq/verify?hash=111214facf8f2e8c1587d25fda7979f3521f3806fd298588532d9d7e1823324c" | jq -e '.changed == false'

Pinned hash 111214facf8f, from Nov 10, 2026, 09:18 UTC.

Watch

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

https://radar.anlyon.com/servers/com.folionomiq/folionomiq/changes.xml

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

Badge

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

Source: MCP Registry. Synced Nov 10, 2026, 09:17 UTC.

Folionomiq MCP server: questions and answers

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

Is the Folionomiq MCP server safe?

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

Can the Folionomiq MCP server delete data?

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

Can the Folionomiq 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 Folionomiq MCP server have?

22 tools: 19 write, 3 read. measure_portfolio, test_a_change, portfolio_structure, look_through, past_crises, portfolio_report, factor_exposure, currency_effect and 14 more.

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

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

Does the Folionomiq MCP server send data to outside services?

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

Has the Folionomiq MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Oct 24, 2026. Every change is on this page and in its Atom feed.