Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

X PrimeFlow

REMOTE · MCP.XPRIMEFLOW.TRADE

Read-only market and on-chain data: BTC and ETH network stats, liquidations, Hyperliquid traders

71 Trust /100

Last scanned (2 hours ago)

Scores higher than 56% of remote servers

Reachable. Last reached 21 Nov 2026.

Trust breakdown (7 categories)

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 Security74
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • 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
Schema Quality & AI Usability72
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1186 tokens (~118/item across 10 items; 10 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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 26 71

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://mcp.xprimeflow.trade/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=xprimeflow.trade CN=WE1,O=Google Trust Services,C=US 29 Oct 2026 27 Jan 2027 ECDSA 256 ECDSA-SHA256 536147a352e8b5e013b13f6486d6bf59
SANs: xprimeflow.trade, *.xprimeflow.trade
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 mcp.xprimeflow.trade. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
trade. DS published 64969 8 Verified
xprimeflow.trade. No DS 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
Header Value
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.xprimeflow.trade/mcp Verified 200
http (plaintext) http://mcp.xprimeflow.trade/mcp HTTPS enforced 301 https://mcp.xprimeflow.trade/mcp
MCP tools · 10 exposed · ~1,106 tokens

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 →

Tool Tokens
bonynode_validator_status ~56

Whether the BonyNode validator is in the active set on the chains it validates, with its status as read from the chains.

NameTypeReqDescription
chainstring–Optional chain id or name to filter, for example cosmoshub.

No output schema declared.

No examples provided.

btc_network_metrics ~112

Daily Bitcoin network series computed by X PrimeFlow on its own Bitcoin full node: hash rate, difficulty, transaction count, unique addresses, coin days destroyed, NVT ratio, miner revenue in BTC and fee rates. Returns the latest values or one series with up to 365 daily points, with asOf and age.

NameTypeReqDescription
daysinteger–How many latest daily points to return (1–365).
metricstring–One daily series. Omit to get the latest value of every series.

No output schema declared.

No examples provided.

chain_overview ~161

State of the Ethereum, Gno.land, AtomOne and Provenance networks read by X PrimeFlow from its own nodes: overview, network, staking, validators, governance and other sections. Parts that were answered by a node we may not redistribute are held back and listed.

NameTypeReqDescription
chainstringyesNetwork.
sectionstring–Section. Ethereum: overview, network, burn, staking, stablecoins, l2, coverage. Gno: overview, network, validators, governance, registry, gnoswap, pools, infrastructure. AtomOne: overview, network, s…

No output schema declared.

No examples provided.

data_sources_status ~97

Where X PrimeFlow data comes from and how fresh each collector is, plus reference lists: indicator definitions, the coin-to-sector taxonomy and real-world-asset categories.

NameTypeReqDescription
categorystring–For topic=sources: list every source of one category instead of only those not ok.
topicstringyessources = freshness of every collector; indicators = indicator definitions; sectors = coin sectors; rwa = real-world-asset categories.

No output schema declared.

No examples provided.

eth_network_metrics ~124

Daily Ethereum series computed by X PrimeFlow on its own execution (geth) and beacon (lighthouse) nodes: ETH burned, base fee, gas, blob fees, validators and staked ETH, stablecoin supply on L1 and ETH held in L2 bridges. Returns the latest values or one series with up to 365 daily points, with asOf and age.

NameTypeReqDescription
daysinteger–How many latest daily points to return (1–365).
metricstring–One daily series. Omit to get the latest value of every series.

No output schema declared.

No examples provided.

hyperliquid_trader_board ~109

Hyperliquid traders ranked by X PrimeFlow by how copyable their trading was over the last 30 days, recomputed from raw fills: realised PnL of closed round trips, win rate against payoff, profit factor, drawdown of the PnL curve, tenure and three copyability checks. The venue leaderboard supplies only the list of addresses. The board is rebuilt every few hours.

NameTypeReqDescription
limitinteger–How many top rows to return (1–25).

No output schema declared.

No examples provided.

macro_cot_m2 ~104

CFTC Commitments of Traders for CME Bitcoin futures (weekly positions of leveraged funds, asset managers, dealers and small traders) and US M2 money supply from the Federal Reserve H.6 release, monthly and weekly.

NameTypeReqDescription
pointsinteger–How many latest rows or points to return.
seriesstringyescme-cot = weekly COT rows; us-m2 = monthly M2; us-m2-weekly = weekly M2.

No output schema declared.

No examples provided.

onchain_liquidations ~119

Liquidations of perpetual positions on Hyperliquid and Helix (Injective) for one coin over the last 24 hours and 7 days: long and short USD totals, event counts and the largest liquidation. Each venue shows up to which time its feed has been read. Coins are those of the open liquidation summary: ETH, SOL, BNB, AVAX, ATOM, INJ, TIA, DYDX, ASTER. BTC is not part of this open summary.

NameTypeReqDescription
coinstringyesCoin symbol.

No output schema declared.

No examples provided.

sec_13f_holdings ~106

Quarterly 13F holdings of institutional managers, matched by X PrimeFlow: biggest inflows and outflows by stock, the largest filers, holders of one stock, positions of one manager, and dataset coverage. Long positions above the reporting threshold only.

NameTypeReqDescription
cikstring–SEC CIK number of the manager, digits only.
symbolstring–US ticker in upper case.
viewstringyesholders needs symbol; fund needs cik.

No output schema declared.

No examples provided.

sec_filings_insiders ~118

Company filings with the SEC parsed by X PrimeFlow: 8-K events and 13D/13G stakes, Form 4 insider transactions, and crypto treasury holdings reported in filings, for a tracked universe of crypto-related and large US companies. Summary views need no ticker; per-company views take a ticker.

NameTypeReqDescription
symbolstring–US ticker in upper case, for example COIN or MSTR.
viewstringyesfilings_summary and insiders_summary cover all tracked companies; filings, insiders and treasury need symbol.

No output schema declared.

No examples provided.

Install

How do I install the X PrimeFlow MCP server?

X PrimeFlow is a hosted endpoint at https://mcp.xprimeflow.trade/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 · mcp.xprimeflow.trade

# add to Claude Code
claude mcp add --transport http trade-xprimeflow-mcp 'https://mcp.xprimeflow.trade/mcp'
Common questions

What is the X PrimeFlow MCP server?

X PrimeFlow is an MCP server listed in the public MCP registry as trade.xprimeflow/mcp. Read-only market and on-chain data: BTC and ETH network stats, liquidations, Hyperliquid traders. This page covers its hosted endpoint (https://mcp.xprimeflow.trade/mcp).

Is the X PrimeFlow MCP server safe to use?

X PrimeFlow scores 71 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 X PrimeFlow MCP server expose?

X PrimeFlow exposes 10 tools: btc_network_metrics, eth_network_metrics, onchain_liquidations, hyperliquid_trader_board, sec_filings_insiders, and 5 more. Their descriptions and schemas cost roughly 1,106 tokens of context every time the server is loaded.

Does the X PrimeFlow MCP server require authentication?

No. We connected to X PrimeFlow without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the X PrimeFlow MCP server still maintained?

X PrimeFlow is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the X PrimeFlow MCP server?

VerifyMCP ran 12 checks on X PrimeFlow, covering TLS certificate, Authorization, HTTPS, HSTS header and 8 more. One item could not be completed, a gap on our side rather than a finding about X PrimeFlow: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.