Skip to content

Prop Firm Rules (FloorGuard)

by kburrus64-max · remote · no sign-in to list tools · v0.1.0 · published by GitHub user kburrus64-max

Sourced prop-firm daily-loss and max-drawdown rules and a drawdown-room checker. Read-only, no auth.

Changes · 1
CompareRegistry entry

3 tools: 1 change things and 2 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http prop-firm-rules https://floorguard-kappa.vercel.app/api/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

3 tools

Changes things 1Claude Code: ask
  • check_drawdownRemaining 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.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 2Claude Code: allow
  • get_rulesFull daily-loss and max-drawdown rules for one program (static/trailing mode, lock, reset time, notes, official source links, firm copy-trading/automation policy).No findings

    Why it is in this group

    • The name "get_rules" says "get": a word for reading.
    Description, as the server wrote it
    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>.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_firmsList supported prop firms and their programs: program ids, account sizes, verified flags and last-verified dates.No findings

    Why it is in this group

    • The name "list_firms" says "list": a word for reading.
    Description, as the server wrote it
    List supported prop firms and their programs: program ids, account sizes, verified flags and last-verified dates. Same data as GET /api/v1/firms.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http prop-firm-rules https://floorguard-kappa.vercel.app/api/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__prop-firm-rules__list_firms",
      "mcp__prop-firm-rules__get_rules"
    ],
    "ask": [
      "mcp__prop-firm-rules__check_drawdown"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as prop-firm-rules. Review it before you use it.