Crypto Vertex MCP server
io.github.Taibi56/crypto-vertexTaibi56streamable-httpv1.0.1Scanned
Read-only crypto screener for Binance: 100+ indicators, funding, OI, CHoCH/BOS/CRT, breadth, F&G.
5 tools: 5 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Sign-in required, no OAuth metadata. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Crypto Vertex MCP server can do
The Crypto Vertex MCP server is published by the GitHub account Taibi56. It has 5 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint asks for sign-in.
Last scanned Nov 19, 2026, version 1.0.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
5 tools
Only reads 5Show 5 read-only tools
get_coinEverything Crypto Vertex publishes for one coin: price, performance, volume, trend, funding / open interest (futures), market cap, and per-timeframe indicators, chart patterns, div…No findings
Why it is in this group
- The name "get_coin" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_marketMarket 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)…No findings
Why it is in this group
- The name "get_market" says "get": a word for reading.
Description, as the server wrote it 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).
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_metaDescribes 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…No findings
Why it is in this group
- The name "get_meta" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_screenerScreen every listed Crypto Vertex crypto pair (USDT spot or perpetual futures).No findings
Why it is in this group
- The name "get_screener" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_signalsCurrent 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.No findings
Why it is in this group
- The name "get_signals" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 16, 2026, 14:19 UTC, unchanged since Nov 16, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 401
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- no
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint asks for credentials (HTTP 401) but publishes no RFC 9728 protected resource metadata: no resource_metadata in WWW-Authenticate and no document at /.well-known/oauth-protected-resource.
What this check looks forMatched text
https://www.cryptovertex.net/mcp: initialize answered HTTP 401, without a WWW-Authenticate header
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http crypto-vertex https://www.cryptovertex.net/mcp --header 'Authorization: <your-authorization>'claude mcp add --transport http crypto-vertex https://www.cryptovertex.net/mcp --header 'Authorization: <your-authorization>'Run in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__crypto-vertex__get_screener",
"mcp__crypto-vertex__get_coin",
"mcp__crypto-vertex__get_signals",
"mcp__crypto-vertex__get_market",
"mcp__crypto-vertex__get_meta"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as crypto-vertex. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.Taibi56/crypto-vertex/verify?hash=11318e256f8265609b218bb2f1dcceba73be624331824e40790359317f619b70" | jq -e '.changed == false'Pinned hash 11318e256f82, from Nov 19, 2026, 11:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.Taibi56/crypto-vertex/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.Taibi56/crypto-vertex)Source: MCP Registry · repository. Synced Nov 19, 2026, 11:18 UTC.
Crypto Vertex MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Crypto Vertex MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the Crypto Vertex MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Crypto Vertex MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Crypto Vertex MCP server have?
- 5 tools: 5 read. get_screener, get_coin, get_signals, get_market and get_meta.
Does the Crypto Vertex MCP server need sign-in or OAuth?
- Yes. Its remote endpoint answered 401 without credentials, and no OAuth protected resource metadata was found.
Does the Crypto Vertex MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Crypto Vertex MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.