Alpaca Trading API integration for Model Context Protocol (MCP)
Prop Firm Rules (FloorGuard) is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Sourced prop-firm daily-loss and max-drawdown rules and a drawdown-room checker. Read-only, no auth.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http prop-firm-rules-floorguard-mcp https://floorguard-kappa.vercel.app/api/mcp
# 2 — ask your agent for something these tools do
# list_firms, get_rules, check_drawdown
Prop Firm Rules (FloorGuard) costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http prop-firm-rules-floorguard-mcp https://floorguard-kappa.vercel.app/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
3 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List supported prop firms and their programs: program ids, account sizes, verified flags and last-verified dates. Same data as GET /api/v1/firms.
No parameter schema on file.
Full daily-loss and max-drawdown rules for one program (static/trailing mode, lock, reset time, notes, official source links, firm copy-trading/automation policy). Same as GET /api/v1/rules?program=<id>.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| program | string | yes | Program id from list_firms, e.g. ftmo_2step |
Remaining daily-loss and max-drawdown room in dollars for an account, the binding limit and breach flags, computed with the same model as the FloorGuard calculator. Same inputs as GET /api/v1/check.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| program | string | yes | Program id from /api/v1/firms, e.g. ftmo_2step |
| accountSize | number | yes | Nominal account size, e.g. 100000 (must be one of the program sizes when the rule is a fixed $ amount per size) |
| startingBalance | number | no | Initial balance the percentages apply to (default: accountSize) |
| currentEquity | number | yes | Current equity including open P&L |
| currentBalance | number | no | Current closed balance (default: currentEquity) |
| highWaterMark | number | no | Peak the firm trails from (highest EOD balance / closed balance / intraday equity, per program mode). Default: computed like the site calculator |
| todayPnl | number | no | Today's P&L since the firm's daily reset, closed + open (default 0) |
| dayStartBalance | number | no | Balance at the daily reset, if positions were held through it (default: currentEquity - todayPnl) |
| customDailyLoss | number | no | Your own daily loss limit in $ for programs without one (e.g. Topstep optional DLL) |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Prop Firm Rules (FloorGuard) or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.1.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Prop Firm Rules (FloorGuard) can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.