Financial Datasets
NPM · @PIPEWORX/MCP-FINANCIAL-DATASETS · 2 COMPONENTS
Financial Datasets AI MCP — wraps financialdatasets.ai
Available components
Last scanned (11 hours ago)
Scores higher than 72% 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 & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-financial-datasets). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 753 tokens (~188/item across 4 items; 4 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 Management20
- Stability observed for 6 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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 →
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Stability: unverified → 0.07 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.1 → 0.2.2 functional
- 31 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- Security disclosure: unverified → fail ▼ functional
- 30 Oct 26 64
First indexed and scored.
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/@pipeworx/mcp-financial-datasets@0.2.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-financial-datasets |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-financial-datasets/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3635943098 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:1695b193bd3aa3ed82f972c6b952cfabf0c8015a97082991db4ad7940a6362f2778efc6664db15d11d152877396e7e70a5ba92ea10c905dcbdbdb9015 |
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 →
fd_filings ~181
Recent SEC filings for <ticker> — the company's latest EDGAR filings (10-K, 10-Q, 8-K, 20-F, 6-K). Returns filing type, report period, filing date, and document URL. Optionally filter by filing_type. Example: fd_filings({ ticker: "AAPL", filing_type: "8-K", limit: 20, _apiKey: "your-key" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Financial Datasets API key (from financialdatasets.ai) |
| filing_type | string | – | Optional filter, e.g. "10-K", "10-Q", "8-K", "20-F", "6-K" |
| limit | integer | – | Max filings to return (default 20) |
| ticker | string | yes | Stock ticker symbol, e.g. "AAPL" |
No output schema declared.
No examples provided.
fd_insider_transactions ~153
Insider (Form 4) transactions for <ticker> — recent buys/sells by officers, directors, and 10%+ owners as reported on SEC Form 3/4/5. Returns insider name, title, transaction type, shares, price, date, and board-director flag. Example: fd_insider_transactions({ ticker: "AAPL", limit: 25, _apiKey: "your-key" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Financial Datasets API key (from financialdatasets.ai) |
| limit | integer | – | Max transactions to return (default 25, max 1000) |
| ticker | string | yes | Stock ticker symbol, e.g. "AAPL" |
No output schema declared.
No examples provided.
fd_institutional_holders ~156
Who holds <ticker> (institutional 13F holders) — the institutional investors (funds, asset managers) that report holding a stock in their latest SEC Form 13F. Returns investor name, shares held, market value, and report period. Example: fd_institutional_holders({ ticker: "AAPL", limit: 25, _apiKey: "your-key" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Financial Datasets API key (from financialdatasets.ai) |
| limit | integer | – | Max holders to return (default 25, max 200) |
| ticker | string | yes | Stock ticker symbol, e.g. "AAPL", "NVDA", "TSLA" |
No output schema declared.
No examples provided.
fd_investor_portfolio ~208
What does fund <investor> hold (institutional 13F portfolio) — every long position an institutional filer reported in its latest SEC Form 13F. Identified by the fund's 10-digit zero-padded SEC CIK (e.g. Berkshire Hathaway = 0001067983). Returns ticker, shares, market value, and report period per position. Example: fd_investor_portfolio({ filer_cik: "0001067983", limit: 50, _apiKey: "your-key" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Financial Datasets API key (from financialdatasets.ai) |
| filer_cik | string | yes | The fund's SEC filer CIK, 10-digit zero-padded, e.g. "0001067983" (Berkshire Hathaway). This endpoint requires a CIK, not a fund name. |
| limit | integer | – | Max positions to return (default 50, max 200) |
No output schema declared.
No examples provided.
How do I install the Financial Datasets MCP server?
Financial Datasets runs locally as an npm package, launched with npx -y @pipeworx/mcp-financial-datasets. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-financial-datasets
claude mcp add pipeworx-io-financial-datasets -- npx -y @pipeworx/mcp-financial-datasets
What is the Financial Datasets MCP server?
Financial Datasets is an MCP server listed in the public MCP registry as io.github.pipeworx-io/financial-datasets. Financial Datasets AI MCP, wraps financialdatasets.ai. This page covers its npm package (@pipeworx/mcp-financial-datasets).
Is the Financial Datasets MCP server safe to use?
Financial Datasets scores 82 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. Its build provenance is signed and verified. 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 Financial Datasets MCP server expose?
Financial Datasets exposes 4 tools: fd_institutional_holders, fd_investor_portfolio, fd_insider_transactions, fd_filings. Their descriptions and schemas cost roughly 698 tokens of context every time the server is loaded.
Is the Financial Datasets MCP server still maintained?
Financial Datasets 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 Financial Datasets MCP server under?
Financial Datasets 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 Financial Datasets MCP server?
VerifyMCP ran 16 checks on Financial Datasets, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. 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.