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.

Fundamental Analysis

NPM · FUNDAMENTAL-ANALYSIS-MCP

Read-only fundamental analysis: P/E, DCF, Graham, Altman Z, Piotroski and margins, with formulas

0 this week 66 Trust /100

Last scanned (14 hours ago)

Scores higher than 38% of npm servers

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
Schema Quality & AI Usability59
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1779 tokens (~177/item across 10 items; 10 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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

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.

  • 5 Nov 26 66

    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 21 Nov 2026 · Analysed npm/fundamental-analysis-mcp@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 10 exposed · ~1,741 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
altman_z_score ~166

Bankruptcy risk score. The original model (1968) is for US public manufacturers; the Z'' model is for non-manufacturers, private and non-US companies.

NameTypeReqDescription
bookEquitynumber–Book value of equity (double_prime model)
ebitnumberyesEarnings before interest and taxes
marketValueEquitynumber–Market value of equity (original model)
modelstringyesoriginal (public manufacturers) or double_prime (everyone else)
retainedEarningsnumberyesRetained earnings
salesnumber–Revenue (original model)
totalAssetsnumberyesTotal assets
totalLiabilitiesnumberyesTotal liabilities
workingCapitalnumberyesCurrent assets minus current liabilities

No output schema declared.

No examples provided.

analyze_company ~613

Every ratio the figures allow, in one call: valuation, profitability, liquidity, solvency, efficiency, risk (Altman Z, Z'', Piotroski) and quality. Every figure is optional; a metric whose figures are missing comes back null and is named. With withInsights, each metric also gets a status and a one-line reading.

NameTypeReqDescription
analystTargetPricenumber–Analyst target price
annualDividendPerSharenumber–Dividends per share over one year
bookValuePerSharenumber–Book value per share
cashAndEquivalentsnumber–Cash and equivalents
costOfRevenuenumber–Cost of revenue, as a positive number
currentAssetsnumber–Current assets
currentLiabilitiesnumber–Current liabilities
ebitnumber–Earnings before interest and taxes
ebitdanumber–EBITDA
epsnumber–Earnings per share, trailing twelve months or last fiscal year
expectedEarningsGrowthRatenumber–Expected yearly EPS growth as a decimal, e.g. 0.15 (PEG)
freeCashFlownumber–Operating cash flow minus capital expenditure
grossProfitnumber–Gross profit, used when cost of revenue is not given
interestExpensenumber–Interest expense, as a positive number
inventorynumber–Inventory
longTermDebtnumber–Long-term debt
marketCapnumber–Market capitalisation (price x shares outstanding)
netIncomenumber–Net income
operatingCashFlownumber–Cash flow from operations
operatingIncomenumber–Operating income
pricenumber–Share price
retainedEarningsnumber–Retained earnings
returnsnumber–Return for the period as a decimal (Sharpe)
revenuePerSharenumber–Revenue per share
riskFreenumber–Risk-free rate for the same period as a decimal (Sharpe)
sharesOutstandingnumber–Shares outstanding
stdDevnumber–Standard deviation of returns for the same period (Sharpe)
taxRatenumber–Effective tax rate as a decimal, e.g. 0.25 (ROIC)
totalAssetsnumber–Total assets
totalDebtnumber–Short-term plus long-term borrowings
totalEquitynumber–Shareholders' equity
totalLiabilitiesnumber–Total liabilities
totalRevenuenumber–Revenue for the period
tradeReceivablesnumber–Trade receivables
withInsightsboolean–Optional: add a status (Good, Neutral, Bad, N/A) and a one-line reading to each metric
workingCapitalnumber–Current assets minus current liabilities; worked out from them when left out

No output schema declared.

No examples provided.

dcf_valuation ~163

Present value of projected free cash flows plus a Gordon-growth terminal value. Optionally converts enterprise value to an implied share price.

NameTypeReqDescription
cashnumber–Optional: cash and equivalents, for the implied share price
discountRatenumberyesDiscount rate or WACC as a decimal, e.g. 0.09 for 9%
projectedFCFarrayyesProjected free cash flow for years 1 to N
sharesOutstandingnumber–Optional: shares outstanding, for the implied share price
terminalGrowthRatenumberyesPerpetual growth after year N as a decimal, e.g. 0.025
totalDebtnumber–Optional: total debt, for the implied share price

No output schema declared.

No examples provided.

graham_number ~66

Benjamin Graham's ceiling price for a defensive investor, from EPS and book value per share.

NameTypeReqDescription
bookValuePerSharenumberyesBook value per share
epsnumberyesEarnings per share
pricenumber–Optional: current share price, to compare

No output schema declared.

No examples provided.

leverage_ratio ~112

How much debt a company carries against its equity, or how many times its operating profit covers its interest.

NameTypeReqDescription
ebitnumber–EBIT, operating income (interest_coverage)
interestExpensenumber–Interest expense, positive or negative as your data reports it (interest_coverage)
kindstringyesWhich ratio
totalDebtnumber–Total debt (debt_to_equity)
totalEquitynumber–Shareholders' equity (debt_to_equity)

No output schema declared.

No examples provided.

liquidity_ratio ~74

Whether short-term assets cover short-term liabilities: the current ratio, or the quick ratio that leaves out inventory.

NameTypeReqDescription
currentAssetsnumberyesCurrent assets
currentLiabilitiesnumberyesCurrent liabilities
inventorynumber–Inventory (quick)
kindstringyescurrent or quick (acid test)

No output schema declared.

No examples provided.

pe_ratio ~52

Price to earnings ratio from a share price and earnings per share.

NameTypeReqDescription
epsnumberyesEarnings per share, same period basis as you intend (trailing or forward)
pricenumberyesShare price

No output schema declared.

No examples provided.

piotroski_f_score ~341

Nine pass or fail accounting signals (profitability, leverage and liquidity, efficiency) added into a 0 to 9 score. Signals that compare two years are scored only when both years are given.

NameTypeReqDescription
assetTurnoverValuenumber–Optional: revenue / total assets, current year (F9)
currentRatioValuenumber–Optional: current ratio, current year (F6)
grossMarginValuenumber–Optional: gross margin as a decimal, current year (F8)
longTermDebtnumber–Optional: long-term debt, current year (F5)
netIncomenumberyesNet income, current year
operatingCashFlownumberyesCash flow from operations, current year
priorAssetTurnoverValuenumber–Optional: revenue / total assets, prior year (F9)
priorCurrentRatioValuenumber–Optional: current ratio, prior year (F6)
priorGrossMarginValuenumber–Optional: gross margin as a decimal, prior year (F8)
priorLongTermDebtnumber–Optional: long-term debt, prior year (F5)
priorNetIncomenumber–Optional: net income, prior year (F3)
priorSharesOutstandingnumber–Optional: shares outstanding, prior year (F7)
priorTotalAssetsnumber–Optional: total assets, prior year (F3, F5)
sharesOutstandingnumber–Optional: shares outstanding, current year (F7)
totalAssetsnumberyesTotal assets, current year

No output schema declared.

No examples provided.

profit_margin ~101

One margin as a share of revenue: gross, operating, net or free cash flow.

NameTypeReqDescription
costOfRevenuenumber–Cost of revenue (gross)
freeCashFlownumber–Free cash flow (free_cash_flow)
kindstringyesWhich margin
netIncomenumber–Net income (net)
operatingIncomenumber–Operating income (operating)
revenuenumberyesRevenue for the period

No output schema declared.

No examples provided.

return_on_equity ~53

Net income as a share of shareholders' equity.

NameTypeReqDescription
equitynumberyesShareholders' equity (average of the period if you have it)
netIncomenumberyesNet income for the period

No output schema declared.

No examples provided.

Install

How do I install the Fundamental Analysis MCP server?

Fundamental Analysis runs locally as an npm package, launched with npx -y fundamental-analysis-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · fundamental-analysis-mcp

# add to Claude Code
claude mcp add boffincoders-fundamental-analysis-mcp -- npx -y fundamental-analysis-mcp
Common questions

What is the Fundamental Analysis MCP server?

Fundamental Analysis is an MCP server listed in the public MCP registry as io.github.boffincoders/fundamental-analysis-mcp. Read-only fundamental analysis: P/E, DCF, Graham, Altman Z, Piotroski and margins, with formulas. This page covers its npm package (fundamental-analysis-mcp).

Is the Fundamental Analysis MCP server safe to use?

Fundamental Analysis scores 66 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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 Fundamental Analysis MCP server expose?

Fundamental Analysis exposes 10 tools: pe_ratio, dcf_valuation, graham_number, altman_z_score, return_on_equity, and 5 more. Their descriptions and schemas cost roughly 1,741 tokens of context every time the server is loaded.

Is the Fundamental Analysis MCP server still maintained?

Fundamental Analysis 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 licence is the Fundamental Analysis MCP server under?

Fundamental Analysis declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the Fundamental Analysis MCP server?

VerifyMCP ran 15 checks on Fundamental Analysis, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Fundamental Analysis: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.