FirmFax prop firm data
REMOTE · FIRMFAX.COM · SCANNED SEP 28
Independent rule and fee data on 71 prop trading firms, every figure with its evidence state.
Available components
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 931 tokens (~155/item across 6 items; 6 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 Management57
- Stability observed for 17 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the FirmFax prop firm data MCP server?
FirmFax prop firm data is a hosted endpoint at https://firmfax.com/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 · firmfax.com
claude mcp add --transport http com-firmfax-prop-firm-data 'https://firmfax.com/api/mcp'
{
"mcpServers": {
"com-firmfax-prop-firm-data": {
"url": "https://firmfax.com/api/mcp"
}
}
} {
"servers": {
"com-firmfax-prop-firm-data": {
"type": "http",
"url": "https://firmfax.com/api/mcp"
}
}
} [mcp_servers.com-firmfax-prop-firm-data] url = "https://firmfax.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-firmfax-prop-firm-data": {
"type": "remote",
"url": "https://firmfax.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add com-firmfax-prop-firm-data --url 'https://firmfax.com/api/mcp' --transport streamable-http
mcp_servers:
com-firmfax-prop-firm-data:
url: "https://firmfax.com/api/mcp" {
"McpServers": {
"com-firmfax-prop-firm-data": {
"Transport": "http",
"Url": "https://firmfax.com/api/mcp"
}
}
} assistant mcp add com-firmfax-prop-firm-data -t streamable-http -u 'https://firmfax.com/api/mcp'
{
"mcpServers": {
"com-firmfax-prop-firm-data": {
"type": "http",
"url": "https://firmfax.com/api/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 −1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Sept 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.
- 20 Sept 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.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 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.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
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 28 Sept 2026 · Probed https://firmfax.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=firmfax.com | CN=WE1,O=Google Trust Services,C=US | 9 Aug 2026 | 7 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | f73ba7ae6bed3c960e7fc2a63091f7ea |
| SANs: firmfax.com, *.firmfax.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of firmfax.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| firmfax.com. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://firmfax.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://firmfax.com/api/mcp | HTTPS enforced | 301 | https://firmfax.com/api/mcp |
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 →
compare_firms ~119
Two firms side by side. Reports each figure with its evidence state and whether the pair is comparable at all: a field neither firm records is not a tie, and a field only one records is not a win. No per-field winner is declared, because the direction of "better" for several of these is a judgement the published scoring model already makes; each firm's grade is returned alongside so the verdict comes from that model rather than from this tool.
| Name | Type | Req | Description |
|---|---|---|---|
| a | string | yes | First firm slug. |
| b | string | yes | Second firm slug. |
No output schema declared.
No examples provided.
find_firms ~428
Firms matching every criterion given. A firm whose record does not carry a criterion is never counted as a match and never silently dropped: it is returned separately under unknown, with the field that could not be tested. Absence is common here, so read counts before treating the matched list as the answer.
| Name | Type | Req | Description |
|---|---|---|---|
| assetClass | string | – | Firms recorded as offering this. 21 of 71 records name no asset class and are returned as unknown. |
| dailyLossLimitUnit | string | – | The unit maxDailyLossLimit is in. Daily loss limits are recorded in percent at some firms and in dollars at others, and the two are never compared: a firm recorded in the other unit is returned under… |
| maxActivationFee | number | – | Activation fee at or below this. 42 of 71 record no fee. |
| maxConsistencyPct | number | – | Consistency rule at or below this. 28 of 71 record none. |
| maxDailyLossLimit | number | – | Daily loss limit at or below this, in the unit dailyLossLimitUnit names. 31 of 71 record none. |
| maxMinDaysToPayout | number | – | Minimum days to first payout at or below this, counted as minDaysToPayoutUnit names. 26 of 71 record none. |
| maxMinTradingDays | number | – | Minimum trading days at or below this. 16 of 71 record none. |
| maxResetFee | number | – | Reset fee at or below this. 56 of 71 record no fee. |
| minDaysToPayoutMinProfit | number | – | With winning_days only: the profit a day must reach to count. A firm whose winning days carry a different profit bar is returned under unknown. |
| minDaysToPayoutUnit | string | – | What maxMinDaysToPayout counts: calendar_days, trading_days or winning_days. A wait is compared only with waits counted the same way; a firm counting another way, or stating no unit, is returned unde… |
No output schema declared.
No examples provided.
get_evidence ~140
The stored reading behind a figure: the verbatim quote, the page it came from, and the date we read it. Answers "we hold none" explicitly rather than returning an empty list. `outcome` is load-bearing: a `contradicted`, `contradiction` or `absent` row records what we read, not a figure we publish. Use get_firm for the published figure.
| Name | Type | Req | Description |
|---|---|---|---|
| field | string | – | One field path, e.g. "rules.dailyLossLimit". Omit for every field we hold for this firm. |
| slug | string | yes | The firm slug, e.g. "topstep". |
No output schema declared.
No examples provided.
get_firm ~59
One prop trading firm. Every figure states whether we hold evidence for it, and a firm whose score range spans more than one band carries no letter grade at all.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The firm slug, e.g. "topstep". |
No output schema declared.
No examples provided.
get_rule_changes ~159
The dated record of what changed, newest first. Every entry states its KIND, and most of this tape is FirmFax correcting its own data rather than a firm changing its rules. Read counts before describing industry activity: a total taken across kinds overstates it.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | firm = the firm changed a rule. record = FirmFax corrected its own data. withdrawn = we published an entry and then retracted it. |
| limit | number | – | How many entries to return, newest first. Default 50. |
| since | string | – | ISO date, e.g. "2026-08-01". Entries dated on or after it. |
| slug | string | – | Limit to one firm. Omit for every firm. |
No output schema declared.
No examples provided.
list_firms ~26
Every firm slug and name. Carries no figures, so nothing here needs evidence.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the FirmFax prop firm data MCP server?
FirmFax prop firm data is an MCP server listed in the public MCP registry as com.firmfax/prop-firm-data. Independent rule and fee data on 71 prop trading firms, every figure with its evidence state. This page covers its hosted endpoint (https://firmfax.com/api/mcp).
Is the FirmFax prop firm data MCP server safe to use?
FirmFax prop firm data scores 70 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 FirmFax prop firm data MCP server expose?
FirmFax prop firm data exposes 6 tools: get_firm, get_rule_changes, get_evidence, find_firms, compare_firms, list_firms. Their descriptions and schemas cost roughly 931 tokens of context every time the server is loaded.
Does the FirmFax prop firm data MCP server require authentication?
No. We connected to FirmFax prop firm data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the FirmFax prop firm data MCP server still maintained?
FirmFax prop firm data is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.