Sato Hub
MCP

Alpaca MCP Server

Official Alpaca MCP for stock, options, and crypto trading, portfolio and order management, and market data.

  • Sato Score70
ActiveSelf-ReportedActive · 3d ago

Alpaca MCP Server is a MCP server by Alpaca, with last code activity on 2026-10-12 (Active). Latest release on 2026-10-12. Sato Score 70/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-15. How the score works →

See how to install Alpaca MCP Server →

Last commit Sep 25, 2026 · Last release Oct 12, 2026 (v2.4.0) · ★ 1,011

Listed from alpaca.markets on 2026-07-12. Install: not attempted. Evidence →

Next step

Watch Alpaca MCP Server

One email if what we observe changes — its repo goes quiet or disappears, or the listing is retired. Nothing else.

Check it from your agent

Add Sato Hub’s MCP server (no key), then ask:

https://satohub.ai/api/mcp
Run Sato Hub Preflight on alpacahq/alpaca-mcp-server before I use it.
Full setup: Claude Code, Cursor, others →

Your project?

Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.

Claim this listing →

Overview

Alpaca's own MCP server lets an AI agent trade and manage a brokerage account through natural language — placing market/limit/stop/trailing-stop orders, checking portfolios and watchlists, and pulling real-time and historical market data, news, and corporate actions. It runs against Alpaca's brokerage API and defaults to a free paper-trading account. Builders plug it into Claude Desktop, Cursor, VS Code, or other MCP clients via stdio or Streamable HTTP.

Sato Score

70/100· High

How open, active & verifiable — not a safety or returns grade.

Maintenance & liveness
35/35
Code transparency
12/20
Interface verifiability
0/10
Docs & demo
6/10
Listing transparency & provenance
14/15
Independent verification
3/10

Sato Check

v2.4.0 · as of 2026-10-13
Does it take your key?
No key read found
Does your key leave?
Not yet run
Can it move funds on its own?
Unknown
Full profile, evidence and limits →

A profile describes what we read and ran, with dates. It is not a safety rating, an audit or an endorsement, and "not found" is not "not there".

Evidence — listed vs checked · what the words mean

Listed from alpaca.markets on 2026-07-12. Install: not attempted.

ClaimValueEvidenceSourceChecked
Chains supportednot statedself-reporteddocs.alpaca.marketsas of 2026-10-15
Verification statusSelf-Reported — not independently reviewedself-reportedalpaca.marketsas of 2026-10-15
Recent activitylast release 2026-10-12 · last commit 2026-09-25observedgithub.com/alpacahq/alpaca-mcp-server2026-10-15
Install worksdocumented by the project, not run by Sato Hubnot attempted: the run did not complete and the log named no cause we could attributeself-reportedgithub.com/alpacahq/alpaca-mcp-serveras of 2026-09-21
Website answersanswered (HTTP 200)observedalpaca.markets2026-10-15
Daily check record90 of 90 daily checks since 2026-07-17 succeededa success rate of our checks, not uptime; the source is this listing's own historyobserved—2026-10-14
Takes your keyno private-key read found in what we readtracedsatohub.ai2026-10-13
Key leaves the machinenot yet run with planted test keysthe sandbox lane has not run on this versionobservedsatohub.ainot dated
Moves funds on its ownunknown — could not read what it exposestracedsatohub.ai2026-10-13
Deploys asPyPI (uvx/pipx, stdio), Dockerconfidence 0.85self-reportedgithub.com/alpacahq/alpaca-mcp-serveras of 2026-07-14
Works withClaude Desktop, Claude Code, Cursor, VS Code, PyCharm, Antigravity CLIconfidence 0.85self-reportedgithub.com/alpacahq/alpaca-mcp-serveras of 2026-07-14
X accounthttps://x.com/alpacahqconfidence 0.85self-reportedgithub.com/alpacahq/alpaca-mcp-serveras of 2026-07-14
Sato Score70/100 (High)how open, active and verifiable — not a safety or quality gradecomputedsatohub.ai2026-10-15

Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.

Install — not run by us — the run did not complete and the log named no cause we could attribute

Runtime: python

uvx alpaca-mcp-server
{"mcpServers":{"alpaca":{"command":"uvx","args":["alpaca-mcp-server"],"env":{"ALPACA_API_KEY":"...","ALPACA_SECRET_KEY":"..."}}}}

You supply: ALPACA_API_KEY, ALPACA_SECRET_KEY (free paper-trading account at app.alpaca.markets)

Add to CursorAdd to VS Code
claude mcp add satohub-alpaca-mcp -- uvx alpaca-mcp-server

A local server: your client runs this command on your machine. Installing runs third-party software under your own credentials. Sato Hub publishes the documented invocation and, where the harness reproduced it, the date it did — neither is a safety review.

Read from the project’s own docs as of 2026-09-21. What a deploy spec is →

Observed record — 91 daily checks since 2026-07-17

100%of 91 checks since 2026-07-17 succeeded
Currently responding for 91 days
Succeeded
91
Failed
0
Their error
0
Unattributed
0

This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden. 46 of these checks predate 2026-09-01, when the probe counted a bot-block (HTTP 403) as a failure and recorded no reason for any failure. Every one of them passed, so the rate covers them too.

Last 30 days — to 2026-10-15, one point per UTC day

Share of OUR checks that succeeded
100%
7-day rolling; unattributable days are gaps · 30/30 days
Tools listed
fewer than 2 points—
from the server's own tools/list · 0/30 days
Sato Score
70
as snapshotted that day · 29/30 days

A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.

Details

Chains
Unknown
Agent types
Trading, Data Provider
Open source
Unknown
Deploys as
PyPI (uvx/pipx, stdio), Docker
Works with
Claude Desktop, Claude Code, Cursor, VS Code, PyCharm, Antigravity CLI
Last checked
2026-10-15

Marketplace Signals

No marketplace signals recorded for this resource yet.

Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.

#mcp#trading#brokerage#stocks#market-data
See something inaccurate or outdated?Submit a correction →

Recent Activity

All news →

Releases and posts from Alpaca MCP Server, pulled from its GitHub and X.

Listing History

Recorded changes to Alpaca MCP Server's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.

  1. Oct 12, 2026
    New release published
  2. Oct 1, 2026
    Crossed 1k GitHub stars
    990 → 1000.
  3. Sep 21, 2026
    Verified: deploy spec
  4. Jul 18, 2026
    Sato Hub began tracking this listing
  5. Jul 14, 2026
    Auto-enriched: deployment options, supported integrations, x url
  6. Jul 13, 2026
    Listed on Sato Hub

Compared with

Appears in

Related Resources

Reference

QuestionsShowHide

Questions people ask about Alpaca MCP Server

Is Alpaca MCP Server open source?
Unknown. Sato Hub has not found a public repository or a license statement for Alpaca MCP Server as of 2026-10-15.
Which chains does Alpaca MCP Server support?
Sato Hub has no confirmed chain list for Alpaca MCP Server as of 2026-10-15; treat chain support as unknown.
Is Alpaca MCP Server still maintained?
The most recent code activity Sato Hub observed was on 2026-10-12 (last commit 2026-09-25, last release 2026-10-12), which Sato Hub labels "Active". Posts on X are not counted as maintenance. Activity is a recency signal, not a quality judgment.
How do I install or run Alpaca MCP Server?
python. Install: uvx alpaca-mcp-server. Entry: {"mcpServers":{"alpaca":{"command":"uvx","args":["alpaca-mcp-server"],"env":{"ALPACA_API_KEY":"...","ALPACA_SECRET_KEY":"..."}}}}. This is taken from the project's own documentation and has not been reproduced by Sato Hub. It runs as an MCP server (uvx alpaca-mcp-server).
Is Alpaca MCP Server verified on Sato Hub?
No independent verification is on record for Alpaca MCP Server; its verification status is "Self-Reported" and its Sato Score is 70 of 100. Self-reported is not verified, and the score is not a safety, quality or returns grade.
Cite this pageShowHide

Cite this page

Sato Hub. "Alpaca MCP Server — Sato Hub." Sato Hub, updated 2026-10-15, accessed 2026-10-15. https://satohub.ai/resources/alpaca-mcp

Data last refreshed 2026-10-15; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.

Join the Sato Hub Briefing

Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.