io.github.evidai/alpaca-guard
NPM · ALPACA-GUARD-MCP · SCANNED SEP 21
Alpaca trading API with hard daily USD cap guard. Paper trading default; live opt-in.
Available components
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 Security98
- 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
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 122 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 627 tokens (~78/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 70% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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
How do I install the io.github.evidai/alpaca-guard MCP server?
io.github.evidai/alpaca-guard runs locally as an npm package, launched with npx -y alpaca-guard-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · alpaca-guard-mcp
claude mcp add evidai-alpaca-guard -- npx -y alpaca-guard-mcp
{
"mcpServers": {
"evidai-alpaca-guard": {
"command": "npx",
"args": [
"-y",
"alpaca-guard-mcp"
]
}
}
} {
"servers": {
"evidai-alpaca-guard": {
"command": "npx",
"args": [
"-y",
"alpaca-guard-mcp"
]
}
}
} codex mcp add evidai-alpaca-guard -- npx -y alpaca-guard-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"evidai-alpaca-guard": {
"type": "local",
"command": [
"npx",
"-y",
"alpaca-guard-mcp"
],
"enabled": true
}
}
} openclaw mcp add evidai-alpaca-guard --command npx --arg -y --arg alpaca-guard-mcp
mcp_servers:
evidai-alpaca-guard:
command: "npx"
args: ["-y", "alpaca-guard-mcp"] {
"McpServers": {
"evidai-alpaca-guard": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"alpaca-guard-mcp"
]
}
}
} assistant mcp add evidai-alpaca-guard -t stdio -c npx -a -y alpaca-guard-mcp
{
"mcpServers": {
"evidai-alpaca-guard": {
"command": "npx",
"args": [
"-y",
"alpaca-guard-mcp"
]
}
}
} 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.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −3
- Stability: pass → 0.80 functional
- 9 Sept 26 +1
- Stability: 0.97 → pass security
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 21 Sept 2026 · Analysed npm/alpaca-guard-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| 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 →
get_account ~30
Alpaca account snapshot (buying power, cash, equity, portfolio value, PDT flag). Read-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_latest_quote ~46
Latest bid/ask/mid quote for a given symbol from Alpaca's market-data API. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | yes | e.g. AAPL, TSLA |
No output schema declared.
No examples provided.
get_positions ~35
Current open positions on Alpaca (symbol, qty, avg entry price, current price, unrealized P&L). Read-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
guard_set_limit ~78
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.
| Name | Type | Req | Description |
|---|---|---|---|
| dailyLimitUsd | number | yes | Non-negative USD value. Set 0 to disable trading entirely. |
No output schema declared.
No examples provided.
guard_status ~35
Return today's spend ledger: daily limit, used so far, remaining, lifetime order count, and recent 10 orders. Read-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
guarded_close_position ~77
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.
| Name | Type | Req | Description |
|---|---|---|---|
| qty | number | – | Optional — partial close. If omitted, closes the full position. |
| symbol | string | yes | Ticker of the position to close |
No output schema declared.
No examples provided.
guarded_place_order ~162
Place an order on Alpaca, but ONLY if the trade's notional USD value fits within today's remaining cap. Pre-flight is mandatory: agent cannot override. If notional > remaining, returns BUDGET_EXCEEDED with a structured hint. On success the charge is recorded to the local ledger so the cap survives MCP restarts. Returns: { allowed, status, tradeNotionalUsd, remainingUsd, limitUsd, alpacaOrder?, x402Receipt? }
| Name | Type | Req | Description |
|---|---|---|---|
| limitPrice | number | – | Required if type=limit |
| qty | number | yes | Quantity in shares |
| side | string | yes | – |
| symbol | string | yes | Ticker e.g. AAPL |
| tif | string | – | – |
| type | string | – | – |
No output schema declared.
No examples provided.
setup ~36
Show alpaca-guard-mcp setup status: env vars, paper/live mode, current daily cap, and ledger file location. Read-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the io.github.evidai/alpaca-guard MCP server?
io.github.evidai/alpaca-guard is an MCP server listed in the public MCP registry as io.github.evidai/alpaca-guard. Alpaca trading API with hard daily USD cap guard. Paper trading default; live opt-in. This page covers its npm package (alpaca-guard-mcp).
Is the io.github.evidai/alpaca-guard MCP server safe to use?
io.github.evidai/alpaca-guard scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. 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 io.github.evidai/alpaca-guard MCP server expose?
io.github.evidai/alpaca-guard exposes 8 tools: setup, guard_status, guard_set_limit, get_account, get_positions, and 3 more. Their descriptions and schemas cost roughly 499 tokens of context every time the server is loaded.
Is the io.github.evidai/alpaca-guard MCP server still maintained?
io.github.evidai/alpaca-guard is still listed as active in the MCP registry. We last reached this channel on 21 September 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 io.github.evidai/alpaca-guard MCP server under?
io.github.evidai/alpaca-guard declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.