TAS Guard MCP server
io.github.intoApex/tas-guard·v0.5.1Order limits, phone approvals and a kill switch in front of any broker or exchange MCP server.
not scanned yet
0 stars86 downloads/wk
Reviews
Write oneNobody has reviewed TAS Guard yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
TAS Guard tools
No tool declarations could be read from the package source. They show once the server is installed.
How TAS Guard compares
Against every graded E-commerce MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 89/100
- higher than 87% of 2,174 E-commerce servers
- Downloads a week
- 86
- more than 65% of 411 E-commerce servers with a package
Release history: 3 versions in the registry since 2026-10-23, latest 2026-10-30, typically one every 5 days.
Install TAS Guard in Claude Code, Cursor or VS Code
Runs npx -y tas-guard on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add tas-guard -- npx -y tas-guard
What the publisher says
From the TAS Guard repository's README, as published. We do not edit it. Read it on GitHub
TAS Guard
A trading-aware safety proxy for AI agents. Put it between your AI client (Claude, ChatGPT, Cursor, your own agent) and any broker or exchange MCP server. It enforces per-order and daily limits, symbol allowlists, human approvals, a kill switch and a tamper-evident audit log, before an order ever reaches your broker.
AI client ──► TAS Guard ──► Alpaca / CCXT / any trading MCP server ──► your account
│
├─ blocks: over-limit orders, off-list symbols, withdrawals, leverage changes
├─ asks you: large orders, live money, "close everything"
└─ logs: every decision, hash-chainedZero dependencies. About 2,000 lines of plain JavaScript you can read in one sitting.
New in 0.3: onchain (EVM) mode. The same limits, approvals, kill switch and audit log for agents that hold their own wallet: tas-guard rpc is a local JSON-RPC endpoint your agent uses as its RPC URL.
Try it in 10 seconds (no broker account)
tas-guard demo runs the guard in front of a built-in paper broker with simulated prices. Add it to your AI app as an MCP server:
{ "mcpServers": { "tas-guard-demo": { "command": "npx", "args": ["-y", "tas-guard", "demo"] } } }(On Windows use "command": "cmd", "args": ["/c", "npx", "-y", "tas-guard", "demo"].) Then ask your agent to buy 1 SPY at $580 (allowed), 2 SPY at $580 (held for your approval), 10 SPY (blocked: over the $2,000 per-order limit) or 1 TSLA (blocked: not on the allow list). Approve held orders with npx tas-guard approve .
Why not a generic MCP gateway?
Generic gateways decide per tool: "createOrder is critical, require approval." They can't tell a $50 order from a $50,000 one, so you end up approving everything or nothing.
TAS Guard reads the order itself. It knows that Alpaca's placeoptionorder has a 100x contract multiplier, that ccxt's cost is a quote-currency value while amount is base units, and that ccxt answers the first live order with a preview. That's what makes "allow small orders, ask for big ones, never exceed $2,000 a day" possible.
Safety scores and order-gating facts: tradingagentstack.com.
Quick start (Alpaca, paper trading)
- Write ~/tas-guard/alpaca.json (or run npx tas-guard init alpaca-mcp-server):
{
"name": "alpaca",
"profile": "alpaca-mcp-server",
"upstream": {
"command": "uvx",
"args": ["alpaca-mcp-server"],
"env": {
"ALPACA_API_KEY": "${ALPACA_API_KEY}",
"ALPACA_SECRET_KEY": "${ALPACA_SECRET_KEY}",
"ALPACA_PAPER_TRADE": "true"
}
},
"policy": {
"max_order_value": 500,
"max_daily_value": 2000,
"approve_over": 250,
"symbols_allow": ["SPY", "QQQ", "AAPL", "MSFT"]
}
}${VAR} is read from the environment, so keys don't have to live in the file.
- Point your MCP client at the guard instead of at Alpaca. For Claude Desktop (claudedesktopconfig.json):
{
"mcpServers": {
"alpaca": {
"command": "npx",
"args": ["-y", "tas-guard", "run", "--config", "/Users/you/tas-guard/alpaca.json"],
"env": { "ALPACA_API_KEY": "...", "ALPACA_SECRET_KEY": "..." }
}
}
}For Claude Code: claude mcp add alpaca -- npx -y tas-guard run --config ~/tas-guard/alpaca.json
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
TAS Guard: common questions
- Is TAS Guard MCP server safe?
- Yes, by our scan: it is graded A (89/100). Read the TAS Guard safety report
- How do I install TAS Guard?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does TAS Guard need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is TAS Guard maintained?
- The last commit was 12 days ago (2026-10-23). The latest release is v0.5.1.
- What can I use instead of TAS Guard?
- Servers from other publishers that do the same job: Sv Number MCP server, Iran Crypto Exchanges MCP server and Omie MCP server.
- How does TAS Guard compare with other E-commerce MCP servers?
- safety score 89/100 (higher than 87% of 2,174 E-commerce servers); downloads a week 86 (more than 65% of 411 E-commerce servers with a package). Full comparison.
Alternatives to TAS Guard
Same job from other publishers: the closest match first, then the best rated.
- Sv NumberPhone numbers for AI agents: order a private number, read the SMS verification code, hand it back.not reviewedEstablishedB
- Iran Crypto ExchangesUnofficial read-only Iranian crypto exchanges: prices in Toman, order books, trades, candles.not reviewedGrowingA
- OmieMCP server for Omie — ERP, customers, products, orders, invoices, financialsnot reviewedEstablishedB
- Polymarket ToolkitRead-only Polymarket data tools for AI agents: profiles, PnL, market scans. No keys, no orders.not reviewedEstablishedB
- WebCake StorefrontBuild pages and manage products, orders, and content on the WebCake/StoreCake storefront builder.not reviewedGrowingA