alpaca-guard-mcp

MCPcommunity
v0.1.3UnknownMITUpdated 3mo agonpmGitHub

MCP server that wraps the Alpaca trading API with a hard daily USD cap. Paper trading by default. Live trading blocked unless explicit opt-in.

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
47Downloads/wk
3mo agoLast update
Reads these credentials
  • ALPACA_API_KEYAPI keyoptional

    Alpaca API key. Leave unset for paper trading mode.

  • ALPACA_SECRET_KEYAPI keyoptional

    Alpaca secret key.

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
AuthorUnknown
LicenseMIT
Version0.1.3
Sourcenpm+mcp-registry
Trust Status
B
60/100Good
Listed in Forge index+10/10
Publisher identity verified+0/20
Publisher: run `forge publish` from the package repo to claim ownership
Ed25519 publish signature+0/5
Included automatically when the publisher runs `forge publish`
Domain verification+0/5
Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
npm Trusted Publishing (Sigstore)+0/5
Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
npm maintainer match+0/5
Earned once your identity is verified above and that login is an npm maintainer of this package
CVE scan · clean+30/30
Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain
Provenance
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface8 tools · none privileged
Security scan✓ Cleanv0.1.3 · 3d agoHow well does this scan work?
EvalsNone
IndexedAug 26, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

8 tools · none privileged
Statically extracted from the published packagev0.1.3 · 3d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

setupShow alpaca-guard-mcp setup status: env vars, paper/live mode, current daily cap, and ledger file location. Read-only.

Show alpaca-guard-mcp setup status: env vars, paper/live mode, current daily cap, and ledger file location. Read-only.

No input schema was published for this tool.

guard_statusReturn today's spend ledger: daily limit, used so far, remaining, lifetime order count, and recent 10 orders. Read-only.

Return today's spend ledger: daily limit, used so far, remaining, lifetime order count, and recent 10 orders. Read-only.

No input schema was published for this tool.

guard_set_limitSet the daily USD cap. The agent cannot raise its own cap silently — calling this tool is logged in the ledger. Typical use: human operator runs this once to set the daily limit (default $10) before letting the agent loose.

Set the daily USD cap. The agent cannot raise its own cap silently — calling this tool is logged in the ledger. Typical use: human operator runs this once to set the daily limit (default $10) before letting the agent loose.

No input schema was published for this tool.

get_accountAlpaca account snapshot (buying power, cash, equity, portfolio value, PDT flag). Read-only.

Alpaca account snapshot (buying power, cash, equity, portfolio value, PDT flag). Read-only.

No input schema was published for this tool.

get_positionsCurrent open positions on Alpaca (symbol, qty, avg entry price, current price, unrealized P&L). Read-only.

Current open positions on Alpaca (symbol, qty, avg entry price, current price, unrealized P&L). Read-only.

No input schema was published for this tool.

get_latest_quoteLatest bid/ask/mid quote for a given symbol from Alpaca's market-data API. Read-only.

Latest bid/ask/mid quote for a given symbol from Alpaca's market-data API. Read-only.

No input schema was published for this tool.

guarded_place_orderNo description published

This tool published no description. Forge does not invent one.

guarded_close_positionClose a position on Alpaca. Pre-flighted against the daily cap: if closing requires re-opening exposure (short close → re-buy) that exceeds the cap, refuses.

Close a position on Alpaca. Pre-flighted against the daily cap: if closing requires re-opening exposure (short close → re-buy) that exceeds the cap, refuses.

No input schema was published for this tool.

7 of 8 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

MCP server that wraps the Alpaca trading API with a hard daily USD cap. Paper trading by default. Live trading blocked unless explicit opt-in.

Keywords
mcpmodel-context-protocolalpacaalpaca-marketsagentic-tradingai-agentspending-capdaily-limitpaper-tradingguardcircuit-breakerclaudecursor
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-08-30 — observed resolution, not a publisher declaration.

60 packages resolved · 1 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

53 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+41 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

Topics

Related in finance & trading