Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

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.

+3 this week 79 Trust /100

Last scanned (9 hours ago)

Scores higher than 82% of remote servers

Reachable. Last reached 17 Oct 2026.

Category Finance and Payments

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability74
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
  • Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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
Changelog

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.

  • 15 Oct 26 +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.

  • 13 Oct 26 +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.

  • 11 Oct 26 +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.

  • 10 Oct 26 +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.

  • 7 Oct 26 +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.

  • 6 Oct 26 +1
    • Stability: unverified → 0.07 ▲ functional
  • 4 Oct 26 73

    First indexed and scored.

Diagnostics

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 17 Oct 2026 · Probed https://floorguard-kappa.vercel.app/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.vercel.app CN=WR1,O=Google Trust Services,C=US 29 Aug 2026 27 Nov 2026 RSA 2048 SHA256-RSA f7911168ffa7d0f4135e24792e7a52a8
SANs: *.vercel.app
CN=WR1,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7fd9e2c2d2048a0474b627a26d0868a7
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of floorguard-kappa.vercel.app. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
vercel.app. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://floorguard-kappa.vercel.app/api/mcp Verified 200
http (plaintext) http://floorguard-kappa.vercel.app/api/mcp HTTPS enforced 308 https://floorguard-kappa.vercel.app/api/mcp
MCP tools · 3 exposed · ~412 tokens

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 →

Tool Tokens
check_drawdown ~289

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.

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

No output schema declared.

No examples provided.

get_rules ~81

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

NameTypeReqDescription
programstringyesProgram id from list_firms, e.g. ftmo_2step

No output schema declared.

No examples provided.

list_firms ~42

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

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.

remote · floorguard-kappa.vercel.app

# add to Claude Code
claude mcp add --transport http kburrus64-max-prop-firm-rules 'https://floorguard-kappa.vercel.app/api/mcp'
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.