# Prop Firm Rules (FloorGuard) (remote · floorguard-kappa.vercel.app)

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

- Trust score: 79/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- remote · `floorguard-kappa.vercel.app`: 79/100 (this document), [markdown](https://verifymcp.io/servers/kburrus64-max-prop-firm-rules/api-mcp.md), [page](https://verifymcp.io/servers/kburrus64-max-prop-firm-rules/api-mcp)

## Channel facts

- Endpoint: `https://floorguard-kappa.vercel.app/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-17.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 501 tokens (~167/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Prop Firm Rules (FloorGuard) MCP server?

Prop Firm Rules (FloorGuard) is a hosted endpoint at https://floorguard-kappa.vercel.app/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http kburrus64-max-prop-firm-rules 'https://floorguard-kappa.vercel.app/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "kburrus64-max-prop-firm-rules": {
      "url": "https://floorguard-kappa.vercel.app/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "kburrus64-max-prop-firm-rules": {
      "type": "http",
      "url": "https://floorguard-kappa.vercel.app/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.kburrus64-max-prop-firm-rules]
url = "https://floorguard-kappa.vercel.app/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "kburrus64-max-prop-firm-rules": {
      "type": "remote",
      "url": "https://floorguard-kappa.vercel.app/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add kburrus64-max-prop-firm-rules --url 'https://floorguard-kappa.vercel.app/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  kburrus64-max-prop-firm-rules:
    url: "https://floorguard-kappa.vercel.app/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "kburrus64-max-prop-firm-rules": {
      "Transport": "http",
      "Url": "https://floorguard-kappa.vercel.app/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add kburrus64-max-prop-firm-rules -t streamable-http -u 'https://floorguard-kappa.vercel.app/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "kburrus64-max-prop-firm-rules": {
      "type": "http",
      "url": "https://floorguard-kappa.vercel.app/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-15 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-13 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-11 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-10 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 20. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-07 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-06 (score 74, +1)

- [functional improvement] Stability: unverified → 0.07

### 2026-10-04 (score 73)

First indexed and scored.

## MCP tools (3)

### `list_firms` (~42 tokens)

List prop firms and programs

List supported prop firms and their programs: program ids, account sizes, verified flags and last-verified dates. Same data as GET /api/v1/firms.

### `get_rules` (~81 tokens)

Get rules for one program

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>.

Input parameters:

- `program` (string, required): Program id from list_firms, e.g. ftmo_2step

### `check_drawdown` (~289 tokens)

Check remaining drawdown room

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.

Input parameters:

- `accountSize` (number, required): Nominal account size, e.g. 100000 (must be one of the program sizes when the rule is a fixed $ amount per size)
- `currentBalance` (number): Current closed balance (default: currentEquity)
- `currentEquity` (number, required): Current equity including open P&L
- `customDailyLoss` (number): Your own daily loss limit in $ for programs without one (e.g. Topstep optional DLL)
- `dayStartBalance` (number): Balance at the daily reset, if positions were held through it (default: currentEquity - todayPnl)
- `highWaterMark` (number): Peak the firm trails from (highest EOD balance / closed balance / intraday equity, per program mode). Default: computed like the site calculator
- `program` (string, required): Program id from /api/v1/firms, e.g. ftmo_2step
- `startingBalance` (number): Initial balance the percentages apply to (default: accountSize)
- `todayPnl` (number): Today's P&L since the firm's daily reset, closed + open (default 0)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/kburrus64-max-prop-firm-rules/api-mcp#diagnostics

## Score history

- 2026-10-17: 79
- 2026-10-16: 79
- 2026-10-15: 79
- 2026-10-14: 78
- 2026-10-13: 78
- 2026-10-12: 77
- 2026-10-11: 77
- 2026-10-10: 76
- 2026-10-07: 75
- 2026-10-06: 74
- 2026-10-04: 73

## Common questions

### What is the Prop Firm Rules (FloorGuard) MCP server?

Prop Firm Rules (FloorGuard) is an MCP server listed in the public MCP registry as io.github.kburrus64-max/prop-firm-rules. Sourced prop-firm daily-loss and max-drawdown rules and a drawdown-room checker. Read-only, no auth. This page covers its hosted endpoint (https://floorguard-kappa.vercel.app/api/mcp).

### Is the Prop Firm Rules (FloorGuard) MCP server safe to use?

Prop Firm Rules (FloorGuard) scores 79 out of 100 on VerifyMCP. 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 Prop Firm Rules (FloorGuard) MCP server expose?

Prop Firm Rules (FloorGuard) exposes 3 tools: list_firms, get_rules, check_drawdown. Their descriptions and schemas cost roughly 412 tokens of context every time the server is loaded.

### Does the Prop Firm Rules (FloorGuard) MCP server require authentication?

No. We connected to Prop Firm Rules (FloorGuard) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Prop Firm Rules (FloorGuard) MCP server still maintained?

Prop Firm Rules (FloorGuard) is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://floorguard-kappa.vercel.app/api/mcp
- Repository: https://github.com/kburrus64-max/prop-firm-rules
- Website: https://floorguard-kappa.vercel.app/api/
- Changelog RSS feed: https://verifymcp.io/servers/kburrus64-max-prop-firm-rules/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/kburrus64-max-prop-firm-rules/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/kburrus64-max-prop-firm-rules/api-mcp