This public directory lists broker families and exact MT5 server examples only when the backend directory can expose them safely. A ready status means runtime validation exists; discovered or manual fallback statuses are not promises of support.
| Broker family | Public status | Exact server examples | Public counts | Last validated |
|---|---|---|---|---|
| Exness | Ready Runtime validated on connected accounts. |
|
4 servers 2 profiles |
|
| Admirals | Ready Runtime validated on connected accounts. |
|
4 servers 2 profiles |
|
| PU Prime | Ready Runtime validated on connected accounts. |
|
7 servers 5 profiles |
|
| gatesfx | Ready Runtime validated on connected accounts. |
|
1 servers 1 profiles |
|
| mexatlantic-real | Ready Runtime validated on connected accounts. |
|
1 servers 3 profiles |
|
| Vantage | Ready Runtime validated on connected accounts. |
|
19 servers 8 profiles |
|
| vtmarkets-live | Ready Runtime validated on connected accounts. |
|
2 servers 2 profiles |
Why exact server names matter
MT5 servers are broker-specific and can differ by live environment, region, prop firm, or infrastructure lane. Entering the exact server name lets support classify the account against backend evidence instead of guessing from the broker brand.