Toolstem Financial Data MCP — Curated Signals for AI Agents
Pricing
from $5.00 / 1,000 tool calls
Stock prices, company fundamentals, DCF valuation & peer comparison for AI agents. Agent-ready JSON. Claude & GPT.
Pricing
from $5.00 / 1,000 tool calls
Rating
0.0
(0)
Developer
Toolstem
Actor stats
0
Bookmarked
3
Total users
1
Monthly active users
3 days ago
Last modified
Categories
Share
All notable changes to the Toolstem MCP Server will be documented in this file.
The format is based on Keep a Changelog , and this project adheres to Semantic Versioning .
_lastHttpBody, _lastHttpStatus, _lastScreenDiag are now privateMCP_AUTH_DISABLED semantics — only valid for local-only mode; remote-without-auth now requires explicit I_KNOW_THIS_IS_DANGEROUS=1 plus a periodic warning bannerHTTP mode (--http) now defaults to localhost; remote access requires explicit opt-in and bearer token.
127.0.0.1: HTTP server no longer listens on 0.0.0.0. Set ALLOW_REMOTE=1 to bind all interfaces.ALLOW_REMOTE=1, the server refuses to start unless MCP_AUTH_TOKEN is set (or MCP_AUTH_DISABLED=1 for explicit override)./mcp routes require Authorization: Bearer <token> when auth is enabled. Uses crypto.timingSafeEqual for constant-time comparison./mcp is rate-limited to 150 requests/minute per IP via express-rate-limit./health remains unauthenticated for load-balancer and uptime probes (returns no secrets).express-rate-limit dependency.Credit: Ryan (responsible disclosure).
Tightened semver ranges in package.json so the lowest version satisfying each range is a patched release. No behavior change; resolved versions in package-lock.json are unchanged.
@modelcontextprotocol/sdk: ^1.12.0 → ^1.29.0 (clears GHSA-345p-7cg4-v4c7, GHSA-8r9q-7v3j-jr4g, GHSA-w48q-cv73-mx4w false-positive findings)express: ^4.21.0 → ^4.22.1apify: ^3.3.0 → ^3.7.0zod: ^3.24.0 → ^3.25.76Motivated by the mcp-marketplace.io scanner, which reads package.json ranges worst-case (lowest satisfying version) rather than the resolved version, producing flagged findings even though installed versions are fully patched. npm audit --omit=dev --audit-level=high reports 0 high/critical.
All three tools (get_stock_snapshot, get_company_metrics, compare_companies) now expose the standard MCP annotations block:
readOnlyHint: true — tools never write to external statedestructiveHint: false — tools never mutate or deleteidempotentHint: true — same input yields same output across callsopenWorldHint: true — tools fetch from external upstreams (FMP)title — human-readable display labelMotivated by the Anthropic Connectors Directory submission requirement that every submitted tool include title plus readOnlyHint/destructiveHint. Per past directory-rejection analysis, missing annotations account for roughly 30% of rejections. Purely additive metadata; no behavioral change.
Three-tier per-result pricing model. The Apify Actor now routes each tool call to a distinct PPE event name, enabling the Apify Console to charge different dollar amounts by tool:
| Tool | PPE Event Name | Tier | Price per call |
|---|---|---|---|
get_stock_snapshot | tool-call | Cheap | $0.005 |
get_company_metrics | tool-call-standard | Standard | $0.05 |
compare_companies | tool-call-premium | Premium | $0.50 |
The tool-call-standard and tool-call-premium event names are new. Dollar amounts for these events must be configured in the Apify Console PPE settings before publishing — the code only fires Actor.charge({ eventName }); the platform resolves the charge.
Rationale. The previous flat $0.005/call structure was structurally below market and mis-priced by tool complexity. get_stock_snapshot is a fast, single-company quote synthesis — cheap is appropriate. get_company_metrics fans out to five financial-statement endpoints and computes CAGRs, signal classifications, and health scores — standard tier reflects that effort. compare_companies runs DCF and full ratio analysis across 2–5 companies in parallel — premium pricing reflects the compute intensity and the unique value of pre-ranked, cross-company intelligence. This matches the established Apify ecosystem norm: top revenue-generating actors price per result ($0.40–$1.50 per 1,000 results) rather than flat per call, capturing value proportional to the work performed and output delivered.
No change to default-demo behavior. Runs with no input.tool still skip all PPE charges (probe policy from v1.2.6 is preserved). Both versioned locations in src/index.ts (McpServer constructor, /health endpoint), version fields in package.json and server.json (top-level + packages[0]), and .well-known/mcp/server-card.json are all promoted to 1.2.9.
src/actor.ts — Actor.charge({ eventName: 'tool-call' }) replaced with a PRICING_TIER routing block. Log line now includes the event name for auditability.src/index.ts — version corrected from drifted 1.2.2 to 1.2.9 in both McpServer({ version }) and the /health response.package.json, server.json (both version and packages[0].version) — bumped from 1.2.8 to 1.2.9.README.md — pricing section updated with three-tier table.screen_stocks references. Removed leftover mentions in the Architecture directory-tree and the unused data/universe.ts line that referenced a v1.3 screener refactor. README now describes only what is shipped today..actor/input_schema.json and .actor/actor.json descriptions to front-load "Financial data MCP server for AI agents" and remove references to a tool not currently exposed. Aligns listing copy with the v1.2.6 product surface and matches search-intent keywords on Apify Store.screen_stocks — temporarily disabled section. The roadmap line in the hero already signals continued investment in finance tools; the apologetic mid-README block was suppressing perceived recency.tool field), it now runs get_stock_snapshot('AAPL') as a default demonstration instead of exiting with an error. This addresses a real conversion leak observed in production: directory health-check probes and first-time evaluators frequently invoke actors with empty input to verify reachability, and the previous behavior (silent exit, no output) made the actor look broken or empty in those probes. The new behavior produces a real, useful result so directory listings and exploratory runs see what the actor actually does. MCP gateway invocations are unaffected — they always pass tool explicitly.tool-call PPE charge. Probes don't generate revenue, and we shouldn't bill health-check accounts for runs they didn't intend. Real invocations (input with tool specified) charge as before.await Actor.exit() call at the end of the Actor entrypoint, which is required by the Apify SDK v3 when Actor.init() has been called (init opens a WebSocket that must be explicitly closed). Without this, every run completed its tool work successfully but the container stayed alive until timeout, causing downstream orchestration (including the pre-publish smoke test) to see runs as TIMED-OUT. Regression introduced in commit fb7d35c (2026-04-21); detected by the pre-publish smoke test on 2026-04-24.compare_companies: graceful degradation when FMP's /stable/batch-quote endpoint returns 402 on the free tier. The tool now falls back to per-symbol getQuote calls via the new withBatchFallback helper, so a 2–5 symbol comparison completes with a full response instead of failing the whole call.withBatchFallback helper in src/services/fallback.ts for batch → per-item degradation with bounded concurrency. Reserved for reuse by future tools that depend on batch endpoints (SEC Form 4 batches, 13F batch holdings in the upcoming SEC server).api_calls_made in the compare_companies response now reflects the true network round-trip count in both the batch-succeeded and fallback paths.actor.json declares LIMITED_PERMISSIONS explicitly.server-card.json for MCP registry distribution.screen_stocks tool temporarily disabledv1.2.1 diagnostics confirmed the root cause of screen_stocks returning 0 results: FMP's /stable/batch-quote endpoint now returns HTTP 402 ("Restricted Endpoint") on the free tier. The diagnostic payload showed every batch request rejected with a subscription-required error regardless of chunk size.
Rather than ship a broken tool, v1.2.2 removes screen_stocks from the public surface area:
src/index.ts).src/actor.ts).screen_stocks-specific fields from the Apify input schema (.actor/input_schema.json).get_stock_snapshot, get_company_metrics, compare_companies.The underlying source for the screener (src/tools/screen-stocks.ts, src/services/fmp.ts helpers, and the Russell 1000 universe in src/data/universe.ts) is retained in the repository for the v1.3 refactor, but is no longer reachable from any transport.
screen_stocks will return in v1.3 built on FMP's free-tier-available /api/v3/stock-screener endpoint (server-side filtering, 1 API call instead of 11, supports filters previously stubbed out: industry, beta, dividend, country).
_lastScreenDiag, _lastHttpStatus, _lastHttpBody, per-chunk meta.diagnostics) — retained only within the now-inert screenStocks path in fmp.ts for v1.3 reference./health endpoint and createServer() to report version 1.2.2.Post-publish QA found screen_stocks returns 0 results on the live Apify Actor despite the Russell 1000 universe being present. Apify swallows console.error output under LIMITED_PERMISSIONS, so root cause was unobservable in logs.
v1.2.1 is a diagnostic release that surfaces the failure point directly in the response body:
size, returned, ms) in meta.diagnostics.chunksmeta.diagnostics.last_http_status / last_http_bodyconsole.error to console.log so Apify captures itThis is a temporary diagnostic build — meta.diagnostics will be removed once the batch-quote issue is confirmed and fixed.
screen_stocks now works on FMP's free tierFMP's /company-screener endpoint requires a paid plan (HTTP 402 on free tier), so screen_stocks was silently returning zero results for every free-tier user. v1.2.0 replaces the call with a synthetic screener that works on the free tier:
/batch-quote endpoint and filters in-memory.Information Technology → Technology, Health Care → Healthcare).screen_stocks response: meta.universe surfaces the universe name (russell-1000), description, size (1003), and country (US). Agents can now detect scope and caveat their output appropriately.meta.unsupported_filters lists any filters that were passed but cannot be honored by the free-tier screener. meta.notes explains the limitation in plain language.console.error for visibility in Apify Actor logs.The synthetic screener cannot honor these filters on the free tier (they are accepted and surfaced as unsupported_filters in the response):
industry — iShares data has no GICS sub-industry.beta_min / beta_max — not present in /batch-quote payload.dividend_min — not present in /batch-quote payload.exchange — Russell 1000 is always NYSE/NASDAQ.country — Russell 1000 is always US (non-US country filters return unsupported).To use these filters, upgrade to an FMP Starter plan ($19/mo) and revert to the paid /company-screener endpoint.
apify was added to dependencies but left in optionalDependencies, so npm still treated it as optional and it was stripped from production builds. Removed the optionalDependencies block entirely. Apify Actor runs now start successfully.ERR_MODULE_NOT_FOUND: apify startup failure. (Superseded by 1.1.2 — this release was incomplete.)screen_stocks tool — Screen and filter stocks by sector, market cap, price, beta, volume, dividend yield, exchange, and country. Returns derived cap_category, volatility_category, and liquidity_category signals for every match. All filters optional; configurable limit up to 200.compare_companies tool — Side-by-side comparison of 2–5 companies across price, valuation (P/E, DCF), profitability (margins, ROE, ROIC), financial health, growth, dividends, and ratings. Auto-computed rankings identify leaders in each dimension: lowest_pe, highest_margin, strongest_balance_sheet, best_growth, most_undervalued, highest_rated.getBatchQuote) for efficient multi-symbol price retrieval..actor/input_schema.json updated — symbol is no longer required at the schema level (each tool validates its own inputs).MAJOR.MINOR format per platform requirements.get_stock_snapshot tool — Comprehensive stock overview combining quote, profile, DCF valuation, and rating into one response. Includes derived dcf_signal, market_cap_readable, and 52-week distance metrics.get_company_metrics tool — Deep fundamentals analysis synthesized from 5 financial statement endpoints. Includes margin_trend, health_signal, growth_signal, and pre-computed CAGRs.