Fundamentals MCP
PYPI · FUNDAMENTALS-MCP · SCANNED SEP 20
Unofficial read-only MCP for fundamentals, macro & news (EDGAR + FRED + Tavily, BYO-key).
Available components
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
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 1 of 22 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency6
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (Apache Software License) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 83 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 848 tokens (~169/item across 5 items; 5 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 Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
How do I install the Fundamentals MCP server?
Fundamentals MCP runs locally as a PyPI package, launched with uvx fundamentals-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · fundamentals-mcp
claude mcp add simontarara62-fundamentals-mcp -- uvx fundamentals-mcp
{
"mcpServers": {
"simontarara62-fundamentals-mcp": {
"command": "uvx",
"args": [
"fundamentals-mcp"
]
}
}
} {
"servers": {
"simontarara62-fundamentals-mcp": {
"command": "uvx",
"args": [
"fundamentals-mcp"
]
}
}
} codex mcp add simontarara62-fundamentals-mcp -- uvx fundamentals-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"simontarara62-fundamentals-mcp": {
"type": "local",
"command": [
"uvx",
"fundamentals-mcp"
],
"enabled": true
}
}
} openclaw mcp add simontarara62-fundamentals-mcp --command uvx --arg fundamentals-mcp
mcp_servers:
simontarara62-fundamentals-mcp:
command: "uvx"
args: ["fundamentals-mcp"] {
"McpServers": {
"simontarara62-fundamentals-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"fundamentals-mcp"
]
}
}
} assistant mcp add simontarara62-fundamentals-mcp -t stdio -c uvx -a fundamentals-mcp
{
"mcpServers": {
"simontarara62-fundamentals-mcp": {
"command": "uvx",
"args": [
"fundamentals-mcp"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 −3
- Stability: pass → 0.80 functional
- 17 Sept 26 +1
- Stability: 0.97 → pass security
- 15 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 14 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 −3
- Stability: pass → 0.80 functional
- 10 Sept 26 +1
- Stability: 0.97 → pass security
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 20 Sept 2026 · Analysed pypi/fundamentals-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 22 packages
| Packages resolved | 22 |
|---|---|
| Stale | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
get_fundamentals ~378
Fetch US-equity company fundamentals from SEC EDGAR (requires a User-Agent). `ticker` is a US ticker or company name (resolved to a CIK). `metrics` is an optional list of canonical keys; omitted = the full default set (31 metrics). Available metric families (canonical key in parentheses): - Income statement: revenue, cost_of_revenue, gross_profit, research_and_development, sga_expense, operating_income, income_tax_expense, net_income, eps_basic, eps_diluted. - Balance sheet: accounts_receivable, inventory, current_assets, ppe_net, total_assets, accounts_payable, current_liabilities, long_term_debt, total_liabilities, stockholders_equity, retained_earnings, cash_and_equivalents. - Cash flow: operating_cash_flow, investing_cash_flow, financing_cash_flow, capex, stock_based_compensation, dividends_paid. - Shares: shares_outstanding, weighted_avg_shares_basic, weighted_avg_shares_diluted. Returns a provenance-stamped envelope of the latest annual (10-K) values. Report figures only from `facts`, surface each `as_of`/period and source, and if a fact is 'not_available'/'not_configured' say so — do not estimate. Some metrics are sector-dependent (e.g. banks/insurers don't tag `cost_of_revenue` or `gross_profit`); that is the expected `not_available` behavior. Ratios and analyses (P/E, ROE, current ratio, FCF, Altman Z, etc.) are computed by the skill layer, never by the server. Not financial advice.
| Name | Type | Req | Description |
|---|---|---|---|
| metrics | – | – | – |
| ticker | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_macro ~123
Fetch the latest value of a macro/economic time series from FRED (BYO key). `series` is a FRED series id (e.g. 'CPIAUCSL', 'FEDFUNDS', 'DGS10'). Returns a provenance-stamped envelope. Report figures only from `facts`; always surface the `as_of` date and the source. If a fact's status is 'not_available' or 'not_configured', say so explicitly — do not estimate. Not financial advice.
| Name | Type | Req | Description |
|---|---|---|---|
| series | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_news ~211
Fetch citation-bound news snippets for any query (BYO Tavily key). `query` is free-text (a ticker, company name, instrument, topic, headline, etc.). Works for ALL asset classes — equities, indices, commodities, FX, crypto. `lookback_days` (1/≤7/≤31/>31 → day/week/month/year) and `max_results` are optional. Returns a provenance-stamped envelope with `facts=[]` (always) and `context=[NewsItem...]`. **Hard rule: this tool never populates a numeric value.** When summarizing for the user, attribute every claim by item id (e.g. [c1]); do not state any figure from this tool — quote a snippet verbatim if the source mentions a number, and label it as media framing, not as a measurement. Not financial advice.
| Name | Type | Req | Description |
|---|---|---|---|
| lookback_days | integer | – | – |
| max_results | integer | – | – |
| query | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
ping ~17
Liveness check — confirms the server is reachable.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
resolve_instrument ~83
Resolve a US-equity ticker or company name to its SEC CIK. Returns a resolution with `cik`, `canonical` name, `confidence` (high/medium/low/none) and, when ambiguous, `alternatives`. If confidence is low/none, ask the user to confirm rather than assuming a match.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
What is the Fundamentals MCP server?
Fundamentals MCP is listed in the public MCP registry as io.github.SimonTarara62/fundamentals-mcp. Unofficial read-only MCP for fundamentals, macro & news (EDGAR + FRED + Tavily, BYO-key). This page covers its PyPI package (fundamentals-mcp).
Is the Fundamentals MCP server safe to use?
Fundamentals MCP scores 72 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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 Fundamentals MCP server expose?
Fundamentals MCP exposes 5 tools: ping, get_macro, resolve_instrument, get_fundamentals, get_news. Their descriptions and schemas cost roughly 812 tokens of context every time the server is loaded.
Is the Fundamentals MCP server still maintained?
Fundamentals MCP is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.