TradeAlmanac
NPM · @TRADEALMANAC/MCP-SERVER · 3 COMPONENTS
TradeAlmanac market data: dividends, screener, sentiment indicators, calendar effects, stock lists.
Available components
Last scanned (10 hours ago)
Scores higher than 53% of npm servers
Category Finance and Payments
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 & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 28 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 (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1818 tokens (~121/item across 15 items; 15 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 Management77
- Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 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
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 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 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.
- 21 Oct 26 +4
- Stability: unverified → 0.27 ▲ functional
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 5 Nov 2026 · Analysed npm/@tradealmanac/mcp-server@2026.10.7
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 →
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 →
afgi Fear & Greed Index ~57
The current value of our own Fear & Greed Index of the Russian market, with the scale and the components. A former name: the same as get_indicator with the identifier afgi. It is the platform's estimate, not exchange data.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
afgi_history Fear & Greed Index history ~116
Daily values of the Fear & Greed Index over the chosen period: value, scale zone and date. A former name: the same as get_indicator_history with the identifier afgi. Good for showing how market sentiment moved, but it is the platform's estimate, not an exchange figure.
| Name | Type | Req | Description |
|---|---|---|---|
| date_from | string | – | Start of the period, YYYY-MM-DD. |
| date_to | string | – | End of the period, YYYY-MM-DD. |
| limit | integer | – | How many days to return, 180 by default. |
No output schema declared.
No examples provided.
analysis_by_ticker Write-ups for one security ~76
Published write-ups of the platform for one security: headline, date, address of the piece, conclusions. These are editorial texts, not market data.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many write-ups to return, 20 by default. |
| ticker | string | yes | Ticker of the security, e.g. SBER. |
No output schema declared.
No examples provided.
api_meta What the API serves and what it does not ~86
The API describing itself: which data is available, what the platform does NOT serve (quotes, candles and the Moscow Exchange instrument directory, world market data), rate ceilings and contract versions. Call it when you need to know where the data ends, before promising the user a number.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Language of the answer texts: en or ru. Defaults to the server language. |
No output schema declared.
No examples provided.
dividends_by_ticker Dividends for one security ~114
Dividend history and the next payout for one Moscow Exchange security. Returns declared and forecast payouts with their announcement status, the record date, the amount per share and the yield. The yield is a fraction (0.08 = 8 %), not a percentage. A forecast status means the board of directors has not recommended the payout yet: never present such a value as declared.
| Name | Type | Req | Description |
|---|---|---|---|
| ticker | string | yes | Ticker of the security on the Moscow Exchange, e.g. SBER, LKOH, GAZP. |
No output schema declared.
No examples provided.
dividends_calendar Dividend record-date calendar ~119
Calendar of upcoming dividend record dates across all securities, with announcement statuses. Filtered by a range of record dates. To page through, pass the cursor from the next_cursor field of the previous answer.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Cursor of the next page, from the next_cursor field. |
| date_from | string | – | Lower bound of the record date, YYYY-MM-DD. |
| date_to | string | – | Upper bound of the record date, YYYY-MM-DD. |
| limit | integer | – | How many payouts to return, 50 by default. |
No output schema declared.
No examples provided.
get_almanac_effect Calendar effects ~191
Calendar effects of the Russian market: how the index behaved in January, on Mondays, around Bank of Russia meetings, at quarter end and in the tax period. For each effect: the number of observations, the mean and median return, the share of positive outcomes, the t-statistic and the significance after correction for multiple comparisons. Returns are fractions (0.0125 = 1.25 %). This is statistics of the past, not a forecast: an effect marked nominal or none must not be presented as a regularity.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | Code of one effect from the answer, e.g. month_01. |
| family | string | – | Effect family: month, weekday, cbr, quarter, tax. Omitted — all. |
| subject | string | – | Series: IMOEX (equities) or RGBITR (government bonds). Omitted — both. |
No output schema declared.
No examples provided.
get_indicator Indicator: value and components ~89
The current value of one indicator, its zone, the methodology version and the normalised components with their weights. Components are given as a score on a 0–100 scale; the answer carries no raw input values. A missing component is marked with the status absent — that is absence, not zero.
| Name | Type | Req | Description |
|---|---|---|---|
| spec_id | string | yes | Indicator identifier from list_indicators, e.g. afgi. |
No output schema declared.
No examples provided.
get_indicator_history Indicator history ~130
Daily values of one indicator over the chosen period: date, value, zone, methodology version. Without a key the last year is served, the full history needs a key; when the period was cut, the answer carries depth_limited. Good for showing how the indicator moved, but it is the platform's estimate, not an exchange series.
| Name | Type | Req | Description |
|---|---|---|---|
| date_from | string | – | Start of the period, YYYY-MM-DD. |
| date_to | string | – | End of the period, YYYY-MM-DD. |
| spec_id | string | yes | Indicator identifier from list_indicators, e.g. afgi. |
No output schema declared.
No examples provided.
get_ranking A ranking: places and metrics ~146
The latest snapshot of one ranking: the place of a security, its ticker, sector, the discount to its own history and to its sector in percent, changes in the line-up and the selection rules. The answer carries no price, price change or multiples: the ranking of securities that got cheaper gives the order, not the size of the fall; per-security multiples come from the screener tool. A ranking is built by rules and is not a recommendation.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Language of the names: en, ru or de. Defaults to the server language. |
| ranking_id | string | yes | Ranking identifier from list_rankings, e.g. undervalued_relative. |
No output schema declared.
No examples provided.
list_indicators Platform indicators ~86
All indicators of the platform with the current value, the scale zone and the date: the Fear & Greed Index of the Russian market, the US market sentiment index, the crypto Fear & Greed Index and others. Call it first to learn the identifiers for get_indicator and get_indicator_history. The values are our own calculations on a 0–100 scale, not exchange data.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_rankings Security rankings ~85
The list of ready-made security rankings of the platform, with the date and size of the latest snapshot: undervalued against their own history and their sector, the ones that got cheaper over a period. Call it first to learn the identifier for get_ranking.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Language of the names: en, ru or de. Defaults to the server language. |
No output schema declared.
No examples provided.
screener Screener: securities by fundamentals ~185
Screen securities by fundamentals that are already computed: sector, a ceiling on trailing-twelve-month P/E, a floor on dividend yield. Thresholds are fractions: dividend_yield_min=0.08 means 8 %. An empty answer means no security matched the conditions, not that data is missing.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Cursor of the next page, from the next_cursor field. |
| dividend_yield_min | number | – | Lower bound of dividend yield AS A FRACTION: 0.08 means 8 %. |
| limit | integer | – | How many securities to return, 50 by default. |
| pe_ttm_max | number | – | Upper bound of trailing-twelve-month P/E. |
| sector | string | – | Sector code; the sectors tool lists the codes. |
| sort | string | – | Sort field; the screener_fields tool lists the allowed values. |
No output schema declared.
No examples provided.
screener_fields Screener fields and their units ~46
The list of screener fields with their units and the allowed sort values. Call it before the first screen, so that fractions are not mistaken for percentages and no field name is invented.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
sectors Sectors ~30
Sector codes and names with summary metrics. A code from here goes into the sector parameter of the screener tool.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the TradeAlmanac MCP server?
TradeAlmanac runs locally as an npm package, launched with npx -y @tradealmanac/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @tradealmanac/mcp-server
claude mcp add com-tradealmanac-mcp-server -- npx -y @tradealmanac/mcp-server
What is the TradeAlmanac MCP server?
TradeAlmanac is an MCP server listed in the public MCP registry as com.tradealmanac/mcp-server. TradeAlmanac market data: dividends, screener, sentiment indicators, calendar effects, stock lists. This page covers its npm package (@tradealmanac/mcp-server).
Is the TradeAlmanac MCP server safe to use?
TradeAlmanac scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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 TradeAlmanac MCP server expose?
TradeAlmanac exposes 15 tools: dividends_by_ticker, dividends_calendar, screener, screener_fields, sectors, and 10 more. Their descriptions and schemas cost roughly 1,556 tokens of context every time the server is loaded.
Is the TradeAlmanac MCP server still maintained?
TradeAlmanac is still listed as active in the MCP registry. We last reached this channel on 5 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 TradeAlmanac MCP server under?
TradeAlmanac declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.