Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Quantic Finance

REMOTE · QUANTIC.FINANCE

Dividend portfolio tracking and planning for US and EU markets: income, safety, Spain-aware taxes.

Available components

0 this week 81 Trust /100

Last scanned (3 hours ago)

Scores higher than 83% of remote servers

Reachable. Last reached 6 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

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 Security74
  • 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
  • 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
Schema Quality & AI Usability65
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 5175 tokens (~215/item across 24 items; 24 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 24 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 24 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

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 →

Changelog

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.

  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Oct 26 0
    • Tool “dividend_changes” rewrote its description, which is the text the model reads security
    • Tool “get_stock” rewrote its description, which is the text the model reads security
  • 15 Oct 26 0
    • Tool “dividend_calendar” rewrote its description, which is the text the model reads security
    • Schema quality: 4447 → 5062 ▼ functional
    • New tool “dividend_changes” functional
    • New tool “earnings_calendar” functional
    • New tool “get_upcoming_dividends” functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 2 Sept 26 0
    • Tool “get_tax_report” rewrote its description, which is the text the model reads security
  • 27 Aug 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 26 Aug 26 0

    First indexed and scored.

Diagnostics

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 6 Nov 2026 · Probed https://quantic.finance/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=quantic.finance CN=YE2,O=Let's Encrypt,C=US 18 Oct 2026 16 Jan 2027 ECDSA 256 ECDSA-SHA384 649b20c2677c1ca334a0948a9fa0f7510ca
SANs: quantic.finance
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 quantic.finance. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
finance. DS published 46861 8 Verified
quantic.finance. 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://quantic.finance/mcp Verified 200
http (plaintext) http://quantic.finance/mcp HTTPS enforced 301 https://quantic.finance/mcp
MCP tools · 24 exposed · ~5,175 tokens

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 →

Tool Tokens
compare_stocks ~84

Compare 2–4 stocks side by side (the /compare view): snapshot, dividend growth, Quantic reads, valuation, momentum, financial health, schedule and community metrics — with the winning column flagged per row (`best`). Pass a list of tickers, e.g. ["KO","PEP","MO"].

NameTypeReqDescription
symbolsarrayyes–

No output schema declared.

No examples provided.

dividend_calendar ~159

Upcoming ex-dividend dates across the dividend universe over the next `days` days (default 45, max 120), soonest first. Public — buy before the ex-date to receive the next dividend. Each row also carries the forward annual dividend rate (`dividend_rate`, in `currency`: the provider's declared rate, or for a steady payer its last payment times payments per year — never the coming payment's own amount), the current yield as a percentage (`dividend_yield`, 2.84 = 2.84%), and the payment date (`pay_date`). Any of them is null when unknown, as the rate is for payers with an uneven interim and final.

NameTypeReqDescription
daysinteger––

No output schema declared.

No examples provided.

dividend_changes ~208

Dividend raises and cuts Quantic saw over the last `days` days (default 7, max 90), newest first. Public. Each row is a change in the forward annual dividend rate: `old_rate` → `new_rate`, in `currency`, with `kind` "raise" or "cut" and `basis` "annual". A semi-annual payer's row has `basis` "payment" instead: its new payment against the same payment a year earlier (interim against interim, final against final), since its two payments a year are rarely the same size. `detected_on` is the day Quantic first saw the new rate: near the declaration when the provider declares it, within a week of the first changed payment's ex-date when it comes from the payments. Never the company's declaration date. The log starts on 2026-10-14; nothing before that is in it.

NameTypeReqDescription
daysinteger––

No output schema declared.

No examples provided.

earnings_calendar ~102

Upcoming earnings reports across the universe over the next `days` days (default 14, max 60), soonest first. Public — the same dates the stock pages show logged out. `estimated` is true when the date is the provider's projection from the previous cycle rather than one the company confirmed; word the two differently. `earnings_date_end` is set when only a window is known.

NameTypeReqDescription
daysinteger––

No output schema declared.

No examples provided.

get_dividends ~186

The signed-in user's received (paid) dividends, newest first. Each row carries the symbol, pay date, shares, per-share and gross amount, withholding tax, net amount and currency. Optionally filter by `symbol` (e.g. "AAPL") and a `from`/`to` date window (ISO-8601, e.g. "2024-01-01"), and/or pass `portfolio` (one of your portfolio names or slugs, case-insensitive — see `list_portfolios`) to narrow to that portfolio; omitted, dividends aggregate across all your portfolios (rows then carry a `portfolio` name when you have more than one). Private to the caller.

NameTypeReqDescription
fromstring––
portfoliostring––
symbolstring––
tostring––

No output schema declared.

No examples provided.

get_holdings ~142

The signed-in user's current holdings: each position's symbol, name, shares held, average cost per share, trading currency and sector. This is cost-basis data from the ledger (no live prices) — use `get_valuation` for current market value, gain/loss and yield. Optionally pass `portfolio` (one of your portfolio names or slugs, case-insensitive — see `list_portfolios`) to narrow to that portfolio; omitted, holdings aggregate across all your portfolios (rows then carry a `portfolio` name when you have more than one). Private to the caller.

NameTypeReqDescription
portfoliostring––

No output schema declared.

No examples provided.

get_income_attribution ~382

Why the signed-in user's dividend income changed: the trailing 12 months against the 12 before them, split into what the companies did, what the user did, what the tax office took and what the exchange rate moved. The four components sum to the headline change by construction, so they can be quoted together without reconciling them yourself. Each is in the user's preferred currency and **net of the withholding their broker recorded**, the same basis `get_income_outlook` reports. `organic` is the part that came from raises alone — income the companies added without the user putting in another cent. That is the number worth leading with: a year where income grew because savings went in is a different achievement from one where it grew because dividends were raised, and only the second compounds on its own. Returns `null` when the ledger doesn't reach back far enough to cover both windows. That is a refusal, not an error: comparing a part-year against a full one shows a collapse that never happened, so say the history is too short rather than reporting a change. Two honesty flags worth relaying when non-zero: * `withholding_newly_reported` — holdings whose earlier window recorded no withholding and whose later one did. Their withholding line reflects the broker starting to report the tax, not the tax changing. * `unresolved_fx` — payments whose historical rate couldn't be resolved. Those fall back to today's rate and so contribute nothing to the currency line, rather than inventing a move. Optionally pass `portfolio` (one of your portfolio names or slugs, case-insensitive — see `list_portfolios`); omitted, it aggregates across all your portfolios. Private to the caller.

NameTypeReqDescription
portfoliostring––

No output schema declared.

No examples provided.

get_income_outlook ~331

The signed-in user's forward dividend income outlook, in their preferred currency: projected annual income at the current rate (gross and net of estimated foreign withholding tax), the income-weighted trailing dividend growth, the current yield, the top income-contributing holdings (gross and net per holding, ranked on the net basis when withholding applies; with each one's growth, 5-year CAGR and consecutive-increase streak), and a year-by-year income projection (gross and net). Also `income_year` — the shape of a typical year: projected income per calendar month, which months sit below the monthly average ("thin") or collect nothing at all, and the share of the year landing in its three biggest months (0.25 would be perfectly even; higher is lumpier). Most companies pay quarterly on one of three cycles, so portfolios drift towards collecting heavily in March/June/September/December, which matters to anyone spending the income rather than reinvesting it. Absent for portfolios too small for the shape to mean anything. Set `years` for the projection horizon (default 10, max 50) and `drip: true` to compound reinvested dividends. Optionally pass `portfolio` (one of your portfolio names or slugs, case-insensitive — see `list_portfolios`) to project just that portfolio; omitted, the outlook aggregates across all your portfolios. Private to the caller.

NameTypeReqDescription
dripboolean––
portfoliostring––
yearsinteger––

No output schema declared.

No examples provided.

get_movements ~187

The signed-in user's trades / cash movements (buys, sells, …), newest first. Each row carries the symbol, date, type, quantity, price, total amount, fee and currency. Optionally filter by `symbol` (e.g. "AAPL") and a `from`/`to` date window (ISO-8601, e.g. "2024-01-01"), and/or pass `portfolio` (one of your portfolio names or slugs, case-insensitive — see `list_portfolios`) to narrow to that portfolio; omitted, movements aggregate across all your portfolios (rows then carry a `portfolio` name when you have more than one). Private to the caller.

NameTypeReqDescription
fromstring––
portfoliostring––
symbolstring––
tostring––

No output schema declared.

No examples provided.

get_options ~205

The signed-in user's options positions — the income "wheel" of sold puts and calls — newest first. Each row carries the symbol, put/call type, strike, expiry, contracts, premium collected, fees, status (open/expired/assigned/ closed), net premium, break-even price, annualized premium yield (ratio) and currency. Optionally filter by `symbol` (e.g. "AAPL") and `status` ("open", "history" for everything resolved, or "all"), and/or pass `portfolio` (one of your portfolio names or slugs, case-insensitive — see `list_portfolios`) to narrow to that portfolio; omitted, positions aggregate across all your portfolios (rows then carry a `portfolio` name when you have more than one). Premium is received income alongside dividends. Private to the caller.

NameTypeReqDescription
portfoliostring––
statusstring––
symbolstring––

No output schema declared.

No examples provided.

get_performance ~381

How the signed-in user's portfolio has actually done — an annualized **money-weighted** return (XIRR) in their preferred currency, including dividends received and any sales, next to what the same money moved on the same days would have made in broad index funds. Money-weighted, not time-weighted: it counts *when* each amount went in, so money invested before a good year earns more of the credit than money added at the end. Every flow is converted at the exchange rate published on its own date, so currency movement is part of the answer — unlike `get_realized`, which deliberately never converts because it measures a position rather than a portfolio. `status` says whether a number was produced: * `"ok"` — `rate_pct` and the comparison are present. * `"insufficient_ledger"` — no holding has any trades behind it, so there is nothing to measure a return on. Ask the user to import their broker's trades. * `"awaiting_rates"` — historical exchange rates for the years the ledger spans are still being fetched; they arrive shortly. **`coverage` matters when reporting this.** Holdings whose shares were typed in by hand have no purchase behind them, so they are excluded from both the flows and the value: the rate describes only the part with trade history, and `coverage.value_pct` says how much of the portfolio that is. Say so rather than presenting the figure as the whole portfolio's. Benchmarks are accumulating funds, whose price already includes reinvested dividends, so both sides are total return. They are priced monthly, so treat the comparison as a direction rather than a decimal. Private to the caller.

NameTypeReqDescription
portfoliostring––

No output schema declared.

No examples provided.

get_portfolio ~178

The signed-in user's complete portfolio snapshot in one call: current holdings (shares + average cost), dividends received, trades (movements) and radar watchlist with target prices. Their own private data, including amounts. Use this for a full overview/backup; for a specific slice (filtered dividends or movements, current market value, income projection) prefer the focused tools (`get_dividends`, `get_movements`, `get_valuation`, `get_income_outlook`). Optionally pass `portfolio` (one of your portfolio names or slugs, case-insensitive — see `list_portfolios`) to narrow to that portfolio; omitted, the snapshot aggregates across all your portfolios (ledger rows then carry a `portfolio` name when you have more than one).

NameTypeReqDescription
portfoliostring––

No output schema declared.

No examples provided.

get_radar ~61

The signed-in user's radar (watchlist): stocks they're tracking to buy or sell, with their target buy/sell prices, notes and currency. Private to the caller. Use `get_stock` to fetch the current price for any of these symbols.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_realized ~212

What the signed-in user's sales actually realized — the positions they've sold out of, and the partial sales of positions they still hold. Each row carries proceeds, the cost basis those proceeds consumed, and the **signed** `result` (negative when sold below the average cost), plus the holding window, trade count and dividends collected while held. Pass `status: "closed"` for only the positions that were fully sold out, or `portfolio` (a portfolio name or slug — see `list_portfolios`) to narrow to one; omitted, it covers every portfolio. Also returns per-currency totals. Results use **average cost** and are never converted between currencies: each figure stays in the currency the shares traded in. This is a measure of how a position performed, not a tax calculation — most European tax rules match each sale to specific purchases (FIFO) instead. Private to the caller.

NameTypeReqDescription
portfoliostring––
statusstring––

No output schema declared.

No examples provided.

get_stock ~159

Look up a stock or ETF by ticker (e.g. "KO", "SCHD"): its dividend profile, live quote, two annual dividends with their yields (`dividend_rates`: `trailing`, paid in the last 12 months, and `forward`, the latest payment times payments a year; `headline` says which of them the quote's `dividend_yield` is), dividend safety, balance-sheet leverage, the momentum & value scores and the snowflake radar — and, for a signed-in caller, the full "Valuation & strategy" read (fair value, two-stage DDM, margin of safety, sector-relative rank, dividend doubling time, max drawdown).

NameTypeReqDescription
symbolstringyes–

No output schema declared.

No examples provided.

get_stock_research ~84

Fetch Quantic's AI-generated research deep-dive for a stock — the narrative brief (overview, dividend history, safety, risks, watch items). Optional `locale` (falls back to English). Returns `found: false` when no article has been generated for the stock yet.

NameTypeReqDescription
localestring––
symbolstringyes–

No output schema declared.

No examples provided.

get_tax_report ~425

A tax year assembled from the signed-in user's own ledger: the dividends received (gross, withheld at source, net — per payment and per source country) and the disposals made (matched first-in first-out, with Spain's two-month rule applied to losses). Foreign currency is converted to euros at the ECB's official daily reference rate for each date — a dividend at its pay date, and a sale's cost and proceeds at their own separate dates, so the currency movement between buying and selling is part of the result. Pass `year` (defaults to the last completed one). Private to the caller. **Beta, and unevenly scoped.** The dividends section works for any tax residence. The disposals section is modelled for **Spain only** so far and returns `supported: false` for anyone else — say so rather than implying the user has no sales. `other_income` is cash that is income but not a dividend — today only payments in lieu of a dividend, paid by the borrower of a lent share instead of the company. It is reported and deliberately **not classified**: no casilla, and it must never be added to the dividend totals or described as dividend income. `other_costs` is what the broker charged the account — today only margin interest. It is **not deductible** in a Spanish declaration, and that is a rule rather than an open question: say so plainly if asked, and never suggest subtracting it from income or folding it into a cost basis. **This is the input to a declaration, not a declaration.** No tax is computed. Every figure carries flags where the data is incomplete — a missing exchange rate, a broker that never reports withholding, a position that sold more shares than its recorded purchases account for. Those flags are the point: relay them, and relay the disclaimer, whenever you relay a number from here.

NameTypeReqDescription
portfoliostring––
yearinteger––

No output schema declared.

No examples provided.

get_upcoming_dividends ~261

The signed-in user's next dividends: each holding, and each stock on their radar, whose ex-dividend date or payment date falls in the next `days` days (default 45, max 120), soonest first. Each item carries `ex_dividend_date` and `pay_date` (either can be null; an ex-date already past with the payment still to come means the dividend is already theirs), `per_share` (this payment per share: the forward annual rate over the payments a year, an estimate until declared) and `currency`. A holding (`held: true`) also carries its `shares` and `expected`, what it should pay gross, and `expected_net`, net of estimated foreign withholding, both in the stock's currency. A radar stock has no amount. Optionally pass `portfolio` (one of your portfolio names or slugs, case-insensitive — see `list_portfolios`) for that portfolio's holdings only, without the radar; omitted, every portfolio and the radar, and each holding says which portfolio it is in when there is more than one. Private to the caller.

NameTypeReqDescription
daysinteger––
portfoliostring––

No output schema declared.

No examples provided.

get_valuation ~185

The signed-in user's portfolio valued at current market prices, in their preferred display currency. Returns the total market value and cost basis (so total − cost is the unrealised gain/loss), the yield on cost and current yield, a sector breakdown, and a per-position list with each holding's market value, cost and forward annual dividend income. Income is reported both gross and net of estimated foreign withholding tax (from the user's tax residence), and the health block includes a per-country geography breakdown. Uses live quotes; positions whose price can't be resolved have null value/income. Optionally pass `portfolio` (one of your portfolio names or slugs, case-insensitive — see `list_portfolios`) to value just that portfolio; omitted, the valuation aggregates across all your portfolios. Private to the caller.

NameTypeReqDescription
portfoliostring––

No output schema declared.

No examples provided.

list_portfolios ~113

The signed-in user's portfolios: each one's name and whether it is the default; publicly shared portfolios also carry their URL `slug`. Pass a name (or slug) as the `portfolio` param of the ledger tools (`get_holdings`, `get_portfolio`, `get_movements`, `get_dividends`, `get_options`, `get_valuation`, `get_income_outlook`) to narrow them to one portfolio; without it they aggregate across all portfolios. Private to the caller.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_stocks ~254

Fetch a curated dividend list by `slug`. Slugs: dividend-aristocrats, dividend-kings, monthly-dividend-stocks, highest-yield-dividend-stocks, safest-reits, dividend-growth-stocks, low-debt-dividend-stocks, large-cap-safe-dividend-stocks, utility-dividend-stocks, healthcare-dividend-stocks, consumer-staples-dividend-stocks, energy-dividend-stocks, european-dividend-stocks, best-dividend-etfs, monthly-dividend-etfs, best-momentum-dividend-stocks, undervalued-dividend-stocks. Returns the list's title, intro and ranked stocks (compact rows — call get_stock for a full read). Set `eu_only` to keep only holdings listed on a European exchange. This matters most on the two fund lists: a US-listed ETF has no key information document under European rules, so a European broker refuses the order — most of the funds in `best-dividend-etfs` are US-listed and unbuyable from Europe. Use it whenever the person asking is investing from Europe.

NameTypeReqDescription
eu_onlyboolean––
slugstringyes–

No output schema declared.

No examples provided.

screen_stocks ~463

Find dividend stocks & ETFs matching criteria — the screener behind quantic.finance. Filter by `sector`, `currency`, yield range (`min_yield`/`max_yield`, on the 5-year average), `min_cagr5y`, `min_streak`, `frequency`, leverage (`max_de`), `min_current` ratio, `min_market_cap`, dividend-`safety` ("safe"/"watch"/"at_risk"), `min_rating` (Quantic's composite 0–10 read on the company), `type` ("equity"/"etf"), or the `aristocrat`/`reit`/`has_ffo`/`exclude_traps` toggles; `sort` by "quality" (the default — the 0–10 rating), "yield", "cagr5y", "streak", "ffo_payout_asc", "momentum" or "value". Returns up to 100 compact rows — call `get_stock` for a full read of any match. Two notes worth passing on to whoever asked. **Sorting by yield alone is how people find yield traps**, which is why quality leads by default. And `exclude_traps` drops what Quantic has already judged at risk while KEEPING stocks it has never assessed — unassessed is not the same as dangerous, so a result set is never quietly narrowed to only what happens to have been scanned.

NameTypeReqDescription
aristocratboolean––
currencystring––
exclude_trapsboolean––
frequencystring––
has_ffoboolean––
max_denumber––
max_yieldnumber––
min_cagr5ynumber––
min_currentnumber––
min_market_capnumber––
min_ratingnumber––
min_streakinteger––
min_yieldnumber––
reitboolean––
safetystring––
sectorstring––
sortstring––
typestring––

No output schema declared.

No examples provided.

screen_wheel ~365

Options worth selling on the wheel, ranked by company quality first and premium second — the same order the `/options/wheel` screen uses. Two lenses via `side`: `"put"` (the default) lists quality dividend payers the caller does **not** hold, where a cash-secured put gets paid to wait for a price they'd accept; `"call"` lists holdings large enough to cover a contract once shares already pledged to open calls are set aside. Rows are **not priced** unless `price: true`. Listing costs nothing; pricing fetches a live option chain per symbol, so it is capped by `limit` (default 5, max 10) and should be asked for only when the caller actually wants numbers. Securities with no listed options come back `chain_status: "no_chain"` — a fact about the security, not a failure, and most European listings land there. Priced put rows carry the period and annualized return, the downside buffer, the effective cost basis if assigned, the yield on cost that basis would give, and the maximum loss. Priced call rows carry the return if called away, the upside forfeited, whether the strike clears the holding's cost basis, and whether a dividend goes ex inside the contract — the usual reason a covered call is exercised early. **This is not investment advice.** Every response carries a `disclaimer`, verbatim rather than paraphrased, and it must be relayed rather than summarized away — as must the maximum loss beside any return quoted. Private to the caller.

NameTypeReqDescription
limitinteger––
portfoliostring––
priceboolean––
sidestring––

No output schema declared.

No examples provided.

search_stocks ~48

Search dividend stocks by ticker or company name (e.g. "coca", "AAPL"). Public — returns up to ~10 matches with their symbols.

NameTypeReqDescription
querystringyes–

No output schema declared.

No examples provided.

Install

How do I install the Quantic Finance MCP server?

Quantic Finance is a hosted endpoint at https://quantic.finance/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 · quantic.finance

# add to Claude Code
claude mcp add --transport http finance-quantic-mcp 'https://quantic.finance/mcp'
Common questions

What is the Quantic Finance MCP server?

Quantic Finance is an MCP server listed in the public MCP registry as finance.quantic/mcp. Dividend portfolio tracking and planning for US and EU markets: income, safety, Spain-aware taxes. This page covers its hosted endpoint (https://quantic.finance/mcp).

Is the Quantic Finance MCP server safe to use?

Quantic Finance scores 81 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 Quantic Finance MCP server expose?

Quantic Finance exposes 24 tools: compare_stocks, dividend_calendar, dividend_changes, earnings_calendar, get_dividends, and 19 more. Their descriptions and schemas cost roughly 5,175 tokens of context every time the server is loaded.

Does the Quantic Finance MCP server require authentication?

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

Is the Quantic Finance MCP server still maintained?

Quantic Finance is still listed as active in the MCP registry. We last reached this channel on 6 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 Quantic Finance MCP server?

VerifyMCP ran 13 checks on Quantic Finance, 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.