Fortunest demo
REMOTE · APP.FORTUNEST.AI
Free demo of Fortunest: a sample multi-broker portfolio your AI can query. No account needed.
Available components
Last scanned (17 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 21 Nov 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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability50
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 5952 tokens (~350/item across 17 items; 17 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage69
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 6% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 17 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 18 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- Tool “allocation” changed its title: Allocation cosmetic
- Tool “chart_values” changed its title: Chart values cosmetic
- Tool “docs_lookup” changed its title: Docs sections cosmetic
- Tool “docs_search” changed its title: Search docs cosmetic
- Tool “events” changed its title: Upcoming events cosmetic
- Tool “get_core” changed its title: Portfolio overview cosmetic
- Tool “get_trade_plan” changed its title: Trade plan cosmetic
- Tool “holding” changed its title: One holding cosmetic
- Tool “holdings” changed its title: Holdings cosmetic
- Tool “money_flow” changed its title: Money flow cosmetic
- Tool “recent_trades” changed its title: Recent trades cosmetic
- Tool “risk” changed its title: Risk summary cosmetic
- Tool “simulation” changed its title: Simulation cosmetic
- Tool “tax_free_summary” changed its title: Tax-free summary cosmetic
- Tool “tax_lots” changed its title: Tax lots cosmetic
- Tool “trade_candidates” changed its title: Trade candidates cosmetic
- Tool “warnings” changed its title: Warnings cosmetic
- 10 Nov 26 67
First indexed and scored.
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 21 Nov 2026 · Probed https://app.fortunest.ai/mcp/demo
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=app.fortunest.ai | CN=YE2,O=Let's Encrypt,C=US | 14 Oct 2026 | 12 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6b13dd8e53884c08934419afa1aa732729e |
| SANs: app.fortunest.ai | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 app.fortunest.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | DS published | 1814 | 8 | Verified |
| fortunest.ai. | No DS | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self'; base-uri 'self'; object-src 'none'; frame-ancestors 'none'; form-action 'self'; img-src 'self' data: blob: https:; font-src 'self' data:; style-src 'self' 'unsafe-inline'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://cloud.umami.is; connect-src 'self' https://cloud.umami.is https://gateway.umami.is; worker-src 'self' blob: |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://app.fortunest.ai/mcp/demo | Verified | 200 | |
| http (plaintext) | http://app.fortunest.ai/mcp/demo | HTTPS enforced | 301 | https://app.fortunest.ai/mcp/demo |
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 →
allocation Allocation ~298
DEMO portfolio (synthetic, shared, read-only). Read ONE dimension of the portfolio's allocation — where the money is, and how far that is from the user's saved targets — instead of the whole context. dimension: assetClass, sector, region, currency, cap, type, account (default assetClass; there is no separate broker dimension — an account label IS its broker). depth (1-30, default 10) keeps the largest segments and groups the rest into `other`; a segment already named 'Other' is the app's own fold of its smallest segments. withTargets (default true) adds targetPct and driftPct in percentage points wherever the user has saved a target, and raises a target nothing matched so a 0% holding against a target is never invisible; targets exist for assetClass and sector only. weightBasis says what weightPct is a percent OF: 'portfolio' for every breakdown dimension, and 'accounts' for dimension=account, where the weights are a percent of the accounts' combined value (totalValue) because an asset held in no account is outside that split. Every value is in the display currency. `pending` names holdings whose market data has not landed — they are in no segment, so the split is not final while it is there. Describes the portfolio; never investment advice.
| Name | Type | Req | Description |
|---|---|---|---|
| depth | integer | – | – |
| dimension | – | – | – |
| withTargets | boolean | – | – |
No output schema declared.
No examples provided.
chart_values Chart values ~228
DEMO portfolio (synthetic, shared, read-only). The Portfolio value chart's lines on up to 6 dates, from the series the chart draws: value, valueDate, change and returnPct since the chart start (from), ranking, highestBenchmark. date: YYYY-MM-DD or "today" (one or a list; omitted = today). lines: "Portfolio Total", an account, type:/sector:/category:<name>, or "inflation" (the inflation hurdle; adds real returns). from: YYYY-MM-DD, or "" for the first transaction. benchmarks: keys or custom benchmark names. In the in-app chat lines, benchmarks and from default to the chart on screen. A benchmark line is the same money flows invested in that benchmark instead: every day the portfolio bought or sold securities, the same amount buys or sells the benchmark at that day's price, and a later chart start opens it with the whole portfolio value bought on that day.
| Name | Type | Req | Description |
|---|---|---|---|
| benchmarks | array | – | – |
| date | – | – | – |
| from | string | – | – |
| lines | array | – | – |
No output schema declared.
No examples provided.
docs_lookup Docs sections ~48
DEMO portfolio (synthetic, shared, read-only). Read one to five exact section labels from the product docs index; missing sections are reported rather than fabricated.
| Name | Type | Req | Description |
|---|---|---|---|
| labels | array | yes | – |
No output schema declared.
No examples provided.
docs_search Search docs ~48
DEMO portfolio (synthetic, shared, read-only). Search the actual product documentation and return bounded matched sections with source links.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
events Upcoming events ~449
DEMO portfolio (synthetic, shared, read-only). Read the portfolio's forward calendar as a dated list instead of the whole context: earnings dates, ex-dividend and dividend-pay days for the holdings the Events card tracks, central-bank rate decisions and scheduled data releases for the portfolio's jurisdictions, and the tax-free lot maturities from the Taxes digest. kinds filters to any of: earnings, dividends, macro, maturities (default all). days is the window ahead (1-365, default 30, today counts as upcoming); symbols filters to those tickers; limit (1-50, default 20) and offset page the list, which is sorted by date and, on a shared date, by position size. byKind counts the whole window BEFORE the kinds filter, so one call shows what else is coming. servedFrom says where the answer came from: 'context' is the assistant's cached list (the nearest 20 events within 45 days), 'engine' means the events calendar itself was asked for the full window. THE EARNINGS CALENDAR: ask with kinds=['earnings'] alone and the answer is one row PER SYMBOL instead of one per date (bySymbol true) — symbol, name, scope, weightPct, nextEarnings (its next reporting day inside the window), lastReport {date, epsActual, epsEstimate, surprisePct, verdict} and filingUrl/filingSearchUrl when a filing is known, sorted soonest first with companies that have no date in the window last. scope picks whose: holdings (default), watchlist (the user's favourites, up to 20) or both. past is days BACK for recent reports (0-180, default 0). scope and past apply to that per-symbol answer only. This is the multi-symbol view market_lookup can only give one symbol at a time. Dates only — never a forecast of what will be reported, and never advice.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
| kinds | array | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
| past | integer | – | – |
| scope | – | – | – |
| symbols | array | – | – |
No output schema declared.
No examples provided.
get_core Portfolio overview ~298
DEMO portfolio (synthetic, shared, read-only). Read the whole portfolio as one small digest (at most 16 000 characters, about 4 000 tokens) instead of the enormous get_context union: asOf, the value/cash/day-change/P-L totals with the per-account split, time-weighted and money-weighted performance, the six risk headlines (max drawdown, current drawdown, volatility p.a., Sharpe, Sortino, worst day), the ten largest holdings by weight with weight, value, day change and total gain, the asset-class and sector allocation with target drift where targets are set, the trade plan's buy/sell/net totals and order counts, the next five calendar events, the data-quality warning counts by kind, the strategy profile, the central-bank policy rates with the risk regime, the user's own trades of the context window (newest first), the subscription tier and its limits, and the user's saved memories and standing notes in full. include ⊆ [memories, notes] LISTS WHICH of the two optional blocks to keep — both when it is omitted, only the ones named when it is given, and neither for include: []. Every amount is in displayCurrency and every field ending in Pct is a percentage. Start here, then call a focused view for the detail; trimmed names any list that had to be shortened to fit.
| Name | Type | Req | Description |
|---|---|---|---|
| include | array | – | – |
No output schema declared.
No examples provided.
get_trade_plan Trade plan ~463
DEMO portfolio (synthetic, shared, read-only). Read the Trade plan card: suggested orders, their company ratings and decision reasons, buy/sell/net/leftover amounts, constraints and sellLotCoverage. Each order's amountEur is the card's Amount, sharePct its Share (percent of that side's budget), rating its Rating (0-100, 50 neutral, null for funds/crypto) and, on sells, taxFreeValueEur/nextMaturity its Tax-free now column; the card's Run historical backtest button opens the historical simulation the backtest_trades tool runs. tradePlanning carries saved controls; planning describes the result. Invest is new money; sales are independent and their proceeds stay cash. Every amount uses displayCurrency; the Eur suffix is legacy. Each '…Eur' field now also ships under its currency-neutral name (amountEur→amount, buyEur→buy, valueEur→value, totalEur→totalAmount); the '…Eur' twins are DEPRECATED and will be removed — read the neutral name. include:['candidates'] adds ranked candidates with inclusion, exclusion or cap reasons; ['taxOrientation'] adds tax lots. Funds/crypto have no company rating. No orders are placed. Default notes are brief; docs carries docs_lookup labels for the simplified planner, verbose:true includes full notes. unavailableReason explains a missing plan. symbols {buys, sells} lists the plan's tickers, ready to pass as `symbols` to holding, market_lookup, price_on or trade_candidates in ONE call. Each sell order carries taxFreeValueEur/taxFreeQty (the whole position's tax-free capacity today) beside taxFreeEur (the exempt slice of that one order), and nextMaturity {date, qty, valueEur} — the earliest still-future time-test date for that holding, what to report when taxFreeValueEur is 0 ('nothing is tax-free today; the next lot matures on …'); null where no open lot has a maturity date at all. The same orders and contextRevision are in get_context portfolio.tradePlan.
| Name | Type | Req | Description |
|---|---|---|---|
| include | array | – | – |
| verbose | boolean | – | – |
No output schema declared.
No examples provided.
holding One holding ~481
DEMO portfolio (synthetic, shared, read-only). Read ONE position in depth — the asset drawer, as data. Give symbol, or symbols for SEVERAL positions in one call (up to 25; the two are mutually exclusive and one of them is required). A batch answers {batch: true, symbols, results keyed by ticker, missing, truncated} — never call this once per ticker when you already know the list. The symbol may be held or merely on the watchlist. include picks the blocks: fundamentals (valuation, growth, fair value, analyst view), lots (open and tax-free quantity, next maturity), news (the cached recent headlines), insider (the 3-month Form 4 digest), events (its upcoming earnings/dividend dates), correlations (which holdings it moves with), warnings (the data-quality sentences naming it) and priceHistory, whose window is the separate range argument (1m, 3m, 6m, 1y, ytd, max — default 3m) and which comes back downsampled to at most 120 points, and description (the drawer's two-sentence profile of what the company does, where it is headquartered and where it operates, with its provenance: yahoo for the market-data feed, ai when a fast AI model wrote it — the app's own, or this user's own provider — facts when the app composed it from the listing's own data), and checks (strengths & things to watch, as sourced facts). With no include the position line alone comes back. A position under 0.1% of the portfolio answers grouped=true: held, with its position line (value, weight) when the summary has it, and no lot data. Blocks that did not fit the result budget are listed in dropped (ask for them singly), and an unknown symbol answers ok=false with the closest symbols the user actually holds or watches, never an invented position.
| Name | Type | Req | Description |
|---|---|---|---|
| include | array | – | – |
| range | – | – | – |
| symbol | string | – | – |
| symbols | array | – | Several tickers in ONE call — up to 25. Send this instead of calling once per ticker; `symbol` and `symbols` are mutually exclusive. The answer is keyed by symbol under `results`, with `missing` nami… |
No output schema declared.
No examples provided.
holdings Holdings ~379
DEMO portfolio (synthetic, shared, read-only). Read the holdings table — the positions themselves — instead of the whole context. sort: weight (default), value, dayChange (today's money move), dayChangePct (today's move in percent), gainPct, gainAbs, loss (biggest losses first), name, symbol; order desc|asc overrides the sensible default for the key. limit is 1-50 (default 10) with offset/nextOffset paging. filter narrows by account label, assetClass (Equities, Bonds, Gold & commodities, Real estate, Crypto, Cash, Other), category, sector, region, currency, an explicit symbols list and minWeight (a PERCENT, so 5 means 5%). fields picks the row width: core (symbol, name, weightPct, value, dayChangePct, dayChangeAbs, totalGainPct, totalGainAbs, quantity, assetClass, sector, category, accounts), fundamentals (adds valuation, growth, fair value, analyst view), lots (adds open quantity, tax-free quantity and the next maturity) or all. Every field ending in Pct is a PERCENT (4.32 = 4.32%). total counts the filtered list, not the page. Positions under 0.1% of the portfolio have no row: smallHoldingsGrouped gives their count, value and combined weight; a filter by symbols, assetClass, category or sector also names the matching ones, with their category, under notListed — held, but without a row. 'Top 5 holdings' is one call: sort=weight, limit=5.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | – | – | – |
| filter | object | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
| order | – | – | – |
| sort | – | – | – |
No output schema declared.
No examples provided.
money_flow Money flow ~301
DEMO portfolio (synthetic, shared, read-only). Read the Trades tab's Money flow card: the cash spent on purchases and raised by sales per week, month or year, from the same rows as the Recent trades card. period is 'week' (ISO weeks, Monday start), 'month' (calendar months, the default) or 'year' (calendar years, the current one to date); count is how many periods back, up to and including the current one (1-260; default 26 weeks, 24 months or 10 years, the card's own). Each item is one period, newest first: start (the period's first day), purchases (the card's Purchases bar) and sales (its Sales bar) — the display-currency cash at each trade's own date, fees included where the broker reports them — net = sales − purchases (the Net line: positive when the period sold more than it bought), buys, sells and trades (execution counts) and unpriced (trades with no derivable amount: counted, never summed). A period without trades is zeros, not a gap. totals sums the whole window; limit/offset page the periods (nextOffset). Transfers, corrections, staking credits, in-kind fees and corporate actions are not trades and never counted.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
| period | – | – | – |
No output schema declared.
No examples provided.
recent_trades Recent trades ~572
DEMO portfolio (synthetic, shared, read-only). Read the user's OWN executed buys and sells — trade history, never recommendations; the rows of the Trades tab's Recent trades card. since is a number of days back (1-3650, default 90); symbol and side (buy or sell) filter; limit is 1-100 (default 20) with offset/nextOffset, newest first. Each item carries date, side, symbol, name, qty, the account it was filed from and amountEur — the trade's cash value in the display currency at its own trade date, fees included where the broker reports them; a row with no derivable display-currency amount carries nativeAmount plus nativeCurrency (price×qty in the trade's own currency) instead. Transfers between the user's own accounts, ledger corrections, staking credits, in-kind fees and corporate actions are not trades and are never listed — the same rows as the Trades tab's Recent trades card. servedFrom says whether the rows came from the chat context's own trade window ('context') or from the full history ('engine'), and window says which stretch was actually read. detail=true reads the card's own table instead (servedFrom 'engine') and adds its other columns to every row: price (the execution price, in priceCurrency, the trade's own currency), fee (the broker-reported fee in the display currency, only when there was one) and changePct (the Since trade column: how the asset's price moved from this execution to today in its own listing currency, split-adjusted, as a FRACTION — 0.25 = +25%; on a sale, what the sold units did since; absent without a current price), plus cardTotal, the count of every trade the card lists (its 'N of M'). The card's sort and filters imply detail: sort (a column; change = Since trade) with order, query (name/ticker terms), type (asset type, e.g. 'ETF funds') and from/to (ISO days; either replaces since). Each '…Eur' field now also ships under its currency-neutral name (amountEur→amount, buyEur→buy, valueEur→value, totalEur→totalAmount); the '…Eur' twi…
| Name | Type | Req | Description |
|---|---|---|---|
| detail | boolean | – | – |
| from | string | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
| order | – | – | – |
| query | string | – | – |
| side | – | – | – |
| since | integer | – | – |
| sort | – | – | – |
| symbol | string | – | – |
| to | string | – | – |
| type | string | – | – |
No output schema declared.
No examples provided.
risk Risk summary ~373
DEMO portfolio (synthetic, shared, read-only). Read the portfolio's risk picture in selectable pieces instead of the whole context. include (default ['metrics']) ⊆ metrics, drawdown, correlations, diversification, benchmarks, fxAttribution, fingerprint. metrics = volatility, Sharpe, Sortino, max and current drawdown, best and worst day, plus the note on what the per-holding risk figures mean. drawdown = the max drawdown's peak, trough, recovery and length, and the current one. correlations = the strongest pairs, strongest absolute correlation first, with the effective number of independent bets. diversification = the 0-100 score, its grade, the sub-scores and the card's own takeaways. benchmarks = one row per selected benchmark with its own return and the portfolio's beta and correlation to it. fxAttribution = how much of the return came from the currencies rather than from the assets. fingerprint = the Portfolio Fingerprint card: six axes (value, growth, past, health, income, diversification) scored 0-6 by fixed pass/fail checks, each with its measured value, threshold and coverage, plus the card's one-line verdict. range (all | 1y, default all) applies to the ratio metrics only — 1y gives the trailing-year volatility, Sharpe and Sortino plus the rolling 12-month envelope, while drawdowns, correlations and diversification are always whole-history. UNITS: volatility, maxDrawdown, currentDrawdown, correlation and the daily returns bestDay.ret and worstDay.ret are FRACTIONS (0.18 = 18%); a field ending in Pct is a percent. Statistics of the user's own history; never investment advice.
| Name | Type | Req | Description |
|---|---|---|---|
| include | array | – | – |
| range | – | – | – |
No output schema declared.
No examples provided.
simulation Simulation ~404
DEMO portfolio (synthetic, shared, read-only). Read what the app knows about the user's SIMULATIONS — the Simulator tab's future projection, the goal seek, the what-if and the historical trade replay — without running any of them. It never starts a simulation and never starts a job. include (default ['summary']) ⊆ summary, whatif, dcaGoal, backtest. IMPORTANT: the future projection, the DCA goal and the what-if are computed on demand in the app and stored NOWHERE on the server — the only copy of what the user ran is the live-UI line 'last simulation — …' in the current turn's context; each block says resultsStoredOnServer: false and serves the INPUTS instead, so an absent result is never read as a zero. summary = what the portfolio is worth now plus the actual return, volatility and strategy horizon a projected line has to be judged against (whole-history figures; the simulator averages over its own lookback window). whatif = the `before` side a what-if is measured from (value, cash, diversification, portfolio fundamentals) and the verb that computes the `after`. dcaGoal = the goal seek's inputs, including the saved Trades-tab budget, which is NOT a recurring contribution. backtest = the historical trade replay, which IS kept server-side for an hour from when it was STARTED (the prune clock runs from the job's creation, not from its completion): state, progress and, once complete, its summary, window, coverage gaps and warnings; backtestId picks one, the default is the newest, and the per-day series, trades, decisions and assumptions are get_workload's answer, not this one's. Amounts are in the display currency; a field ending in Pct is a percent. Describes the user's own simulations; never investment advice.
| Name | Type | Req | Description |
|---|---|---|---|
| backtestId | string | – | – |
| include | array | – | – |
No output schema declared.
No examples provided.
tax_free_summary Tax-free summary ~51
DEMO portfolio (synthetic, shared, read-only). Read actual tax-lot summary and optionally one symbol. Illustrative orientation only; do not estimate missing tax figures.
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | – | – |
No output schema declared.
No examples provided.
tax_lots Tax lots ~446
DEMO portfolio (synthetic, shared, read-only). Read one slice of the illustrative tax-lot orientation (the Taxes tab) instead of the whole context. view is required: 'maturities' = the open lots whose time test is coming up, soonest first (date; daysToExempt = days left until that date, the Taxes tab's 'N days to go'; symbol, qty, valueEur); 'openLots' = the per-asset lot lines, largest position first (openQty, taxFreeQty, taxFreeValueEur, nextMaturity, warnings); 'annual' = the realized-gains table per year, newest year first (proceedsEur = gross, feesEur = broker fees deducted, timeExemptGainEur, capTaxableGainEur = the part of time-test gains the exempt-proceeds cap taxed, netTaxableGainEur, estimatedTaxEur); 'ytd' = this year's proceeds against the limit, the exempt-proceeds cap (exemptGainsCap: time-test-exempt proceeds, scope 'crypto' from 2026), what is already sellable tax-free and the next maturity. symbol (one ticker) or symbols (several, in one call) filter maturities and openLots; year filters annual; limit is 1-50 (default 10) with offset/nextOffset. Every answer carries activeRules. Approximate orientation only — not tax advice and never input for a tax report. Each '…Eur' field now also ships under its currency-neutral name (amountEur→amount, buyEur→buy, valueEur→value, totalEur→totalAmount); the '…Eur' twins are DEPRECATED and will be removed — read the neutral name.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| offset | integer | – | – |
| symbol | string | – | – |
| symbols | array | – | Narrow to SEVERAL tickers in one call — the batch form of symbol, up to 25. The two are mutually exclusive. |
| view | – | yes | – |
| year | integer | – | – |
No output schema declared.
No examples provided.
trade_candidates Trade candidates ~779
DEMO portfolio (synthetic, shared, read-only). Read buy or sell candidates. side is required (buy or sell). Each row carries one company rating (0-100, 50 neutral), its reasons, the plan decision (included/excluded/capped with reasons and amount), input coverage, and ownedEur (null when not held). A candidate the lot engine has lots for (every sell candidate, and a buy candidate that is already held) also carries taxFreeValueEur and taxFreeQty — how much of the position has already passed the holding-period test, in the display currency and in units — and nextMaturity {date, qty, valueEur}, the earliest still-future time-test date for that holding: with taxFreeValueEur 0 it is what to say instead of 'nothing', and it is absent where no open lot has a maturity date (no time test applies). All three are absent where there are no tracked lots. Funds/crypto have rating null. Legacy score is action strength, not the company rating. criteriaWeights gives the saved weights; buyCandidateSource names the buy list — side=buy holds exactly that universe (owned, starred, or both, per Settings > Trades), so a symbol outside it is not scored and has no row; side=sell is always the holdings. symbol (one ticker), symbols (SEVERAL tickers in one call — never ask once per ticker), driver and owned narrow the list. fields attaches extra fundamentals to EVERY row under fundamentals — forwardPE, peg, marketCap, fcfYield, analystUpside, fairValue and the rest — so 'forward P/E and PEG for the recommended buys' is ONE call, not one per candidate. limit is 1-25 (default 10) with offset/nextOffset. why=true is the answer to 'why is WDC scored 72': every item then also carries why, the per-criterion breakdown the Trades tab's score expander shows — criterion, label, raw (in unit), weight, the 0-100 score, contribution (its points: the contributions add up to the rating) and one sentence from the engine, plus stage — the earnings stage that splits Quality and Valuation between their profit r…
| Name | Type | Req | Description |
|---|---|---|---|
| driver | – | – | – |
| fields | array | – | Extra fundamentals to attach to EVERY candidate in the answer, under `fundamentals`: name, sector, industry, price, marketCap, forwardPE, trailingPE, peg, fcfYield, earningsGrowth, revenueGrowth, ret… |
| limit | integer | – | – |
| offset | integer | – | – |
| owned | boolean | – | – |
| side | – | yes | – |
| symbol | string | – | – |
| symbols | array | – | Narrow to SEVERAL tickers in one call — the batch form of symbol, up to 25. The two are mutually exclusive. |
| why | boolean | – | – |
No output schema declared.
No examples provided.
warnings Warnings ~194
DEMO portfolio (synthetic, shared, read-only). Read the portfolio's data-quality warnings — what the import could not read, what it assumed, and what could not be priced — instead of the whole context. Each item carries the engine's own sentence verbatim plus its kind, the `account` that raised it and the symbols it names. kind filters to one of: parse, unpriced, fx, delisted, openingCash, shortCredit, openingBalance, writeOff, skippedRows, exportWindow, missingHistory, other. symbol filters to the warnings naming that holding. byKind counts the FULL list, not the filtered page, so one call shows what else exists. Paginate with limit/offset and nextOffset. These are import and valuation caveats, never investment advice.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | – | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
| symbol | string | – | – |
No output schema declared.
No examples provided.
How do I install the Fortunest demo MCP server?
Fortunest demo is a hosted endpoint at https://app.fortunest.ai/mcp/demo, 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 · app.fortunest.ai
claude mcp add --transport http ai-fortunest-portfolio-demo 'https://app.fortunest.ai/mcp/demo'
What is the Fortunest demo MCP server?
Fortunest demo is an MCP server listed in the public MCP registry as ai.fortunest/portfolio-demo. Free demo of Fortunest: a sample multi-broker portfolio your AI can query. No account needed. This page covers its hosted endpoint (https://app.fortunest.ai/mcp/demo).
Is the Fortunest demo MCP server safe to use?
Fortunest demo scores 72 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 Fortunest demo MCP server expose?
Fortunest demo exposes 17 tools: get_core, holdings, holding, allocation, risk, and 12 more. Their descriptions and schemas cost roughly 5,812 tokens of context every time the server is loaded.
Does the Fortunest demo MCP server require authentication?
No. We connected to Fortunest demo without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Fortunest demo MCP server still maintained?
Fortunest demo is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Fortunest demo MCP server?
VerifyMCP ran 13 checks on Fortunest demo, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.