# FirmFax prop firm data (remote · firmfax.com)

Independent rule and fee data on 71 prop trading firms, every figure with its evidence state.

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

## Components

- remote · `firmfax.com`: 70/100 (this document), [markdown](https://verifymcp.io/servers/com-firmfax-prop-firm-data/api-mcp.md), [page](https://verifymcp.io/servers/com-firmfax-prop-firm-data/api-mcp)

## Channel facts

- Endpoint: `https://firmfax.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-09-28.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 70/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

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

### Claude

```bash
claude mcp add --transport http com-firmfax-prop-firm-data 'https://firmfax.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-firmfax-prop-firm-data": {
      "url": "https://firmfax.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-firmfax-prop-firm-data": {
      "type": "http",
      "url": "https://firmfax.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-firmfax-prop-firm-data]
url = "https://firmfax.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-firmfax-prop-firm-data": {
      "type": "remote",
      "url": "https://firmfax.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-firmfax-prop-firm-data --url 'https://firmfax.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-firmfax-prop-firm-data:
    url: "https://firmfax.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-firmfax-prop-firm-data": {
      "Transport": "http",
      "Url": "https://firmfax.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-firmfax-prop-firm-data -t streamable-http -u 'https://firmfax.com/api/mcp'
```

### Other

```json
{
  "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.

## 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-09-28 (score 70, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-26 (score 69, +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.

### 2026-09-25 (score 68, −1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 69, +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.

### 2026-09-22 (score 68, +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-09-20 (score 67, +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-09-17 (score 66, +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.

### 2026-09-15 (score 65, +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.

## MCP tools (6)

### `get_firm` (~59 tokens)

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.

Input parameters:

- `slug` (string, required): The firm slug, e.g. "topstep".

### `get_rule_changes` (~159 tokens)

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.

Input parameters:

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

### `get_evidence` (~140 tokens)

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.

Input parameters:

- `field` (string): One field path, e.g. "rules.dailyLossLimit". Omit for every field we hold for this firm.
- `slug` (string, required): The firm slug, e.g. "topstep".

### `find_firms` (~428 tokens)

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.

Input parameters:

- `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…

### `compare_firms` (~119 tokens)

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.

Input parameters:

- `a` (string, required): First firm slug.
- `b` (string, required): Second firm slug.

### `list_firms` (~26 tokens)

Every firm slug and name. Carries no figures, so nothing here needs evidence.

## Diagnostics

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

## Score history

- 2026-09-28: 70
- 2026-09-27: 69
- 2026-09-26: 69
- 2026-09-25: 68
- 2026-09-24: 69
- 2026-09-23: 68
- 2026-09-22: 68
- 2026-09-21: 67
- 2026-09-20: 67
- 2026-09-19: 66
- 2026-09-18: 66
- 2026-09-17: 66
- 2026-09-16: 65
- 2026-09-15: 65
- 2026-09-14: 64
- 2026-09-13: 63
- 2026-09-12: 60
- 2026-09-11: 60

## Common questions

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

## Links

- Remote endpoint: https://firmfax.com/api/mcp
- Website: https://firmfax.com/mcp/
- Changelog RSS feed: https://verifymcp.io/servers/com-firmfax-prop-firm-data/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-firmfax-prop-firm-data/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-firmfax-prop-firm-data/api-mcp