Marketdata App
NPM · @PIPEWORX/MCP-MARKETDATA-APP · 2 COMPONENTS
Market Data App MCP — wraps the Market Data App API (marketdata.app)
Available components
Last scanned (8 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-marketdata-app). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability62
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 973 tokens (~243/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 Management23
- Stability observed for 7 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 (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- 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.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 3 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.2.0 → 0.2.1 functional
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 79
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-marketdata-app@0.2.1
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-marketdata-app |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-marketdata-app/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3649823531 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:f544fa84e8286fb15eb8d6d1bc94c43e687336b418c3d096e5845f1dbe983210a4028365d5635a947027c8b1375cff88663c7f2cae417706dbc0de94d |
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 →
marketdata_candles ~257
Get historical OHLCV candles for a stock symbol at a given resolution ("D" daily, "H" hourly, "5" for 5-minute, etc.). Provide a from/to date range. Example: marketdata_candles({ resolution: "D", symbol: "AAPL", from: "2026-01-01", to: "2026-06-30", _apiKey: "your-key" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Market Data App API token. Get one at https://www.marketdata.app/pricing/ |
| countback | number | – | Return this many candles counting back from `to` (mutually exclusive with `from`). Optional. |
| from | string | – | Start date (YYYY-MM-DD), inclusive. Optional. |
| resolution | string | – | Candle resolution: "D" (daily), "W" (weekly), "M" (monthly), "H" (hourly), or a minute count like "1", "5", "15". Defaults to "D". |
| symbol | string | yes | Stock ticker symbol, e.g. "AAPL". |
| to | string | – | End date (YYYY-MM-DD), inclusive. Optional. |
No output schema declared.
No examples provided.
marketdata_option_chain ~349
Get the full option chain for an underlying stock/ETF/index, with strike, bid/ask/mid/last, volume, open interest, IV and greeks (delta/gamma/theta/vega). Filter by expiration, days-to-expiration, delta, side, and liquidity. Example: marketdata_option_chain({ underlyingSymbol: "AAPL", expiration: "2026-01-16", side: "call", minOpenInterest: 100, _apiKey: "your-key" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Market Data App API token. Get one at https://www.marketdata.app/pricing/ (auth docs: https://www.marketdata.app/docs/api/authentication) |
| date | string | – | Historical snapshot date (YYYY-MM-DD) for a past chain. Optional (defaults to live). |
| delta | string | – | Delta-based strike selection, e.g. "0.30" or a range ".20-.40". Optional. |
| dte | number | – | Filter to contracts with this many days to expiration (nearest match). Optional. |
| expiration | string | – | Filter to a specific expiration date (YYYY-MM-DD) or "all" for every expiration. Optional. |
| minOpenInterest | number | – | Only return contracts with at least this open interest. Optional. |
| side | string | – | Contract side: "call" or "put". Optional (returns both if omitted). |
| strikeLimit | number | – | Limit the number of strikes returned (nearest to the money). Optional. |
| underlyingSymbol | string | yes | Underlying ticker symbol, e.g. "AAPL", "SPY", "TSLA" |
No output schema declared.
No examples provided.
marketdata_option_quote ~183
Get a live/delayed quote plus greeks for a single option contract, identified by its OCC option symbol. Returns bid/ask/mid/last, volume, open interest, IV, delta/gamma/theta/vega, and intrinsic/extrinsic value. Example: marketdata_option_quote({ optionSymbol: "AAPL260116C00150000", _apiKey: "your-key" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Market Data App API token. Get one at https://www.marketdata.app/pricing/ |
| date | string | – | Historical end-of-day quote for a specific trading day (YYYY-MM-DD). Optional. |
| optionSymbol | string | yes | OCC-formatted option symbol, e.g. "AAPL260116C00150000" (AAPL 2026-01-16 $150 call). |
No output schema declared.
No examples provided.
marketdata_stock_quote ~130
Get a live/delayed stock quote: bid/ask/mid/last, absolute + percent change, and session volume. Example: marketdata_stock_quote({ symbol: "AAPL", _apiKey: "your-key" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Market Data App API token. Get one at https://www.marketdata.app/pricing/ |
| fiftyTwoWeek | boolean | – | Include 52-week high/low in the response. Optional. |
| symbol | string | yes | Stock ticker symbol, e.g. "AAPL", "MSFT", "SPY". |
No output schema declared.
No examples provided.
How do I install the Marketdata App MCP server?
Marketdata App runs locally as an npm package, launched with npx -y @pipeworx/mcp-marketdata-app. 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-marketdata-app
claude mcp add pipeworx-io-marketdata-app -- npx -y @pipeworx/mcp-marketdata-app
What is the Marketdata App MCP server?
Marketdata App is an MCP server listed in the public MCP registry as io.github.pipeworx-io/marketdata-app. Market Data App MCP, wraps the Market Data App API (marketdata.app). This page covers its npm package (@pipeworx/mcp-marketdata-app).
Is the Marketdata App MCP server safe to use?
Marketdata App 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 Marketdata App MCP server expose?
Marketdata App exposes 4 tools: marketdata_option_chain, marketdata_option_quote, marketdata_stock_quote, marketdata_candles. Their descriptions and schemas cost roughly 919 tokens of context every time the server is loaded.
Is the Marketdata App MCP server still maintained?
Marketdata App 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 Marketdata App MCP server under?
Marketdata App 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 Marketdata App MCP server?
VerifyMCP ran 15 checks on Marketdata App, 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 Marketdata App: Security disclosure. 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.