Remote MCP · Endpoint

Prop Firm Rules (FloorGuard) MCP server

No. Prop Firm Rules (FloorGuard) answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://floorguard-kappa.vercel.app/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.kburrus64-max/prop-firm-rules
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
87 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Sourced prop-firm daily-loss and max-drawdown rules and a drawdown-room checker. Read-only, no auth.
Listing
From the official MCP registry (active).
Recent checks of Prop Firm Rules (FloorGuard)
CheckedResultHandshake
7 hours agoHandshake completed87 ms
4 days agoHandshake completed85 ms
14 days agoHandshake completed71 ms
15 days agoHandshake completed63 ms
15 days agoHandshake completed572 ms
17 days agoHandshake completed82 ms
18 days agoHandshake completed68 ms
19 days agoHandshake completed54 ms
20 days agoHandshake completed463 ms
21 days agoHandshake completed76 ms
23 days agoHandshake completed92 ms
26 days agoHandshake completed62 ms
28 days agoHandshake completed544 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 23 responding of 23.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Prop Firm Rules (FloorGuard) and makes no claim about it beyond what these checks measured.