_ registry / mcp streamable-http · checked 1h ago

proppasscheck

https://proppasscheck.com

Registry code: f5bf93b307204f2d

api record

PropPassCheck is an independent site that helps traders avoid wasting money on prop firm challenges. It takes no money from any prop firm and has no affiliate links. Rules: list_challenges, get_challenge and compare_challenges give each account's rules as checked against the firm's own site, with the date checked; rule_changes lists what firms have changed recently. Use them instead of your own memory of a firm's rules, which may be out of date. Odds: test_trades replays a trader's own closed trades against those rules and returns the chance of passing, the chance of reaching a first payout…

endpoint
https://proppasscheck.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is proppasscheck live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is proppasscheck free to use?
Yes — the hub reached it with no key and no payment.
What tools does proppasscheck have?
13 tools: get_challenge, compare_challenges, test_trades, test_stats, find_best_size, check_overlap, funded_life, fix_strategy, ….
Is proppasscheck safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
263ms

last good check

priced tools
0

of 13 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 13 tools
3 open 10 never probed 3 of 13 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_challenges open 1h ago

    Lists the prop firm accounts PropPassCheck tracks (evaluation challenges and instant funding), each with its id, targets, loss limits, price and the date the rules were last checked. Filter by firm, account type, market, drawdown type, price and the rules a trading style needs (no daily loss limit, no consistency rule, weekend holding, news trading).

    mcp-tool

    {
  "type": "object",
  "properties": {
    "firm": {
      "type": "string",
      "description": "Part of a firm name, for example \"FTMO\". Leave out for all firms."
    },
    "type": {
      "enum": [
        "instant",
        "1-step",
        "2-step",
        "3-step"
      ],
      "type": "string",
      "description": "Account type."
    },
    "market": {
      "enum": [
        "forex",
        "futures"
      ],
      "type": "string",
      "description": "Forex and CFD firms, or futures firms."
    },
    "drawdown": {
      "enum": [
        "static",
        "trailing"
      ],
      "type": "string",
      "description": "static: the maximum loss never moves. trailing: it follows the account up (including ones that lock at the start)."
    },
    "max_price": {
      "type": "number",
      "description": "Only accounts with a recorded fee at or below this, in dollars."
    },
    "news_trading": {
      "type": "boolean",
      "description": "Leave out accounts recorded as restricting trading around news."
    },
    "no_daily_limit": {
      "type": "boolean",
      "description": "Only accounts with no daily loss limit."
    },
    "weekend_holding": {
      "type": "boolean",
      "description": "Leave out accounts recorded as not allowing trades held over the weekend."
    },
    "no_consistency_rule": {
      "type": "boolean",
      "description": "Only accounts with no best-day consistency rule."
    }
  },
  "additionalProperties": false
}
    arguments 56 lines
  • price_history open 1h ago

    List prices with the date tracking began, the lowest list price in the last 30 days and every price change the firm made. Name challenge ids or a firm, or leave both out for every account whose list price changed in the last 90 days. List prices only: PropPassCheck does not track discount codes or use affiliate links.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "firm": {
      "type": "string",
      "description": "Or: part of a firm name, to test that firm's accounts. Leave both out to rank every account."
    },
    "challenge_ids": {
      "type": "array",
      "items": {
        "type": "integer"
      },
      "maxItems": 10,
      "description": "Up to 10 PropPassCheck account ids."
    }
  },
  "additionalProperties": false
}
    arguments 18 lines
  • rule_changes open 1h ago

    Changes PropPassCheck has recorded to prop firms' rules, newest first: targets, loss limits, drawdown type, consistency rules, payouts, splits and prices, with the old and new value and whether the change is better or worse for traders. Filter by firm.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "firm": {
      "type": "string",
      "description": "Part of a firm name. Leave out for all firms."
    },
    "limit": {
      "type": "integer",
      "maximum": 50,
      "minimum": 1,
      "description": "How many to return, default 20."
    }
  },
  "additionalProperties": false
}
    arguments 16 lines
  • get_challenge unknown never probed

    Full rules for one account: profit targets, daily and maximum loss, drawdown type, minimum days, time limit, consistency rule, payout terms, trading restrictions on record (news, weekends, open losses, short trades), price, the firm's source page, the date checked, recent rule changes and any proof-checked payout reports for the firm. Takes a PropPassCheck account id.

    mcp-tool

    {
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "integer",
      "description": "A PropPassCheck account id."
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • compare_challenges unknown never probed

    Puts two to six accounts side by side, rule by rule, and marks the rules that differ.

    mcp-tool

    {
  "type": "object",
  "required": [
    "ids"
  ],
  "properties": {
    "ids": {
      "type": "array",
      "items": {
        "type": "integer"
      },
      "maxItems": 6,
      "minItems": 2,
      "description": "Two to six challenge ids."
    }
  },
  "additionalProperties": false
}
    arguments 18 lines
  • test_trades unknown never probed

    Replays a list of closed trades 1,000 times against prop firm challenge rules and returns, per account: the chance of passing, the chance of reaching a first payout, the usual number of trading days, why failed attempts failed, the average number of attempts, and the likely fees per first payout with the funded profit needed to win them back. Give every closed trade's profit or loss in money and the starting balance of the test. Include each trade's close date when known, so busy and quiet days are kept as they happened. Name up to 10 challenge ids, or a firm, or leave both out to rank every account. Needs real closed trades, not figures made up from a win rate.

    mcp-tool

    {
  "type": "object",
  "required": [
    "trades",
    "starting_balance"
  ],
  "properties": {
    "firm": {
      "type": "string",
      "description": "Or: part of a firm name, to test that firm's accounts. Leave both out to rank every account."
    },
    "scale": {
      "type": "number",
      "maximum": 10,
      "minimum": 0.05,
      "description": "Trade size multiplier to test, default 1 (as traded)."
    },
    "trades": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "profit"
        ],
        "properties": {
          "date": {
            "type": "string",
            "description": "Close date, YYYY-MM-DD. Give it for every trade or for none."
          },
          "profit": {
            "type": "number",
            "description": "Profit (positive) or loss (negative) in account currency, after costs."
          }
        },
        "additionalProperties": false
      },
      "maxItems": 5000,
      "minItems": 1,
      "description": "Closed trades in the order they closed."
    },
    "challenge_ids": {
      "type": "array",
      "items": {
        "type": "integer"
      },
      "maxItems": 10,
      "description": "Up to 10 PropPassCheck account ids."
    },
    "trades_per_day": {
      "type": "number",
      "maximum": 30,
      "minimum": 0.1,
      "description": "Only used when the trades have no dates. Default 2."
    },
    "starting_balance": {
      "type": "number",
      "description": "Account balance the trades started from, in the same currency as the profits.",
      "exclusiveMinimum": 0
    }
  },
  "additionalProperties": false
}
    arguments 62 lines
  • test_stats unknown never probed

    For a trader with no trade list: estimates the chance of passing, the chance of a first payout and the likely fees per payout from a win rate, reward-to-risk, risk per trade and trades per day. It treats every win and every loss as the same size and every day as alike, so it is rougher than a test of real trades and usually a little optimistic.

    mcp-tool

    {
  "type": "object",
  "required": [
    "win_rate",
    "reward_to_risk",
    "risk_per_trade",
    "trades_per_day"
  ],
  "properties": {
    "firm": {
      "type": "string",
      "description": "Or: part of a firm name, to test that firm's accounts. Leave both out to rank every account."
    },
    "win_rate": {
      "type": "number",
      "maximum": 99,
      "minimum": 1,
      "description": "Percentage of trades that win, for example 45."
    },
    "challenge_ids": {
      "type": "array",
      "items": {
        "type": "integer"
      },
      "maxItems": 10,
      "description": "Up to 10 PropPassCheck account ids."
    },
    "reward_to_risk": {
      "type": "number",
      "maximum": 20,
      "minimum": 0.1,
      "description": "Average win divided by average loss, for example 2 for a 1:2 strategy."
    },
    "risk_per_trade": {
      "type": "number",
      "maximum": 10,
      "minimum": 0.05,
      "description": "Percentage of the account lost on a losing trade, for example 1."
    },
    "trades_per_day": {
      "type": "number",
      "maximum": 30,
      "minimum": 0.1,
      "description": "Average trades per trading day, for example 1.5."
    }
  },
  "additionalProperties": false
}
    arguments 48 lines
  • find_best_size unknown never probed

    Runs the same trades (or headline numbers) at eight trade sizes, from a quarter to three times, against up to three accounts, and shows the pass and first-payout chance at each with the best size marked. Answers "should I risk less or more per trade on this challenge?". Give trades with starting_balance, or the four headline numbers.

    mcp-tool

    {
  "type": "object",
  "required": [
    "challenge_ids"
  ],
  "properties": {
    "trades": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "profit"
        ],
        "properties": {
          "date": {
            "type": "string",
            "description": "Close date, YYYY-MM-DD. Give it for every trade or for none."
          },
          "profit": {
            "type": "number",
            "description": "Profit (positive) or loss (negative) in account currency, after costs."
          }
        },
        "additionalProperties": false
      },
      "maxItems": 5000,
      "minItems": 1,
      "description": "Closed trades in the order they closed."
    },
    "win_rate": {
      "type": "number",
      "maximum": 99,
      "minimum": 1,
      "description": "Percentage of trades that win, for example 45."
    },
    "challenge_ids": {
      "type": "array",
      "items": {
        "type": "integer"
      },
      "maxItems": 3,
      "minItems": 1,
      "description": "One to three challenge ids."
    },
    "reward_to_risk": {
      "type": "number",
      "maximum": 20,
      "minimum": 0.1,
      "description": "Average win divided by average loss, for example 2 for a 1:2 strategy."
    },
    "risk_per_trade": {
      "type": "number",
      "maximum": 10,
      "minimum": 0.05,
      "description": "Percentage of the account lost on a losing trade, for example 1."
    },
    "trades_per_day": {
      "type": "number",
      "maximum": 30,
      "minimum": 0.1,
      "description": "Average trades per trading day, for example 1.5."
    },
    "starting_balance": {
      "type": "number",
      "description": "Needed with trades.",
      "exclusiveMinimum": 0
    }
  },
  "additionalProperties": false
}
    arguments 70 lines
  • check_overlap unknown never probed

    For a trader running two to five strategies on the same account. Merges their trades by date and reports how often they trade and lose on the same day, the worst day together against alone, whether they tend to win and lose together, and the odds together against each strategy alone on up to three accounts. Every trade needs a close date. Each strategy's profits are scaled from its own starting balance.

    mcp-tool

    {
  "type": "object",
  "required": [
    "strategies"
  ],
  "properties": {
    "strategies": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "trades",
          "starting_balance"
        ],
        "properties": {
          "name": {
            "type": "string",
            "description": "A short name for the strategy."
          },
          "trades": {
            "type": "array",
            "items": {
              "type": "object",
              "required": [
                "profit"
              ],
              "properties": {
                "date": {
                  "type": "string",
                  "description": "Close date, YYYY-MM-DD. Give it for every trade or for none."
                },
                "profit": {
                  "type": "number",
                  "description": "Profit (positive) or loss (negative) in account currency, after costs."
                }
              },
              "additionalProperties": false
            },
            "maxItems": 5000,
            "minItems": 1,
            "description": "Closed trades in the order they closed."
          },
          "starting_balance": {
            "type": "number",
            "description": "The balance this strategy's test started from.",
            "exclusiveMinimum": 0
          }
        },
        "additionalProperties": false
      },
      "maxItems": 5,
      "minItems": 2
    },
    "challenge_ids": {
      "type": "array",
      "items": {
        "type": "integer"
      },
      "maxItems": 3,
      "description": "Up to three challenge ids. Leave out to use the three accounts where the combination does best."
    }
  },
  "additionalProperties": false
}
    arguments 64 lines
  • funded_life unknown never probed

    For up to five accounts: the chance of getting funded, then what the funded account does over its first six months (126 trading days): payouts on average, money to the trader after the split, how soon the first payout comes, how many funded accounts are lost, and what one attempt is worth counting those payouts. Each payout follows the account's rules; after a payout the profit comes out and the account carries on from its starting balance. Give trades with starting_balance, or the four headline numbers.

    mcp-tool

    {
  "type": "object",
  "required": [
    "challenge_ids"
  ],
  "properties": {
    "trades": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "profit"
        ],
        "properties": {
          "date": {
            "type": "string",
            "description": "Close date, YYYY-MM-DD. Give it for every trade or for none."
          },
          "profit": {
            "type": "number",
            "description": "Profit (positive) or loss (negative) in account currency, after costs."
          }
        },
        "additionalProperties": false
      },
      "maxItems": 5000,
      "minItems": 1,
      "description": "Closed trades in the order they closed."
    },
    "win_rate": {
      "type": "number",
      "maximum": 99,
      "minimum": 1,
      "description": "Percentage of trades that win, for example 45."
    },
    "challenge_ids": {
      "type": "array",
      "items": {
        "type": "integer"
      },
      "maxItems": 5,
      "minItems": 1,
      "description": "One to five challenge ids."
    },
    "reward_to_risk": {
      "type": "number",
      "maximum": 20,
      "minimum": 0.1,
      "description": "Average win divided by average loss, for example 2 for a 1:2 strategy."
    },
    "risk_per_trade": {
      "type": "number",
      "maximum": 10,
      "minimum": 0.05,
      "description": "Percentage of the account lost on a losing trade, for example 1."
    },
    "trades_per_day": {
      "type": "number",
      "maximum": 30,
      "minimum": 0.1,
      "description": "Average trades per trading day, for example 1.5."
    },
    "starting_balance": {
      "type": "number",
      "description": "Needed with trades: the balance the trades started from.",
      "exclusiveMinimum": 0
    }
  },
  "additionalProperties": false
}
    arguments 70 lines
  • fix_strategy unknown never probed

    Retests a trader's own closed trades on up to three accounts with a daily stop at several levels and with a cap of one to three trades a day (guards the PropPassCheck strategy builder can add to an EA, or a trader can follow by hand), and reports the one that lifts the chance of passing (or of a first payout on instant accounts) the most, with how much and a link to build it. Needs real trades with starting_balance; give dates when known so each day's trades stay together.

    mcp-tool

    {
  "type": "object",
  "required": [
    "trades",
    "starting_balance",
    "challenge_ids"
  ],
  "properties": {
    "scale": {
      "type": "number",
      "maximum": 10,
      "minimum": 0.05,
      "description": "Trade size multiplier, default 1."
    },
    "trades": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "profit"
        ],
        "properties": {
          "date": {
            "type": "string",
            "description": "Close date, YYYY-MM-DD. Give it for every trade or for none."
          },
          "profit": {
            "type": "number",
            "description": "Profit (positive) or loss (negative) in account currency, after costs."
          }
        },
        "additionalProperties": false
      },
      "maxItems": 5000,
      "minItems": 1,
      "description": "Closed trades in the order they closed."
    },
    "challenge_ids": {
      "type": "array",
      "items": {
        "type": "integer"
      },
      "maxItems": 3,
      "minItems": 1,
      "description": "One to three challenge ids."
    },
    "trades_per_day": {
      "type": "number",
      "maximum": 30,
      "minimum": 0.1,
      "description": "Only used when the trades have no dates. Default 2."
    },
    "starting_balance": {
      "type": "number",
      "description": "The balance the trades started from.",
      "exclusiveMinimum": 0
    }
  },
  "additionalProperties": false
}
    arguments 60 lines
  • sample_traders unknown never probed

    Eleven sample traders (breakout, trend following, mean reversion, scalping, swing trading, opening range breakout, day trading, high win rate, low win rate, position trading, and a grid sample with no edge) replayed 1,000 times against each account's rules: pass and first-payout chance, best risk per trade, typical days and the usual reason for failing. Give id for every style on one account, or style for the accounts where that style does best. They show how rules treat a style, not anyone's own odds.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "id": {
      "type": "integer",
      "description": "A PropPassCheck account id."
    },
    "style": {
      "enum": [
        "breakout",
        "trend-following",
        "mean-reversion",
        "scalping",
        "swing-trading",
        "opening-range-breakout",
        "day-trading",
        "high-win-rate",
        "low-win-rate",
        "position-trading",
        "grid-martingale"
      ],
      "type": "string",
      "description": "A sample style, to rank accounts for it."
    }
  },
  "additionalProperties": false
}
    arguments 27 lines
  • track_account unknown never probed

    For a trader on a live account: from the trade history since the account started, how far the balance is above the maximum-loss floor (static or trailing), what is left of today's daily loss limit and the balance to stop at, progress to the profit target or a payout, the consistency rule and the day counts, with a status. Every trade needs a YYYY-MM-DD close date. Closed trades only: open trades also count at most firms, and the firm's own dashboard is what counts.

    mcp-tool

    {
  "type": "object",
  "required": [
    "trades",
    "starting_balance",
    "challenge_id"
  ],
  "properties": {
    "stage": {
      "enum": [
        "phase1",
        "phase2",
        "phase3",
        "funded"
      ],
      "type": "string",
      "description": "Which stage the account is in. Default phase1."
    },
    "today": {
      "type": "string",
      "description": "The trader's own date, YYYY-MM-DD, so \"today\" matches their day. Default: today in UTC."
    },
    "trades": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "profit"
        ],
        "properties": {
          "date": {
            "type": "string",
            "description": "Close date, YYYY-MM-DD. Give it for every trade or for none."
          },
          "profit": {
            "type": "number",
            "description": "Profit (positive) or loss (negative) in account currency, after costs."
          }
        },
        "additionalProperties": false
      },
      "maxItems": 5000,
      "minItems": 1,
      "description": "Closed trades in the order they closed."
    },
    "start_date": {
      "type": "string",
      "description": "YYYY-MM-DD the account (or this stage) started. Default: the first trade's date."
    },
    "challenge_id": {
      "type": "integer",
      "description": "The PropPassCheck id of the account being traded."
    },
    "starting_balance": {
      "type": "number",
      "description": "The account's starting balance, for example 100000.",
      "exclusiveMinimum": 0
    }
  },
  "additionalProperties": false
}
    arguments 61 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id f5bf93b307204f2d.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/f5bf93b307204f2d/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/f5bf93b307204f2d/badge.svg)](https://brick.blue/agent/f5bf93b307204f2d?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.