Crypto Vertex
REMOTE · WWW.CRYPTOVERTEX.NET
Read-only crypto screener for Binance: 100+ indicators, funding, OI, CHoCH/BOS/CRT, breadth, F&G.
Available components
Last scanned (21 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Crypto and Web3
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability51
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 3441 tokens (~688/item across 5 items; 5 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 Management7
- Stability observed for 2 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 5 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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 →
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.
- 20 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 19 Nov 26 +35
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 functional
- 15 Nov 26 36
First indexed and scored.
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://www.cryptovertex.net/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.cryptovertex.net | CN=YR1,O=Let's Encrypt,C=US | 14 Oct 2026 | 12 Jan 2027 | RSA 2048 | SHA256-RSA | 6a07bfb1ce2f2ea0d51a8a14b5f0883f651 |
| SANs: www.cryptovertex.net | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.cryptovertex.net. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| net. | DS published | 37331 | 13 | Verified |
| cryptovertex.net. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'sha256-3+RYezLSmmT5/vx18T5BDqPgJ0UBEPzaGPKDM1A/n70=' 'sha256-CEhaccUcxSe8vh0inq+NCYiM/+gBwHGa5a5WrG/qwuk=' https://challenges.cloudflare.com https://s3.tradingview.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com https://cdnjs.cloudflare.com; font-src 'self' data: https://fonts.gstatic.com https://cdnjs.cloudflare.com; img-src 'self' data: blob: https:; connect-src 'self' https: wss:; frame-src https://challenges.cloudflare.com https://*.tradingview.com https://*.tradingview-widget.com; worker-src 'self' blob:; manifest-src 'self'; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'none'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=() |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | No resource metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.cryptovertex.net/mcp | Verified | 200 | |
| http (plaintext) | http://www.cryptovertex.net/mcp | HTTPS enforced | 308 | https://www.cryptovertex.net/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 →
get_coin ~371
Everything Crypto Vertex publishes for one coin: price, performance, volume, trend, funding / open interest (futures), market cap, and per-timeframe indicators, chart patterns, divergence, support/resistance, CRT, SMC signals and a sparkline. The full object is large: pass fields (e.g. "price,rsi14,macd_hist" with timeframe "4h") for a short answer. Unavailable values are null.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | string | – | Comma-separated fields to return per row (symbol is always included); use it for lightweight answers instead of pulling every value. Filtering, sorting and pagination still run over all coins first,… |
| market | string | – | Market. If omitted, spot is used and futures is the fallback. |
| symbol | string | yes | Coin symbol, e.g. "BTC" or "BTCUSDT". |
| timeframe | string | – | One timeframe, or "all" (default) for 1h, 4h, 1d and 1w. |
No output schema declared.
No examples provided.
get_market ~89
Market overview from Crypto Vertex data: for spot and futures — advancing/declining counts, average and median 24h change, total volume, top gainers and losers (min 1M USDT volume), futures funding and long/short aggregates, BTC and ETH snapshots, plus the Fear & Greed index and BTC dominance (each with its updated_at; null if currently unavailable, never estimated).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_meta ~93
Describes the Crypto Vertex data: supported markets and timeframes, every screener filter field and sort field, every valid screener signal id (tm-*, cs-*, smc-*) with its rule and timeframes, signal types, coin counts and when each dataset was last updated. The `fields` section lists every name usable in the fields parameter, with examples. Call this first to learn valid field names.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_screener ~2,608
Screen every listed Crypto Vertex crypto pair (USDT spot or perpetual futures). Filter by any numeric field with min_<field>/max_<field> (price, change_24h, rsi14, adx14, macd_hist, funding_rate, market_cap…), by signal ids (e.g. signals "tm-above-ema200" = price above EMA200 on `timeframe`, same rule as the Crypto Vertex screener "Price Above EMA200" filter; trend/momentum tm-*, candlestick cs-*, structure smc-* ids are listed in get_meta → screener_signals) and chart patterns, then sort and paginate. Filtering AND sorting run over the full list before pagination, and coins with no value for the sort field always come last. For rankings use sort + order directly instead of paging and sorting yourself: "most oversold on 4h" = sort "rsi14", order "asc", timeframe "4h", limit 5; "biggest 24h gainers" = sort "change_24h", order "desc". Each coin row has 100+ values: when you only need a few, pass fields (e.g. "symbol,price,rsi14") to get a small, fast answer. Values that are unavailable are null, never estimated.
| Name | Type | Req | Description |
|---|---|---|---|
| asset_type | string | – | Default any. "regular" excludes stablecoins and gold tokens (PAXG, XAUT), like the Crypto Vertex screener presets. Combine with min_market_cap=5000000 for the preset base. |
| fields | string | – | Comma-separated fields to return per row (symbol is always included); use it for lightweight answers instead of pulling every value. Filtering, sorting and pagination still run over all coins first,… |
| limit | integer | – | Rows per page, 1–200. Default 50. |
| market | string | – | Market to screen. Default spot. Funding / open-interest / long-short fields exist only on futures. |
| max_adx14 | number | – | Maximum ADX(14) trend strength. Coins with no data for this field are excluded. |
| max_atr_pct | number | – | Maximum ATR as % of price. Coins with no data for this field are excluded. |
| max_bb_width_pct | number | – | Maximum Bollinger band width, %. Coins with no data for this field are excluded. |
| max_btc_correlation_30d | number | – | Maximum 30-day correlation with BTC (-1..1). Coins with no data for this field are excluded. |
| max_cci | number | – | Maximum CCI. Coins with no data for this field are excluded. |
| max_change_1h | number | – | Maximum Change of the last closed 1h candle, %. Coins with no data for this field are excluded. |
| max_change_24h | number | – | Maximum Rolling 24h change from the ticker ((price - open24h) / open24h), %; same as the UI 24h column. Coins with no data for this field are excluded. |
| max_change_30d | number | – | Maximum Price change last 30 days, %. Coins with no data for this field are excluded. |
| max_change_4h | number | – | Maximum Change over the last 4 closed 1h candles, %. Coins with no data for this field are excluded. |
| max_change_7d | number | – | Maximum Price change last 7 days, %. Coins with no data for this field are excluded. |
| max_change_90d | number | – | Maximum Price change last 90 days, %. Coins with no data for this field are excluded. |
| max_cvd_change_pct | number | – | Maximum CVD change, %. Coins with no data for this field are excluded. |
| max_funding_rate | number | – | Maximum Perpetual funding rate (futures market only). Coins with no data for this field are excluded. |
| max_long_short_ratio | number | – | Maximum Global long/short account ratio (futures only). Coins with no data for this field are excluded. |
| max_macd_hist | number | – | Maximum MACD histogram. Coins with no data for this field are excluded. |
| max_market_cap | number | – | Maximum Market capitalisation (USD). Coins with no data for this field are excluded. |
| max_open_interest_change_pct | number | – | Maximum Open interest change, % (futures only). Coins with no data for this field are excluded. |
| max_price | number | – | Maximum Last price (USDT). Coins with no data for this field are excluded. |
| max_quote_volume_24h | number | – | Maximum 24h traded volume in USDT. Coins with no data for this field are excluded. |
| max_rsi14 | number | – | Maximum RSI(14) on the chosen timeframe. Coins with no data for this field are excluded. |
| max_rsi25 | number | – | Maximum RSI(25) on the chosen timeframe. Coins with no data for this field are excluded. |
| max_rsi9 | number | – | Maximum RSI(9) on the chosen timeframe. Coins with no data for this field are excluded. |
| max_stoch_k | number | – | Maximum Stochastic %K. Coins with no data for this field are excluded. |
| max_volume_change_24h | number | – | Maximum Volume of the last 24 closed hours vs the 24 hours before, %; same number as the UI Vol Chg 24h % column and filter. Coins with no data for this field are excluded. |
| max_volume_ratio | number | – | Maximum Volume vs its average (ratio). Coins with no data for this field are excluded. |
| max_volume_vs_avg_1d | number | – | Maximum Last closed day volume vs the average of the 10 days before it, %. Coins with no data for this field are excluded. |
| max_williams_r | number | – | Maximum Williams %R. Coins with no data for this field are excluded. |
| max_z_score_20 | number | – | Maximum Price Z-score over 20 candles. Coins with no data for this field are excluded. |
| min_adx14 | number | – | Minimum ADX(14) trend strength. Coins with no data for this field are excluded. |
| min_atr_pct | number | – | Minimum ATR as % of price. Coins with no data for this field are excluded. |
| min_bb_width_pct | number | – | Minimum Bollinger band width, %. Coins with no data for this field are excluded. |
| min_btc_correlation_30d | number | – | Minimum 30-day correlation with BTC (-1..1). Coins with no data for this field are excluded. |
| min_cci | number | – | Minimum CCI. Coins with no data for this field are excluded. |
| min_change_1h | number | – | Minimum Change of the last closed 1h candle, %. Coins with no data for this field are excluded. |
| min_change_24h | number | – | Minimum Rolling 24h change from the ticker ((price - open24h) / open24h), %; same as the UI 24h column. Coins with no data for this field are excluded. |
| min_change_30d | number | – | Minimum Price change last 30 days, %. Coins with no data for this field are excluded. |
| min_change_4h | number | – | Minimum Change over the last 4 closed 1h candles, %. Coins with no data for this field are excluded. |
| min_change_7d | number | – | Minimum Price change last 7 days, %. Coins with no data for this field are excluded. |
| min_change_90d | number | – | Minimum Price change last 90 days, %. Coins with no data for this field are excluded. |
| min_cvd_change_pct | number | – | Minimum CVD change, %. Coins with no data for this field are excluded. |
| min_funding_rate | number | – | Minimum Perpetual funding rate (futures market only). Coins with no data for this field are excluded. |
| min_long_short_ratio | number | – | Minimum Global long/short account ratio (futures only). Coins with no data for this field are excluded. |
| min_macd_hist | number | – | Minimum MACD histogram. Coins with no data for this field are excluded. |
| min_market_cap | number | – | Minimum Market capitalisation (USD). Coins with no data for this field are excluded. |
| min_open_interest_change_pct | number | – | Minimum Open interest change, % (futures only). Coins with no data for this field are excluded. |
| min_price | number | – | Minimum Last price (USDT). Coins with no data for this field are excluded. |
| min_quote_volume_24h | number | – | Minimum 24h traded volume in USDT. Coins with no data for this field are excluded. |
| min_rsi14 | number | – | Minimum RSI(14) on the chosen timeframe. Coins with no data for this field are excluded. |
| min_rsi25 | number | – | Minimum RSI(25) on the chosen timeframe. Coins with no data for this field are excluded. |
| min_rsi9 | number | – | Minimum RSI(9) on the chosen timeframe. Coins with no data for this field are excluded. |
| min_stoch_k | number | – | Minimum Stochastic %K. Coins with no data for this field are excluded. |
| min_volume_change_24h | number | – | Minimum Volume of the last 24 closed hours vs the 24 hours before, %; same number as the UI Vol Chg 24h % column and filter. Coins with no data for this field are excluded. |
| min_volume_ratio | number | – | Minimum Volume vs its average (ratio). Coins with no data for this field are excluded. |
| min_volume_vs_avg_1d | number | – | Minimum Last closed day volume vs the average of the 10 days before it, %. Coins with no data for this field are excluded. |
| min_williams_r | number | – | Minimum Williams %R. Coins with no data for this field are excluded. |
| min_z_score_20 | number | – | Minimum Price Z-score over 20 candles. Coins with no data for this field are excluded. |
| offset | integer | – | Rows to skip (pagination). Filters always run over every coin first; meta.total is the match count. |
| order | string | – | asc = lowest first (e.g. most oversold by rsi14), desc = highest first. Default desc (asc for symbol). |
| pattern | string | – | Comma-separated chart-pattern ids that must ALL be detected, e.g. "double-bottom". |
| q | string | – | Only symbols containing this text, e.g. "PEPE". |
| signals | string | – | Comma-separated signal ids that must ALL be true, evaluated on `timeframe`. Trend/momentum states (tm-*): "tm-above-ema200" (price > EMA200), "tm-golden-cross" (EMA50 > EMA200), "tm-macd-bull", "tm-e… |
| sort | string | – | Field to rank by, across ALL coins. Technical fields (rsi14, macd_hist…) use `timeframe`. Default quote_volume_24h. |
| timeframe | string | – | Timeframe for the technical fields (rsi14, macd_hist, signals…). Default 1d. |
No output schema declared.
No examples provided.
get_signals ~231
Current ICT/SMC structure signals as published by Crypto Vertex: CHoCH (change of character), BOS (break of structure) and CRT (candle range theory) per coin and timeframe. Order blocks and fair value gaps are not published and are not returned. market "forex" returns forex CRT. Pass fields to return only some columns.
| Name | Type | Req | Description |
|---|---|---|---|
| direction | string | – | Default all. |
| fields | string | – | Comma-separated columns to return (symbol is always included), from: symbol, market, timeframe, type, direction, price, range_high, range_low, distribution_target, confidence, prev_high, prev_low, sw… |
| limit | integer | – | Default 50, max 200. |
| market | string | – | Default futures. |
| offset | integer | – | Pagination offset. |
| symbol | string | – | Only symbols containing this text. |
| timeframe | string | – | Default all. |
| type | string | – | Signal type. Default all. |
No output schema declared.
No examples provided.
How do I install the Crypto Vertex MCP server?
Crypto Vertex is a hosted endpoint at https://www.cryptovertex.net/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 · www.cryptovertex.net
claude mcp add --transport http taibi56-crypto-vertex 'https://www.cryptovertex.net/mcp'
What is the Crypto Vertex MCP server?
Crypto Vertex is an MCP server listed in the public MCP registry as io.github.Taibi56/crypto-vertex. Read-only crypto screener for Binance: 100+ indicators, funding, OI, CHoCH/BOS/CRT, breadth, F&G. This page covers its hosted endpoint (https://www.cryptovertex.net/mcp).
Is the Crypto Vertex MCP server safe to use?
Crypto Vertex scores 72 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 Crypto Vertex MCP server expose?
Crypto Vertex exposes 5 tools: get_screener, get_coin, get_signals, get_market, get_meta. Their descriptions and schemas cost roughly 3,392 tokens of context every time the server is loaded.
Does the Crypto Vertex MCP server require authentication?
Yes. Crypto Vertex asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Crypto Vertex MCP server still maintained?
Crypto Vertex 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 Crypto Vertex MCP server?
VerifyMCP ran 13 checks on Crypto Vertex, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.