Crypto Vertex

io.github.Taibi56/crypto-vertex

Read-only crypto screener for Binance: 100+ indicators, funding, OI, CHoCH/BOS/CRT, breadth, F&G.

Connect this server

One click to install, or copy the config below. Suits: Cursor · HTTP clients.

Add to Cursor Add to VS CodeClaude Desktop / Claude Code: paste the config below.

Or add it manually — claude_desktop_config.json (Claude Desktop) or .cursor/mcp.json (Cursor):

{
  "mcpServers": {
    "crypto-vertex": {
      "url": "https://www.cryptovertex.net/mcp"
    }
  }
}
One line, from the terminal
Claude Code
claude mcp add --transport http crypto-vertex https://www.cryptovertex.net/mcp
VS Code
code --add-mcp '{"name":"crypto-vertex","type":"http","url":"https://www.cryptovertex.net/mcp"}'

Syntax from each client's docs (Claude Code: claude mcp add; Codex: codex mcp add; VS Code: code --add-mcp). Placeholders in angle brackets are values you fill in. Codex takes hosted servers in config.toml ([mcp_servers.<name>] url = …) rather than on the command line.

A starting point — check the repository for exact arguments and setup. Restart your client after editing the config.

Category
Crypto & Web3
Version
1.0.1
Registry
active
Published
11/19/2026
Listed in:Official MCP registry ↗how this is checked

Is it safe? Is it maintained?

Serverdex check: Nov 22, 2026

Mostly fine: Crypto Vertex is hosted endpoint answering without a key.

Maintained
No commit data
The repository has not been read yet, so the last-commit date is unknown.
Official registry
Active
Published as io.github.Taibi56/crypto-vertex in the official MCP registry, version 1.0.1.
Source
No licence found
Public repository, but GitHub reports no recognised licence. Check the README before shipping it in a product.
Runs
Hosted by the publisher
Your client talks to www.cryptovertex.net: prompts and tool arguments leave your machine for that host.
Credentials
None needed to connect
The hosted endpoint completed the Serverdex initialize + tools/list handshake with no key (checked Nov 22, 2026); individual tools may still ask for one.
Owner
Unclaimed
Nobody has claimed this page yet; the data above comes from the registry, GitHub and the live check.

Facts only: last commit and licence from GitHub, the entry's status from the official registry, credentials from the live check. Not a code audit — run the security scan on the endpoint yourself and see the status history.

Live check

checked Nov 22, 2026, 15:07 UTCStatus history & uptime →
● Working209 msprotocol 2025-06-18v1.0.0tools

The endpoint answered the MCP handshake as "Crypto Vertex" and listed 5 tools. Answering since Nov 20, 2026.

Context cost ≈ 4.3k tokens of tool definitions a client loads per conversation (estimate: characters ÷ 4) across 5 tools.

Tools (5)

  • get_screener40 params

    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.

    Show parameters
    • marketstringMarket to screen. Default spot. Funding / open-interest / long-short fields exist only on futures.
    • timeframestringTimeframe for the technical fields (rsi14, macd_hist, signals…). Default 1d.
    • qstringOnly symbols containing this text, e.g. "PEPE".
    • signalsstringComma-separated signal ids that must ALL be true, evaluated on `timeframe`. Trend/momentum states (tm-*): "tm-above-ema200" (price > EMA200), "tm-golden-cross"
    • asset_typestringDefault any. "regular" excludes stablecoins and gold tokens (PAXG, XAUT), like the Crypto Vertex screener presets. Combine with min_market_cap=5000000 for the p
    • patternstringComma-separated chart-pattern ids that must ALL be detected, e.g. "double-bottom".
    • sortstringField to rank by, across ALL coins. Technical fields (rsi14, macd_hist…) use `timeframe`. Default quote_volume_24h.
    • orderstringasc = lowest first (e.g. most oversold by rsi14), desc = highest first. Default desc (asc for symbol).
    • limitintegerRows per page, 1–200. Default 50.
    • offsetintegerRows to skip (pagination). Filters always run over every coin first; meta.total is the match count.
    • fieldsstringComma-separated fields to return per row (symbol is always included); use it for lightweight answers instead of pulling every value. Filtering, sorting and pagi
    • min_pricenumberMinimum Last price (USDT). Coins with no data for this field are excluded.
    • max_pricenumberMaximum Last price (USDT). Coins with no data for this field are excluded.
    • min_quote_volume_24hnumberMinimum 24h traded volume in USDT. Coins with no data for this field are excluded.
    • max_quote_volume_24hnumberMaximum 24h traded volume in USDT. Coins with no data for this field are excluded.
    • min_change_1hnumberMinimum Change of the last closed 1h candle, %. Coins with no data for this field are excluded.
    • max_change_1hnumberMaximum Change of the last closed 1h candle, %. Coins with no data for this field are excluded.
    • min_change_4hnumberMinimum Change over the last 4 closed 1h candles, %. Coins with no data for this field are excluded.
    • max_change_4hnumberMaximum Change over the last 4 closed 1h candles, %. Coins with no data for this field are excluded.
    • min_change_24hnumberMinimum 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_24hnumberMaximum 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_7dnumberMinimum Price change last 7 days, %. Coins with no data for this field are excluded.
    • max_change_7dnumberMaximum Price change last 7 days, %. Coins with no data for this field are excluded.
    • min_change_30dnumberMinimum Price change last 30 days, %. Coins with no data for this field are excluded.
    • max_change_30dnumberMaximum Price change last 30 days, %. Coins with no data for this field are excluded.
    • min_change_90dnumberMinimum Price change last 90 days, %. Coins with no data for this field are excluded.
    • max_change_90dnumberMaximum Price change last 90 days, %. Coins with no data for this field are excluded.
    • min_volume_change_24hnumberMinimum 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 a
    • max_volume_change_24hnumberMaximum 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 a
    • min_volume_vs_avg_1dnumberMinimum Last closed day volume vs the average of the 10 days before it, %. Coins with no data for this field are excluded.
    • max_volume_vs_avg_1dnumberMaximum Last closed day volume vs the average of the 10 days before it, %. Coins with no data for this field are excluded.
    • min_market_capnumberMinimum Market capitalisation (USD). Coins with no data for this field are excluded.
    • max_market_capnumberMaximum Market capitalisation (USD). Coins with no data for this field are excluded.
    • min_funding_ratenumberMinimum Perpetual funding rate (futures market only). Coins with no data for this field are excluded.
    • max_funding_ratenumberMaximum Perpetual funding rate (futures market only). Coins with no data for this field are excluded.
    • min_open_interest_change_pctnumberMinimum Open interest change, % (futures only). Coins with no data for this field are excluded.
    • max_open_interest_change_pctnumberMaximum Open interest change, % (futures only). Coins with no data for this field are excluded.
    • min_long_short_rationumberMinimum Global long/short account ratio (futures only). Coins with no data for this field are excluded.
    • max_long_short_rationumberMaximum Global long/short account ratio (futures only). Coins with no data for this field are excluded.
    • min_btc_correlation_30dnumberMinimum 30-day correlation with BTC (-1..1). Coins with no data for this field are excluded.
  • get_coin4 params

    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.

    Show parameters
    • symbolstringrequiredCoin symbol, e.g. "BTC" or "BTCUSDT".
    • marketstringMarket. If omitted, spot is used and futures is the fallback.
    • timeframestringOne timeframe, or "all" (default) for 1h, 4h, 1d and 1w.
    • fieldsstringComma-separated fields to return per row (symbol is always included); use it for lightweight answers instead of pulling every value. Filtering, sorting and pagi
  • get_signals8 params

    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.

    Show parameters
    • marketstringDefault futures.
    • timeframestringDefault all.
    • typestringSignal type. Default all.
    • directionstringDefault all.
    • symbolstringOnly symbols containing this text.
    • limitintegerDefault 50, max 200.
    • offsetintegerPagination offset.
    • fieldsstringComma-separated columns to return (symbol is always included), from: symbol, market, timeframe, type, direction, price, range_high, range_low, distribution_targ
  • 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).

  • get_meta

    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.

Checked by Serverdex with a plain initialize + tools/list call to www.cryptovertex.net/mcp, no credentials, about once a day. A failed check is never a removal.

Remotes

  • streamable-httphttps://www.cryptovertex.net/mcp

The most-starred Crypto & Web3 servers in the index, with their live-check result.

ServerStarsLast pushLive check
Oh My Posh Validator23,772Nov 2026Working
Solana MCP by Vybe2,811Oct 2026Working
Solana MCP by Vybe2,811Oct 2026Working
Oracle3 prediction-market agent tools569Nov 2026Local / not checked
Flyto Core483Nov 2026Local / not checked

Crypto Vertex: questions people ask

Is Crypto Vertex a remote or a local MCP server?
According to its entry in the official MCP registry, Crypto Vertex ships as a hosted endpoint (streamable-http) that your client connects to by URL.
Does Crypto Vertex need an API key?
Its hosted endpoint completed the Serverdex live check — an MCP initialize + tools/list call — with no credentials on Nov 22, 2026. Individual tools may still ask for a key when called.
Is Crypto Vertex safe to use?
Mostly fine: Crypto Vertex is hosted endpoint answering without a key. In detail — maintained: No commit data; official registry: Active; source: No licence found; runs: Hosted by the publisher; credentials: None needed to connect. Serverdex check of Nov 22, 2026. This is a reading of the repository, the registry entry and the live check, not a code audit; run the Serverdex security scan on the endpoint before trusting it with real data.
What tools does Crypto Vertex expose?
5 tools as listed by the server itself during the live check, including get_screener, get_coin, get_signals, get_market, get_meta. The full list with parameters is in the Live check section above.
How do I add Crypto Vertex to Claude, Cursor or VS Code?
Copy the config in "Connect this server" into your client's MCP config file (claude_desktop_config.json, ~/.cursor/mcp.json or .vscode/mcp.json), or use the one-click Add to Cursor / Add to VS Code buttons and the one-line commands for Claude Code and Codex; then restart the client.
Browse all Crypto & Web3 →

Add the badge to your site

Show visitors that Crypto Vertex is listed here — it’s also the link we check for a free listing.

Crypto Vertex — listed on Serverdex

HTML — for your website

<a href="https://serverdex.io/server/io-github-taibi56-crypto-vertex?utm_source=badge"><img src="https://serverdex.io/brand/badge.svg" alt="Crypto Vertex — listed on Serverdex" width="123" height="40" loading="lazy"></a>

Recommended. A dofollow link from your own domain is the one that counts for search engines, and it's the link we check for a free listing.

Markdown — for your README

[![Crypto Vertex — listed on Serverdex](https://serverdex.io/brand/badge.svg)](https://serverdex.io/server/io-github-taibi56-crypto-vertex?utm_source=badge)

Nice for visibility, but GitHub marks README links nofollow, so it doesn't pass authority. Use the HTML badge on your site as well.

Add to CursorAdd to VS CodeOpen in Claude Code

Install buttons — for your README

[![Add to Cursor](https://serverdex.io/brand/install-cursor.svg)](https://serverdex.io/install/cursor/io-github-taibi56-crypto-vertex) [![Add to VS Code](https://serverdex.io/brand/install-vscode.svg)](https://serverdex.io/install/vscode/io-github-taibi56-crypto-vertex) [![Open in Claude Code](https://serverdex.io/brand/install-claude-code.svg)](https://serverdex.io/install/claude-code/io-github-taibi56-crypto-vertex)

One click opens Cursor or VS Code with this server's config prefilled; the Claude Code button lands on the one-line command. The links point at Serverdex, so when your config changes the buttons keep working.

Install buttons — HTML for your docs

<a href="https://serverdex.io/install/cursor/io-github-taibi56-crypto-vertex"><img src="https://serverdex.io/brand/install-cursor.svg" alt="Add to Cursor — via Serverdex" width="140" height="28"></a>
<a href="https://serverdex.io/install/vscode/io-github-taibi56-crypto-vertex"><img src="https://serverdex.io/brand/install-vscode.svg" alt="Add to VS Code — via Serverdex" width="147" height="28"></a>
<a href="https://serverdex.io/install/claude-code/io-github-taibi56-crypto-vertex"><img src="https://serverdex.io/brand/install-claude-code.svg" alt="Open in Claude Code — via Serverdex" width="180" height="28"></a>

Same buttons as plain links for a docs page or website.

Prefer a live badge with the score, stars and live check? Score badge (links to a page that explains the number and back to this listing).