Alpaca
NPM · @PIPEWORX/MCP-ALPACA · 2 COMPONENTS
Alpaca MCP — real-time US stock market data via the Alpaca Market Data API (data.alpaca.markets…
Available components
Last scanned (8 hours ago)
Scores higher than 68% 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-alpaca). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability59
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 925 tokens (~308/item across 3 items; 3 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 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 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 31 Oct 26 +1
- Security disclosure: fail → unverified ▼ functional
- 30 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 29 Oct 26 78
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-alpaca@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-alpaca |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-alpaca/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3587918785 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:e98959f1958bfaa6d0d3a5d1fa1fa0a46eb51bb575ba47a222c9cfea0913f345135a95813ec1b0c686c587c07f61fc3f5dc485709f218eecedf0c9fbb |
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 →
alpaca_bars ~399
Historical US stock OHLCV bars with per-bar VWAP and trade count. Timeframes 1Min/5Min/15Min/1Hour/1Day; intraday bars include pre-market and after-hours sessions on the IEX feed. Each bar: {t, o, h, l, c, v, vwap, trades}. Use start/end ISO timestamps or a lookback shorthand like "2h", "5d". Multiple symbols comma-separated (max 20). BYOK Alpaca (free account). Example: alpaca_bars({ symbols: "AAPL", timeframe: "5Min", lookback: "1d", _apiKey: "key_id:secret_key" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | REQUIRED: your Alpaca credentials as "key_id:secret_key" — both halves joined by a colon. Free at alpaca.markets (a paper-trading account is enough for market data). |
| end | string | – | End time, ISO/RFC-3339 or date (default: now) |
| limit | number | – | Max bars per symbol to return, 1-1000 (default 100) |
| lookback | string | – | Shorthand window ending now, instead of start/end: e.g. "30m", "2h", "1d", "5d", "2w" |
| start | string | – | Start time, ISO/RFC-3339 (e.g. "2026-07-18T09:30:00-04:00") or date "2026-07-18" |
| symbols | string | yes | Comma-separated ticker symbols, e.g. "AAPL,MSFT" (max 20) |
| timeframe | string | – | Bar size: "1Min", "5Min", "15Min", "1Hour", or "1Day" (default "5Min") |
No output schema declared.
No examples provided.
alpaca_intraday_vwap ~246
Current session VWAP for US stocks — is the price above or below VWAP right now? Fetches today's 1-minute bars from 04:00 ET (pre-market included), computes the cumulative volume-weighted average price, and compares it to the latest trade. Returns current_price, session_vwap, above_vwap, and session volume per symbol. Answers "current VWAP for BLK, AAPL, RHI, CTAS — above or below?" in one call. Multiple symbols comma-separated (max 20). BYOK Alpaca (free account), real-time IEX feed. Example: alpaca_intraday_vwap({ symbols: "BLK,AAPL,RHI,CTAS", _apiKey: "key_id:secret_key" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | REQUIRED: your Alpaca credentials as "key_id:secret_key" — both halves joined by a colon. Free at alpaca.markets (a paper-trading account is enough for market data). |
| symbols | string | yes | Comma-separated ticker symbols, e.g. "BLK,AAPL,RHI,CTAS" (max 20) |
No output schema declared.
No examples provided.
alpaca_snapshot ~227
Real-time US stock snapshot with extended-hours coverage: latest trade price, bid/ask quote, today's OHLCV, previous close, change and change % vs previous close, plus the latest minute bar with its VWAP — during pre-market and after-hours the minute bar IS the live extended-hours price. Answers "pre-market price of OKTA", "overnight change %", "after-hours volume and high/low". Multiple symbols comma-separated (max 20). BYOK Alpaca (free account), real-time IEX feed. Example: alpaca_snapshot({ symbols: "OKTA,AAPL", _apiKey: "key_id:secret_key" })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | REQUIRED: your Alpaca credentials as "key_id:secret_key" — both halves joined by a colon. Free at alpaca.markets (a paper-trading account is enough for market data). |
| symbols | string | yes | Comma-separated ticker symbols, e.g. "OKTA" or "BLK,AAPL,RHI,CTAS" (max 20) |
No output schema declared.
No examples provided.
How do I install the Alpaca MCP server?
Alpaca runs locally as an npm package, launched with npx -y @pipeworx/mcp-alpaca. 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-alpaca
claude mcp add pipeworx-io-alpaca -- npx -y @pipeworx/mcp-alpaca
What is the Alpaca MCP server?
Alpaca is an MCP server listed in the public MCP registry as io.github.pipeworx-io/alpaca. Alpaca MCP, real-time US stock market data via the Alpaca Market Data API (data.alpaca.markets… This page covers its npm package (@pipeworx/mcp-alpaca).
Is the Alpaca MCP server safe to use?
Alpaca scores 81 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 Alpaca MCP server expose?
Alpaca exposes 3 tools: alpaca_snapshot, alpaca_bars, alpaca_intraday_vwap. Their descriptions and schemas cost roughly 872 tokens of context every time the server is loaded.
Is the Alpaca MCP server still maintained?
Alpaca 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 Alpaca MCP server under?
Alpaca declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.