com.bykaranteli/mcp
REMOTE · MCP.BYKARANTELI.COM · 2 COMPONENTS
Crypto derivatives data: funding, OI, liquidations, options, ETF flows. Free account key required.
Available components
Last scanned (23 hours ago)
Scores higher than 99% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Crypto and Web3
Recent critical change
Authorization (30 Sept 2026). See the changelog before you install this server.
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 Security100
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 13334 tokens (~196/item across 68 items; 68 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 Safety94
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 3 of 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "get_psi_charge" implies "charge" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
- An AI judge read all 68 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 3 Nov 26 0
- Tool “get_liqmap” rewrote its description, which is the text the model reads security
- Server version: 1.1.0 → 1.1.1 functional
- “get_liqmap” reworded the description of “symbol” cosmetic
- 25 Oct 26 0
- Stability: fail → pass ▲ security
- Tool “get_hl_whales” rewrote its description, which is the text the model reads security
- Tool “get_liqmap” rewrote its description, which is the text the model reads security
- Tool “get_new_listings” rewrote its description, which is the text the model reads security
- Tool “get_options_flow” rewrote its description, which is the text the model reads security
- Tool “get_positioning” rewrote its description, which is the text the model reads security
- Tool “get_tokenized_stocks” rewrote its description, which is the text the model reads security
- Tool “get_turkey_premium” rewrote its description, which is the text the model reads security
- Tool “get_venue_markets” rewrote its description, which is the text the model reads security
- Tool “get_correlations” rewrote its description, which is the text the model reads security
- Tool “get_coverage” rewrote its description, which is the text the model reads security
- Tool “get_desk_notes” rewrote its description, which is the text the model reads security
- Tool “get_factor_board” rewrote its description, which is the text the model reads security
- Tool “get_funding_arbitrage” rewrote its description, which is the text the model reads security
- Schema quality: 174 → 194 ▼ functional
- Server version: 1.0.1 → 1.1.0 functional
- “get_tokenized_stocks” added an optional parameter “detail” cosmetic
- “get_funding_arbitrage” added an optional parameter “detail” cosmetic
- “get_hl_whales” added an optional parameter “detail” cosmetic
- “get_new_listings” added an optional parameter “detail” cosmetic
- “get_options_flow” added an optional parameter “detail” cosmetic
- “get_positioning” added an optional parameter “detail” cosmetic
- “get_turkey_premium” added an optional parameter “detail” cosmetic
- “get_venue_markets” added an optional parameter “detail” cosmetic
- “get_correlations” added an optional parameter “detail” cosmetic
- “get_desk_notes” added an optional parameter “detail” cosmetic
- “get_factor_board” added an optional parameter “detail” cosmetic
- “get_liqmap” reworded the description of “detail” cosmetic
- “get_coverage” reworded the description of “detail” cosmetic
- 23 Oct 26 +1
- Stability: pass → fail ▼ security
- Authorization: partial → pass ▲ security
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- MCP protocol version: 2025-11-25 → 2026-07-28 functional
- Server version: 0.36.1 → 1.0.1 functional
- 21 Oct 26 0
- Tool “get_desk_notes” rewrote its description, which is the text the model reads security
- Tool “get_series” rewrote its description, which is the text the model reads security
- Tool “list_alert_recipes” rewrote its description, which is the text the model reads security
- Tool “get_factor_board” rewrote its description, which is the text the model reads security
- Server version: 0.36.0 → 0.36.1 functional
- “get_factor_board” added an optional parameter “limit” cosmetic
- “get_series” reworded the description of “to” cosmetic
- “get_desk_notes” reworded the description of “limit” cosmetic
- 20 Oct 26 0
- Stability: fail → pass ▲ security
- 17 Oct 26 0
- Stability: pass → fail ▼ security
- 15 Oct 26 0
- Server version: 0.35.1 → 0.36.0 functional
- New tool “get_desk_notes” functional
- 12 Oct 26 +12
- Authorization: fail → pass ▲ security
- First check of Authorization: partial security
- Tool “get_liqmap” rewrote its description, which is the text the model reads security
- Tool “get_leverage_tiers” rewrote its description, which is the text the model reads security
- Tool “get_lead_lag” rewrote its description, which is the text the model reads security
- Tool “get_hl_whales” rewrote its description, which is the text the model reads security
- Tool “get_funding_arbitrage” rewrote its description, which is the text the model reads security
- Tool “get_coverage” rewrote its description, which is the text the model reads security
- Tool “get_coinbase_premium” rewrote its description, which is the text the model reads security
- Tool “get_borrow_rates” rewrote its description, which is the text the model reads security
- Tool “get_venue_markets” rewrote its description, which is the text the model reads security
- Tool “create_alert_recipe” rewrote its description, which is the text the model reads security
- Tool “add_watchlist_symbol” rewrote its description, which is the text the model reads security
- Tool “get_withdrawal_status” rewrote its description, which is the text the model reads security
- Tool “list_alert_recipes” rewrote its description, which is the text the model reads security
- Tool “list_watchlists” rewrote its description, which is the text the model reads security
- Tool “remove_watchlist_symbol” rewrote its description, which is the text the model reads security
- Tool “delete_alert_recipe” rewrote its description, which is the text the model reads security
- Tool “get_turkey_premium” rewrote its description, which is the text the model reads security
- Tool “get_tradfi_gaps” rewrote its description, which is the text the model reads security
- Tool “get_tradfi_board” rewrote its description, which is the text the model reads security
- Tool “get_tokenized_stocks” rewrote its description, which is the text the model reads security
- Tool “get_solana_perps” rewrote its description, which is the text the model reads security
- Tool “get_settlements” rewrote its description, which is the text the model reads security
- Tool “get_series” rewrote its description, which is the text the model reads security
- Tool “get_rsi_heatmap” rewrote its description, which is the text the model reads security
- Tool “get_positioning” rewrote its description, which is the text the model reads security
- Tool “get_options_chain” rewrote its description, which is the text the model reads security
- Tool “get_network_health” rewrote its description, which is the text the model reads security
- Tool “get_macro_liquidity” rewrote its description, which is the text the model reads security
- Tool “get_liquidations” rewrote its description, which is the text the model reads security
- Schema quality: 149 → 169 ▼ functional
- Server version: 0.34.3 → 0.35.1 functional
- “get_leverage_tiers” added an optional parameter “limit” cosmetic
- “get_lead_lag” added an optional parameter “days” cosmetic
- “get_hl_whales” added an optional parameter “limit” cosmetic
- “get_funding_arbitrage” added an optional parameter “symbol” cosmetic
- “get_coverage” added an optional parameter “detail” cosmetic
- “get_coinbase_premium” added an optional parameter “days” cosmetic
- “get_borrow_rates” added an optional parameter “hours” cosmetic
- “get_borrow_rates” added an optional parameter “asset” cosmetic
- “get_venue_markets” added an optional parameter “limit” cosmetic
- “get_withdrawal_status” added an optional parameter “limit” cosmetic
- “get_turkey_premium” added an optional parameter “daily_days” cosmetic
- “get_tradfi_gaps” added an optional parameter “limit” cosmetic
- “get_tradfi_board” added an optional parameter “limit” cosmetic
- “get_solana_perps” added an optional parameter “limit” cosmetic
- “get_settlements” added an optional parameter “limit” cosmetic
- “get_settlements” added an optional parameter “base” cosmetic
- “get_rsi_heatmap” added an optional parameter “order” cosmetic
- “get_rsi_heatmap” added an optional parameter “limit” cosmetic
- “get_positioning” added an optional parameter “limit” cosmetic
- “get_positioning” added an optional parameter “cvd_points” cosmetic
- “get_network_health” added an optional parameter “series” cosmetic
- “get_macro_liquidity” added an optional parameter “series” cosmetic
- “get_liquidations” added an optional parameter “limit” cosmetic
- “get_liqmap” added an optional parameter “detail” cosmetic
- “get_macro_liquidity” reworded the description of “days” cosmetic
- “get_tokenized_stocks” reworded the description of “top” cosmetic
- “get_series” reworded the description of “limit” cosmetic
- “get_options_chain” reworded the description of “strikes” cosmetic
- “get_network_health” reworded the description of “days” cosmetic
- “get_liqmap” reworded the description of “timeframe” cosmetic
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 4 Nov 2026 · Probed https://mcp.bykaranteli.com/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=bykaranteli.com | CN=YE1,O=Let's Encrypt,C=US | 18 Oct 2026 | 16 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5b4b561f89855c96ae15e16e34d7a9a8b83 |
| SANs: *.bykaranteli.com, bykaranteli.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.bykaranteli.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| bykaranteli.com. | present | 2371 | 13 | Verified |
| mcp.bykaranteli.com. | Verified address RRset verified with the apex keys |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://mcp.bykaranteli.com/.well-known/oauth-protected-resource", scope="mcp:read"
Bearer resource_metadata="https://mcp.bykaranteli.com/.well-known/oauth-protected-resource", scope="mcp:read" | Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://www.googletagmanager.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https://*.google-analytics.com https://stats.g.doubleclick.net https://www.googletagmanager.com https://www.google.com; font-src 'self' data:; connect-src 'self' wss://bykaranteli.com https://*.google-analytics.com https://*.analytics.google.com https://stats.g.doubleclick.net https://www.googletagmanager.com https://www.google.com https://api.cdp.coinbase.com https://secure-wallet.cdp.coinbase.com https://cca-lite.coinbase.com https://api.devnet.solana.com https://solana-rpc.publicnode.com https://mainnet.base.org https://base-rpc.publicnode.com https://base.easscan.org https://sepolia.base.org https://base-sepolia.easscan.org; frame-src 'self' https://player.vimeo.com https://www.youtube-nocookie.com https://secure-wallet.cdp.coinbase.com; worker-src 'self'; manifest-src 'self'; media-src 'self'; object-src 'none'; base-uri 'self'; form-action 'self'; frame-anc |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Protected resource metadata
| Document | https://mcp.bykaranteli.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.bykaranteli.com |
| Authorisation server | https://bykaranteli.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.bykaranteli.com/ | Verified | 200 | |
| http (plaintext) | http://mcp.bykaranteli.com/ | HTTPS enforced | 301 | https://mcp.bykaranteli.com/ |
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 →
add_tracked_address Follow a Hyperliquid address for position alerts (writes to your account) ~134
Call this when the user asks to follow, track or get alerts for a Hyperliquid address (0x followed by 40 hex characters). Every later position change of the address (opened, closed, increased, reduced, flipped) reaches the user's alert channels; the first sight is the baseline and sends nothing. Counted against the plan's address limit; the route answers terminal_required or limit_reached when it cannot add.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | string, 0x followed by 40 hex characters |
| label | string | – | string, optional name for the address, up to 40 characters |
No output schema declared.
No examples provided.
add_watchlist_symbol Add a symbol to your watchlist (writes to your account) ~144
Call this when the user asks to watch, follow or add a coin to their watchlist. Adds the symbol to the list named by watchlist_id, else to the default list (or the only list the account has); a symbol already on the list stays once. Returns the list's symbols after the change. Writes are rate limited per connection (sign-in or key) and each one is recorded on the account.
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | yes | string, a Binance USDT-M perp or coin, e.g. SOLUSDT or SOL |
| watchlist_id | string | – | string, optional list id from list_watchlists (default: the default list) |
No output schema declared.
No examples provided.
create_alert_recipe Create an alert recipe (writes to your account) ~495
Call this when the user asks to be alerted when a metric crosses a threshold and has agreed to the exact condition (parse_alert_text turns their words into one). Saves an alert recipe on the account: it fires when every condition holds, delivers by Telegram first with email as fallback unless channels says otherwise, and waits cooldown_hours before it fires again for the same symbol. field is one of: mark_price, pressure_score, funding_rate_pct, oi24h_pct, basis_pct, price_change_24h_pct, liq_cluster_distance_pct, usdt_peg_min_usd, usdc_peg_min_usd, liq_1h_usd, rsi_4h, ls_ratio_global, book_imbalance_2pct_pct, withdrawal_paused_venues, max_leverage_min, borrow_apr_pct, hl_whale_long_share_pct; op is one of >= > <= < ==; percent fields take percent values (0.05 means 0.05%). Pass field, op and threshold for one condition, or conditions for up to 6. scope: watchlist (default), any, or symbols with symbols. The plan sets how many recipes an account keeps; past it the tool answers with the limit. Writes are rate limited per connection (sign-in or key) and each one is recorded on the account.
| Name | Type | Req | Description |
|---|---|---|---|
| channels | array | – | array, optional delivery channels: telegram | email | push | webhook; empty means Telegram first, email as fallback |
| conditions | array | – | array, optional up to 6 conditions {field, op, value}, all must hold (instead of field, op, threshold) |
| cooldown_hours | number | – | number, optional 1..168 hours before it fires again (default 24) |
| field | string | – | string, one condition's metric, e.g. funding_rate_pct |
| name | string | – | string, optional name; default describes the condition |
| op | string | – | string, one condition's comparison: >= | > | <= | < | == |
| scope | string | – | string, optional: watchlist (default), any, symbols |
| symbols | array | – | array, optional up to 20 symbols, e.g. ["BTCUSDT", "ETH"]; implies scope symbols |
| threshold | number | – | number, one condition's threshold, e.g. 0.05 |
No output schema declared.
No examples provided.
delete_alert_recipe Delete one of your alert recipes (writes to your account) ~94
Call this when the user asks to remove an alert. Deletes the alert recipe with this id from the account (list_alert_recipes shows the ids); an id that is not one of the account's recipes changes nothing and says so. Writes are rate limited per connection (sign-in or key) and each one is recorded on the account.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | string, the recipe id from list_alert_recipes |
No output schema declared.
No examples provided.
get_altseason Altcoin Season Index (live + recorded history) ~88
Call this when the user asks whether it is altseason, how altcoins are doing against Bitcoin, or about market rotation. Returns the live Altcoin Season Index (share of the top 50 Binance perpetual altcoins beating BTC over the trailing 90 days; >=75 altseason, <=25 bitcoin season), the strongest and weakest large alts, and the recorded daily history (never reconstructed).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_borrow_rates Margin borrow rates per venue: the cost of leverage, hourly ~192
Call this when the user asks what it costs to borrow USDT, USDC, BTC, ETH or a major alt on an exchange, which venue has the cheapest borrow, whether stablecoin borrow cost is spiking, or what the carry of a basis trade is on a venue (funding minus borrow). Returns the latest annualised rate per venue and asset, 30 days of hourly series for the stablecoins and majors, and the carry table. Recorded hourly by ByKaranteli (Binance and OKX today). The series hold the last 24 hours unless hours (up to 720) or asset is passed.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | – | Optional. One asset, e.g. USDT: its rates, carry and full 30-day series. |
| hours | integer | – | Optional. Hours of hourly series to return (default 24, or the full 720 with asset). |
No output schema declared.
No examples provided.
get_coinbase_premium Coinbase Premium (US demand gauge) + carry yield ~143
Call this when the user asks whether US investors are buying or selling Bitcoin or Ethereum, about the Coinbase Premium, or what the cash-and-carry basis trade pays. Returns the latest daily premium in percent, 7-day average, same-sign streak, the last 30 days, and annualized quarterly carry yields. History since 2017; positive premium = US buying pressure. The kimchi and Turkey premium daily rows cover the last 7 days; pass days (up to 90) for more.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Optional. Days of kimchi and Turkey premium daily rows, newest first (default 7, up to 90). |
No output schema declared.
No examples provided.
get_correlations Crypto correlation matrix ~161
Call this when the user asks how correlated two coins are, for decorrelated pairs, or how tightly alts track BTC. Returns the 30-day rolling Pearson correlation matrix of daily returns across the top perpetuals. Pass detail "compact" for a shorter page or "full" for the whole answer.
| Name | Type | Req | Description |
|---|---|---|---|
| detail | – | – | Optional. "compact": a shorter page than the default (fewer rows, newest points kept, rounded figures, long text cut, grids left out; every cut named in trimmed). "full" or true: the whole route answ… |
No output schema declared.
No examples provided.
get_cot_positioning CME futures positioning (weekly COT report, BTC + ETH) ~96
Call this when the user asks how hedge funds or institutions are positioned in Bitcoin or Ethereum, or about the CFTC Commitments of Traders report. Returns net positions in contracts, week-over-week changes, open interest and notable extremes/streaks, from official CFTC data updated every Friday. Note: a large share of hedge fund shorts is the market-neutral basis trade, so the weekly change carries more signal than the level.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_coverage Coverage registry: which venues and data types we collect, how, and how fresh ~262
Call this when the user asks which exchanges sit behind a ByKaranteli number, whether a feed is complete or sampled, since when a venue is collected, or how fresh the data is. Returns the live coverage registry: liquidation feeds per venue with kind and last record, snapshot feeds per venue and market, funding arbitrage legs, positioning sources, whale tape, spot minutes and the Hyperliquid whale scan with freshness. snapshots[].country is the jurisdiction only when the venue states one; it is null for most venues, so do not read null as unknown risk. By default the first 30 snapshot feeds, English notes only and no per-venue matrix cells; pass detail "full" for the full registry. Pass detail "compact" for a shorter page or "full" for the whole answer.
| Name | Type | Req | Description |
|---|---|---|---|
| detail | – | – | Optional. "compact": a shorter page than the default (fewer rows, newest points kept, rounded figures, long text cut, grids left out; every cut named in trimmed). "full" or true: the whole route answ… |
No output schema declared.
No examples provided.
get_cycle_indicators Bitcoin cycle indicators: Pi Cycle, Mayer, 200W MA, Puell, S2F ~151
Call this when the user asks whether Bitcoin is near a cycle top or bottom by the classic indicators, about the Pi Cycle Top, Mayer Multiple, 200-week moving average, 2-year MA multiplier, golden ratio multiple, profitable days, stock-to-flow, Puell Multiple or Bitfinex margin positioning. Returns the latest readings, the Pi Cycle cross dates on record, and optionally the daily series (recomputed nightly from a first-party close record since 2012). Levels, not forecasts.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Window in days for the series (default 730) |
| include_points | boolean | – | Include the daily series (large). Default false: latest values and cross dates only. |
No output schema declared.
No examples provided.
get_data_proof BYK Data Layer: on-chain proof that a ByKaranteli number was sealed, signed and anchored on Solana and Base ~315
Call this when the user asks whether ByKaranteli data can be verified or was changed afterwards, about the BYK Data Layer, on-chain proofs of market data, or wants the proof behind one sealed number. Every 5 minutes a catalog of derived feeds (funding composite, aggregate open interest, liquidations, depth within 2%, pressure scores, Kimchi and Turkey premiums) is sealed into one Merkle root, signed and written to Solana mainnet, and attested on Base once a day. With no arguments returns the stream overview: network, epochs and records sealed, final anchors and the newest epochs with explorer links. Pass feed and asset for one record's proof (value, 104-byte leaf, Merkle path, signed manifest, signature, Solana and Base anchors) at the newest epoch or at sequence; sequence alone for one epoch; catalog for the feed list. result ANCHORED means ByKaranteli signed it and an anchor is final; the protocol verdict is reached from the chains alone at https://bykaranteli.com/proof.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | – | Asset of the feed: BTC, ETH, SOL, XRP, DOGE, BNB, USDT or ALL |
| catalog | boolean | – | true: list every sealed feed with its unit and methodology |
| feed | string | – | Feed id from the catalog, e.g. BYK.FUNDING.COMPOSITE.B |
| sequence | integer | – | Epoch sequence; omit for the newest |
No output schema declared.
No examples provided.
get_desk_notes Desk notes: short dated observations the ByKaranteli desk wrote from its own recorded derivatives data ~468
Call this when the user asks what happened in crypto derivatives today or on a date, what the desk observed, what moved in funding, open interest, liquidations, options, ETF flows or exchange premiums, or wants a dated, quotable sentence with its number and time. Returns the desk's notes newest first: each is one observation written by the desk writer (an AI model) from the platform's own recorded data and checked against it before publishing, with its publish time in UTC, the card's data time, the desk's 0 to 10 news value, the board it read from, the coins it names and its permanent URL. Information about the data, never advice. Default the newest 25 notes of the last 24 hours (count says how many came back; limit up to 100 for more); pass day for one UTC day, since for a window up to 7 days back (50 notes unless limit says otherwise), type for one card type (funding-arb, liqmap-btc, event-liq-burst, ...), lang for zh, ru or ko text. Pass detail "compact" for a shorter page or "full" for the whole answer.
| Name | Type | Req | Description |
|---|---|---|---|
| day | string | – | One UTC day, YYYY-MM-DD |
| detail | – | – | Optional. "compact": a shorter page than the default (fewer rows, newest points kept, rounded figures, long text cut, grids left out; every cut named in trimmed). "full" or true: the whole route answ… |
| lang | string | – | Text language (default en); a note without that translation comes back in English |
| limit | integer | – | Notes to return, 1..100 (default 25 for the last 24 hours, 50 with day or since) |
| since | string | – | ISO time; notes published at or after it, at most 7 days back (ignored with day) |
| type | string | – | One card type, e.g. funding-arb, liqmap-btc, event-liq-burst |
No output schema declared.
No examples provided.
get_etf_flows US spot Bitcoin, Ethereum, Solana and XRP ETF daily flows ~179
Call this when the user asks about Bitcoin, Ethereum, Solana or XRP spot ETF flows: daily net inflows or outflows, cumulative flow since launch, or total net assets of the US spot ETFs (IBIT, FBTC, ETHA, XRPC and the rest). Returns one row per finalized US trading day and asset with net inflow, total net assets, cumulative inflow since launch and value traded, all in USD. History by asset: BTC and ETH since 2025-05-20, SOL since 2025-10-28, XRP since 2026-09-08.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | – | Filter to one asset (BTC, ETH, SOL or XRP). Omit for all. |
| days | integer | – | How many most recent trading days to return (default 10). |
No output schema declared.
No examples provided.
get_factor_board Factor board: what followed days like today across recorded metrics ~246
Call this when the user asks which indicators currently sit in an unusual band, whether a metric's current level historically preceded BTC moves, or for a cross-metric conditional overview. Returns every recorded metric in its historical band with the median 7-day BTC move that followed versus the base rate, with an n >= 30 gate; distributions, not forecasts. Without limit the first 40 rows in the board's own order (rows_total counts every row, trimmed names the cut); pass limit up to 400 for the whole board. Pass detail "compact" for a shorter page or "full" for the whole answer.
| Name | Type | Req | Description |
|---|---|---|---|
| detail | – | – | Optional. "compact": a shorter page than the default (fewer rows, newest points kept, rounded figures, long text cut, grids left out; every cut named in trimmed). "full" or true: the whole route answ… |
| limit | integer | – | Optional. Rows to return, 1..400 (default 40) |
No output schema declared.
No examples provided.
get_fee_table Trading fee schedules per venue, base tier maker and taker ~95
Call this when the user asks what an exchange charges to trade, how maker and taker fees compare across venues, whether a venue changed its fees, or what a round trip costs on a given notional. Returns base tier maker and taker per venue and market type (median across pairs where the venue prices per pair) and the fee change log, read daily by ByKaranteli from each venue's own fee endpoint.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_flow_toxicity Order-flow toxicity (VPIN) for BTC, ETH, SOL perps ~92
Call this when the user asks whether informed or toxic order flow is building, about VPIN, or whether market makers are under pressure in Bitcoin, Ethereum or Solana. Returns the current VPIN (0 = balanced, 1 = fully one-sided), its 90-day percentile, the danger threshold and the 24h average. Elevated readings historically precede volatility; VPIN says nothing about direction.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_fomc_impact Measured FOMC impact on Bitcoin ~93
Call this when the user asks what Bitcoin does on Fed days, how FOMC statements move crypto, or when the next FOMC meeting is. Returns per-statement 5/30/60-minute BTC reactions measured from a minute-resolution record, the average move versus a normal half hour, the up/down split (near a coin flip), and the next meeting date. Description, not prediction.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_funding_arbitrage Cross-exchange funding arbitrage opportunities ~263
Call this when the user asks about funding arbitrage, funding rate differences between exchanges, or delta-neutral carry trades. Compares funding across every venue on the board, from Binance, OKX and Bybit to Hyperliquid, dYdX and the smaller perp venues fed by the venue snapshot, for 12 major perps and returns the best long/short venue per symbol with gross and net annualized APR (net of taker fees and weekly rebalance cost). Each row lists its first 5 venue legs; pass symbol for every leg of one perp. Pass detail "compact" for a shorter page or "full" for the whole answer.
| Name | Type | Req | Description |
|---|---|---|---|
| detail | – | – | Optional. "compact": a shorter page than the default (fewer rows, newest points kept, rounded figures, long text cut, grids left out; every cut named in trimmed). "full" or true: the whole route answ… |
| symbol | string | – | Optional. One perp, e.g. BTCUSDT or BTC: its row with every venue leg. |
No output schema declared.
No examples provided.
get_funding_heatmap Funding rates across the ~30 most traded Binance perps ~149
Call this when the user asks for the full current funding table across the ~30 most traded Binance perps (28-30 rows; contracts without a live funding print are skipped), or the funding rate of one specific coin. For a pre-ranked top-10 of the most extreme funding rates, use get_top_movers instead. Returns per-symbol funding rate (per settlement interval), 24h open interest change and 24h price change for the most traded Binance USDT-M perpetuals. Positive funding means longs pay shorts.
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | – | Optional. Filter to one symbol, e.g. BTCUSDT or just BTC. Omit to get all 30 rows. |
No output schema declared.
No examples provided.
get_hl_positions Hyperliquid tracked positions: the liquidation price map of the largest accounts per coin, against the LiqMap model ~148
Call this when the user asks where Hyperliquid whales would be liquidated, how much tracked notional sits at each price, how the largest accounts lean on a coin, or how their liquidation prices compare with the LiqMap model. The universe is the largest accounts by equity on Hyperliquid's public leaderboard, scanned every five minutes; the levels are their own liquidation prices bucketed around the mark. hours returns the hourly archive of level totals.
| Name | Type | Req | Description |
|---|---|---|---|
| coin | string | – | Coin as Hyperliquid names it, e.g. BTC, ETH, SOL (default BTC) |
| hours | integer | – | Hours of archive to return, 1..720 (default 24) |
No output schema declared.
No examples provided.
get_hl_whales Hyperliquid whale tracker: top-300 accounts, long vs short, positions, changes ~277
Call this when the user asks what Hyperliquid whales are doing, whether the biggest Hyperliquid accounts are net long or short a coin, for the largest open positions with liquidation prices, or what large accounts just opened, closed or flipped. Returns the live board of the 300 largest accounts by equity (scanned every 5 minutes, addresses only) and with events the last 200 position changes. Without coin, the 30 largest coins and positions; pass coin, or limit (up to 200) for more. Pass detail "compact" for a shorter page or "full" for the whole answer.
| Name | Type | Req | Description |
|---|---|---|---|
| coin | string | – | One coin, e.g. BTC |
| detail | – | – | Optional. "compact": a shorter page than the default (fewer rows, newest points kept, rounded figures, long text cut, grids left out; every cut named in trimmed). "full" or true: the whole route answ… |
| events | boolean | – | Include the last 200 position change events |
| limit | integer | – | Optional. Coins and positions without coin, largest first (default 30). |
No output schema declared.
No examples provided.
get_insurance_funds Exchange insurance funds: size, 24h and 7d change, fund against open interest, daily history ~226
Call this when the user asks how big an exchange's insurance fund is, whether a fund is shrinking or was used after a crash, how much exchanges hold to absorb bankrupt liquidations, or how a fund compares with the venue's open interest. Returns the latest hourly reading per covered venue (every exchange the insurance fund board lists): the fund in USD (OKX's own published total, the sum of priced pools elsewhere), per asset, 24h and 7d change, the fund as a percent of the venue's perpetual open interest on the coins ByKaranteli tracks, and daily closes per venue. Set pools to include every pool row (the contracts it covers, asset, balance, USD). A fund is a balance the venue reports, not an audit of its reserves.
| Name | Type | Req | Description |
|---|---|---|---|
| history_days | integer | – | Days of daily closes (default 30, max 366). |
| pools | boolean | – | Include every pool row (large for Binance and Bybit). Default false. |
| venue | string | – | One venue; omit for every covered venue. |
No output schema declared.
No examples provided.
get_iv_surface Options implied-volatility surface and 25-delta skew ~99
Call this when the user asks about implied volatility by strike or expiry, skew, put versus call IV, term structure of IV, or whether downside protection is expensive. Returns the IV surface (expiry x moneyness), per-expiry ATM / 25-delta put and call IV, skew and butterfly, and the constant-30d history, from the daily Deribit chain.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | BTC or ETH, default BTC |
No output schema declared.
No examples provided.
get_jupiter_perps Jupiter Perps (Solana): exact long/short OI, utilization, borrow rates, weekly top traders ~127
Call this when the user asks about Jupiter perpetuals on Solana: long versus short open interest per market (SOL, ETH, BTC) read from the on-chain custody state, pool utilization and hourly borrow rates, JLP pool AUM and APR, 24h volume, or the week's top traders by realized PnL. Pass base and history_days for the hourly OI history.
| Name | Type | Req | Description |
|---|---|---|---|
| base | string | – | Market base: SOL, ETH or BTC |
| history_days | integer | – | Include hourly OI history for the base, 1..30 days |
No output schema declared.
No examples provided.
get_lead_lag Venue lead-lag: who moves first (Coinbase, Kraken, Binance) ~120
Call this when the user asks which exchange leads price discovery or whether spot or perp moves first. Returns per-pair daily cross-correlations of one-minute returns at lags -3..+3 and the lead asymmetry, with the share of days each venue led. Each pair's daily rows cover the last 7 days (its summary covers the whole window); pass days (up to 30) for more.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Optional. Daily rows per pair, newest kept (default 7, up to 30). |
No output schema declared.
No examples provided.
get_leverage_tiers Leverage tiers: max leverage and maintenance margin per perpetual on every venue ~213
Call this when the user asks how much leverage an exchange allows on a coin, what the maintenance margin or risk limit ladder is, which venue offers the highest leverage for a symbol, or whether an exchange recently cut leverage. Returns the current ladder per venue (tier, notional floor and cap, max leverage, maintenance margin rate) recorded daily by ByKaranteli, plus a change log. Pass symbol for one base asset (e.g. SOL) and venue for one exchange (bybit, okx, gate, htx, bitget, mexc). Without symbol, the first 30 rows of each list and the first 5 tiers of each ladder; pass symbol for every tier, or limit (up to 300).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Optional. Rows per list without symbol (default 30). |
| symbol | string | – | string, optional base asset, e.g. BTC |
| venue | string | – | string, optional venue id, e.g. bybit |
No output schema declared.
No examples provided.
get_liqmap LiqMap: estimated liquidation clusters with real prints overlaid ~411
Call this when the user asks where liquidation clusters or liquidity pools sit for a perpetual, where leveraged longs/shorts would get liquidated, or for a liquidation heatmap reading. Covers the crypto perps and the stock and commodity perps: gold is XAU, silver XAG, WTI crude oil CL, Brent BZ, natural gas NATGAS, copper COPPER, platinum XPT, palladium XPD, stocks their ticker (TSLA, NVDA). Returns the LiqMap snapshot for one symbol: modeled liquidation levels by price, zone aggregates and real liquidation prints from every liquidation venue ByKaranteli counts (listed on bykaranteli.com/coverage). On the Free plan the 24h view; on Builder and higher plans every timeframe from 1h to 30d. By default the 30 real levels nearest the price and the 30 largest real prints; pass detail "full" for all of them. Pass detail "compact" for a shorter page or "full" for the whole answer.
| Name | Type | Req | Description |
|---|---|---|---|
| detail | – | – | Optional. "compact": a shorter page than the default (fewer rows, newest points kept, rounded figures, long text cut, grids left out; every cut named in trimmed). "full" or true: the whole route answ… |
| symbol | string | – | Symbol like BTCUSDT (bare BTC accepted). Commodity perps use the contract code: XAU gold, XAG silver, CL WTI crude, BZ Brent, NATGAS, COPPER, XPT platinum, XPD palladium; stocks their ticker (TSLA).… |
| timeframe | string | – | Model window. Default 24h, the only one on the Free plan; Builder and higher plans get every window. |
No output schema declared.
No examples provided.
get_liquidation_cascades Auto-detected liquidation cascades (forensic case file) ~84
Call this when the user asks what caused a recent crash or flush, about liquidation cascades, or who got liquidated. Returns auto-detected cascade incidents: when, total notional flushed, long/short split, which coins led, and BTC's move during the window. Totals are an honestly-labeled lower bound from a real liquidation tape.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_liquidation_leaderboard Largest single liquidations and a 30-day session heatmap (counted venue feeds) ~218
Call this when the user asks for the biggest liquidation today or this week, who got liquidated for the most, the largest single liquidation print, or when in the day or week liquidations cluster (Asia, Europe or US hours, weekday by UTC hour). Returns the largest single liquidation prints of the last 24h, 7d or 30d (rank, symbol, venue, side where SELL means a long was liquidated, price, quantity, notional, millisecond time) recorded from the counted venues' public feeds, plus a 30-day weekday by UTC hour heatmap with hour, weekday and session totals. Binance publishes at most one print per second per symbol, so its rows are a floor.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Days folded into the session heatmap (default 30). |
| limit | integer | – | Rows to return (default 25, max 100). |
| window | string | – | Ranking window: 24h (default), 7d or 30d. |
No output schema declared.
No examples provided.
get_liquidations Crypto liquidations: daily long/short totals per symbol and exchange ~226
Call this when the user asks how much was liquidated in crypto futures, whether longs or shorts got flushed, or for liquidation history. Returns daily long and short liquidation totals in USD per symbol and exchange, recorded from ByKaranteli's own stream collectors on every liquidation venue it counts, listed on bykaranteli.com/coverage (recorded events, a floor, not estimates). One row per finalized UTC day, symbol and exchange; history begins 2026-07-30 and grows daily. Without symbol, rows holds the first 30 rows (newest day, largest first) while summary covers every matching row; pass symbol or limit (up to 400) for more rows.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | How many most recent days to return (default 7). |
| limit | integer | – | Optional. Rows to return, newest day first and largest first within a day (default 30 without symbol, 400 with one). |
| symbol | string | – | Optional symbol filter like BTCUSDT or ETHUSDT. Omit for all symbols. |
No output schema declared.
No examples provided.
get_macro_liquidity Macro liquidity: Fed funds, 10y, balance sheet, RRP, stablecoin supply ~140
Call this when the user asks about macro liquidity, the Fed balance sheet, reverse repo, rates or stablecoin supply in relation to crypto. Returns the recorded daily series and latest values. Without days, each series holds its newest 7 points; pass days for the daily series, and series for one key over a long window.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Window in days, 30-4000; the route clamps to that range. Omit for the newest 7 points of each series. |
| series | string | – | Optional. One series key from the answer's series field, e.g. fred_walcl_busd. |
No output schema declared.
No examples provided.
get_market_indices Crypto market indices (Fear & Greed, BTC dominance, euphoria) ~59
Call this when the user asks about overall crypto market sentiment or macro state: the Fear & Greed index (today and yesterday), Bitcoin dominance percentage, total market cap, or the Retail Euphoria composite. Live values refreshed about every 30 minutes.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_market_profile Market Profile: daily TPO profile of a perpetual, point of control, value area, initial balance, naked POCs ~183
Call this when the user asks about a perpetual's Market Profile, TPO profile, point of control (POC), value area (VAH, VAL), initial balance or naked (untested) points of control. Returns one row per closed UTC day from ByKaranteli's own one-minute bars of the Binance USDT-M perpetual (30-minute TPO periods, buckets of 0.05% of the day's open, 70% value area, first-hour initial balance, volume point of control), the naked points of control of the last 60 recorded days and the latest day's profile per price bucket. Symbols without recorded minute bars return no_profile.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Closed UTC days, newest first, 1..30 (default 7) |
| symbol | string | – | Ticker such as BTC or BTCUSDT (default BTC) |
No output schema declared.
No examples provided.
get_metric_context Historical context for any recorded metric (conditional distribution) ~228
Call this when the user asks whether a metric's current reading is high or low, or what happened after similar readings. Buckets today's value against the metric's own recorded daily history and returns the median forward BTC return and up-share per bucket at +1/+3/+7 days, with the all-days base rate alongside. Honesty rules: buckets under 30 days are suppressed, and most metrics do NOT separate from the base rate; the interpretation says so plainly. History, not a forecast. Metrics include coinbase_premium_pct, kraken_btc_premium_pct, dvol_btc, fear_greed, funding_btc_daily_pct, etf_btc_net_flow_usd, vpin_btc, altseason_index, stablecoin_total_mcap_busd, fred_dff, fred_dgs10, fred_walcl_busd, fred_rrp_busd and the btc_* network series.
| Name | Type | Req | Description |
|---|---|---|---|
| metric | string | yes | Metric key, e.g. coinbase_premium_pct, fear_greed, altseason_index, stablecoin_total_mcap_busd. |
No output schema declared.
No examples provided.
get_network_health Bitcoin network health from our own node ~150
Call this when the user asks about Bitcoin hashrate, difficulty or block fees (our node runs blocksonly, so there is no mempool series). Returns the recorded daily series and latest values measured on ByKaranteli's own node. Without days, each series holds its newest 7 points; pass days for the daily series, and series for one key over a long window.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Window in days, 30-4000; the route clamps to that range. Omit for the newest 7 points of each series. |
| series | string | – | Optional. One series key from the answer's series field, e.g. btc_hashrate_ehs. |
No output schema declared.
No examples provided.
get_new_listings New and delisted perpetual contracts ~193
Call this when the user asks what new perpetuals were listed, which exchange listed a coin first, or about delistings. Returns listings and delistings across every exchange the hourly scan covers. Pass detail "compact" for a shorter page or "full" for the whole answer.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Window in days, 1-30 (default 30). Longer listing history is the listings dataset at bykaranteli.com/data. |
| detail | – | – | Optional. "compact": a shorter page than the default (fewer rows, newest points kept, rounded figures, long text cut, grids left out; every cut named in trimmed). "full" or true: the whole route answ… |
No output schema declared.
No examples provided.
get_open_interest Intraday open interest and leverage regimes (10 major perps) ~82
Call this when the user asks whether leverage is entering or leaving the market, about open interest changes, or whether longs or shorts are building in a major coin. Returns 5-minute-resolution OI with 24h OI and price deltas and a four-regime read per symbol: longs building, shorts building, long squeeze, short squeeze, or quiet.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_options_chain Options chain hour by hour: open interest and IV per expiry and strike, the change over 1h and 24h, the ATM IV path ~186
Call this when the user asks how the BTC or ETH option chain moved today or over the last day: open interest and mark IV per expiry and strike from ByKaranteli's own hourly capture of every listed venue, the change over the last hour and the last 24 hours, and the front expiry's ATM IV hour by hour. The Free plan lists the largest strikes; Builder and higher plans list every strike. Recorded from 2026-09-30, so the first days carry a short history.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | – | BTC or ETH (default BTC) |
| expiry | string | – | Expiry as DDMONYY, e.g. 31OCT26 (default: every expiry) |
| strikes | string | – | top (largest strikes) or all (Builder and higher plans) |
| venue | string | – | One venue or all (default all) |
No output schema declared.
No examples provided.
get_options_flow Options tape: biggest prints and premium flow (BTC + ETH) ~222
Call this when the user asks what big options players are buying, about block trades, or whether call or put premium dominates today. Returns 24h call vs put premium bought (net of the sold legs of the same multi-leg block or combo, so a spread counts its net premium), the block-trade share, the multi-leg structure count, and the largest prints of the last 48 hours with strikes, premium, IV, structure id and venue (Deribit or OKX). Updated every 15 minutes. Pass detail "compact" for a shorter page or "full" for the whole answer.
| Name | Type | Req | Description |
|---|---|---|---|
| detail | – | – | Optional. "compact": a shorter page than the default (fewer rows, newest points kept, rounded figures, long text cut, grids left out; every cut named in trimmed). "full" or true: the whole route answ… |
No output schema declared.
No examples provided.
get_options_snapshot Options walls, gamma exposure and DVOL (BTC + ETH) ~266
Call this when the user asks where the big options bets sit, about call/put walls, gamma exposure (GEX), the zero-gamma level, implied volatility (DVOL) or the IV term structure for Bitcoin or Ethereum, across options venues or on one venue. Daily snapshot of the listed option chains of every options venue we record, summed by default or one venue with venue: the call wall (largest call open interest above spot) and put wall (largest put open interest below spot), the largest bars on the whole axis, top strikes by open interest, put/call ratio, dealer hedging map, ATM IV by expiry (calls and puts interpolated at the money, iv_source names the venue whose quotes price the chain), each venue's open interest (venues_included), and per expiry the open interest by side, the max pain strike (where the open contracts as a group pay out the least at settlement, not a price target) and the one-sigma implied move the ATM IV prices (expiries). DVOL is Deribit's index whatever the venue.
| Name | Type | Req | Description |
|---|---|---|---|
| venue | string | – | all (default) sums every options venue; or one venue id: deribit, bybit, binance, okx or delta (Delta Exchange India). |
No output schema declared.
No examples provided.
get_orderbook_depth Spot order book depth: walls and 2% depth from every spot venue on the coverage page ~212
Call this when the user asks where the bid or ask walls are, how deep the spot order book is, whether buyers or sellers have more resting orders near price, or for an order book heatmap. Returns the books of every spot venue with a public book that the coverage page lists, binned into 0.1% buckets within 20% of mid (USD notional), the largest walls with venue split, 2% depth and book reach per venue, and optionally the summed 5-minute history; coins: BTC, ETH, SOL, XRP, DOGE, ADA, LINK, AVAX, LTC, BNB. Books whose size is not corroborated are recorded and returned per venue with in_aggregate false (listed in held_out) but not summed into the walls, 2% depth or history.
| Name | Type | Req | Description |
|---|---|---|---|
| hours | integer | – | Include the summed 5-minute history for this many hours |
| symbol | string | – | One coin, e.g. BTC (default BTC) |
No output schema declared.
No examples provided.
get_positioning Positioning: long/short ratios, taker buy/sell and CVD across exchanges ~359
Call this when the user asks about the long/short ratio, whether retail or top traders are net long or short, the taker buy/sell ratio, or CVD (cumulative volume delta) for a perpetual. Returns exchange-published statistics for the 30 most traded Binance USDT perps on every perpetual venue the positioning board records (Binance global and top-trader ratios, Bybit share long, OKX ratios and taker volume, Gate account and top-trader ratios, HTX elite ratios, Bitget account and position ratios) and CVD series for BTC, ETH and SOL; refreshed every 15 minutes. Without symbol, the 10 most traded perps and the newest 24 points of each CVD series; pass symbol, limit or cvd_points for more. Pass detail "compact" for a shorter page or "full" for the whole answer.
| Name | Type | Req | Description |
|---|---|---|---|
| cvd_points | integer | – | Optional. Newest points per CVD series (1h and 5m); default 24 without symbol, every point with one. |
| detail | – | – | Optional. "compact": a shorter page than the default (fewer rows, newest points kept, rounded figures, long text cut, grids left out; every cut named in trimmed). "full" or true: the whole route answ… |
| limit | integer | – | Optional. Perps without symbol, most traded first (default 10, up to 30). |
| symbol | string | – | One Binance symbol, e.g. BTCUSDT |
No output schema declared.
No examples provided.
get_pressure_scores Derivatives pressure scores (funding + OI + basis composite) ~160
Call this when the user asks which coins are crowded or over-leveraged, or asks for the pressure/derivatives-stress score of specific coins. For a quick top-10 ranking of the highest-stress coins right now, use get_top_movers instead. Each symbol gets a 0-100 composite score built from funding rate, 1h/4h/24h open interest deltas and basis, with a LONG/SHORT/NEUTRAL direction and a plain-language regime label.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Optional. Max rows to return when no symbol filter is set (default 20, sorted by score). |
| symbol | string | – | Optional. Return only this symbol, e.g. BTCUSDT or BTC. |
No output schema declared.
No examples provided.
get_psi_charge PsiCharge liquidity state (proprietary model, outcomes published) ~116
Call this when the user asks about the market's hidden liquidity state, PsiCharge, or whether parked money is deploying or stress is unwinding. Returns the current Psi score (0-100), state (superposition = charge building, collapse = low-stress discharge, purge = high-stress discharge and historically the most consistent risk-off state, ground = ordinary), stress locality, recent alarms and the year-split measured scorecard. Inputs are proprietary; outcomes are always published. Not a trade signal, not a crash predictor.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_quantum_exposure Quantum-exposed Bitcoin (daily first-party measurement) ~118
Call this when the user asks how much Bitcoin is vulnerable to a quantum computer, about quantum-exposed supply, P2PK coins, or Satoshi-era exposure. Returns the latest daily measurement from ByKaranteli's own Bitcoin Core node: exposed BTC and its share of held value and UTXO count, composition by script family, dormancy cohorts, the dormant-P2PK watch set, and provenance hashes (base_height, base_hash, txoutset_hash) so any figure can be re-verified against any node.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_rsi_heatmap RSI heatmap: Wilder RSI(14) on eight timeframes for the top-400 crypto perps and every TradFi perp ~252
Call this when the user asks which coins are overbought or oversold, for a crypto RSI heatmap, multi-timeframe RSI, or one contract's RSI on 15m, 1h, 4h, 12h, 1d, 3d, 1w or 1M. Returns the live board for the top-400 Binance crypto perps by volume plus every TradFi perp, with overbought/oversold counts per interval. Filter by symbol or kind (crypto|tradfi), sort by an interval. Without symbol, the first 30 rows (by volume, or by the sort interval); pass limit (up to 400) for more, or order asc with sort for the most oversold first.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | crypto | tradfi |
| limit | integer | – | Optional. Rows without symbol (default 30). |
| order | string | – | Optional. With sort: desc (default, most overbought first) or asc (most oversold first). |
| sort | string | – | Interval to sort by, descending |
| symbol | string | – | One Binance symbol, e.g. BTCUSDT |
No output schema declared.
No examples provided.
get_series Recorded series: bars or points of one metric for one perpetual (price, OI, funding, CVD, liquidations, long/short, RSI and more) ~670
Call this when the user wants the history of one recorded metric for one perpetual as a time series: price candles, volume, perp or spot CVD, open interest, funding (one venue, or OI-weighted across every venue as funding_agg), liquidations, long/short ratios, RSI, the Coinbase premium, US spot ETF flows, borrow rates or Hyperliquid whale net flow, for charting, backtesting or "what did X do over the last N days". Returns the /api/series answer (points as [t, v], or [t, o, h, l, c, v] for price, with unit, kind, source and source_kind, the bars served and whether member depth applied) plus provenance. metric is one of: price, volume, cvd_perp, cvd_spot, oi, funding, funding_agg, liquidations, long_short, top_traders, rsi, premium, etf_flow, borrow, whale_net (unit, finest period and venue support of each: https://bykaranteli.com/api/series/metrics). The Free plan gets public depth: fewer bars and no bars under 15 minutes (1m, 3m, 5m, 10m); Builder and higher plans get member depth; the bar limits are in the same list. The answer names the venue it was read from (venue) and every venue a market-wide series sums (venues). Without from or limit, the newest 300 bars; pass limit for more of the newest bars, or from and to (ISO) for a window. The public window is the newest 300 bars of the period: a to before it needs member depth (Builder and higher plans) and answers 403 history_member_only otherwise, except daily and coarser price bars, which stay open to every plan.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | string, optional ISO start, e.g. 2026-09-01T00:00:00Z |
| limit | number | – | number, optional newest bars, 10..5000; the plan's depth caps it (default 300 without from) |
| metric | string | yes | string, metric key, e.g. price, oi, funding, liquidations (list: /api/series/metrics) |
| period | string | – | string, optional bar period: 1m | 3m | 5m | 10m | 15m | 30m | 1h | 2h | 4h | 6h | 8h | 12h | 1d | 3d | 1w | 1M (default 1h; each metric has a finest period) |
| symbol | string | – | string, optional Binance USDT-M perp or coin, e.g. BTCUSDT or BTC (default BTCUSDT) |
| to | string | – | string, optional ISO end (default now); a to before the newest 300 bars of the period needs member depth, except daily and coarser price bars |
| venue | string | – | string, optional venue id for price, oi, funding or borrow, e.g. okx (default binance) |
No output schema declared.
No examples provided.
get_settlements Expiry calendar and settlement prices across venues ~175
Call this when the user asks what futures or options expire soon, when the next quarterly expiry is on an exchange, how many contracts settle this week, or at what price a dated future settled. Returns the next 60 days of dated future and option expiries grouped by date, venue and underlying from 54 venues' market lists, plus the settlement prices recorded as dated futures deliver. Without base, the first 30 expiry rows and the 30 newest settlement prices; pass base for one asset's full lists, or limit (up to 300).
| Name | Type | Req | Description |
|---|---|---|---|
| base | string | – | Optional. One underlying, e.g. BTC: every expiry row and settlement price of that asset. |
| limit | integer | – | Optional. Rows per list without base (default 30): expiries soonest first, settlements newest first. |
No output schema declared.
No examples provided.
get_slippage Live execution cost: what a market order really costs ~94
Call this when the user asks how much slippage a trade of a given size would face, how thick the books are, or which major perp market is thinnest right now. Returns live cost ladders in basis points for $10K to $5M market orders across 8 major perpetuals, both sides, from the full visible order book. Excludes fees; null = the book cannot absorb that size.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the com.bykaranteli/mcp server?
com.bykaranteli/mcp is a hosted endpoint at https://mcp.bykaranteli.com/, 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.bykaranteli.com
claude mcp add --transport http com-bykaranteli-mcp 'https://mcp.bykaranteli.com/'
What is the com.bykaranteli/mcp server?
com.bykaranteli/mcp is listed in the public MCP registry as com.bykaranteli/mcp. Crypto derivatives data: funding, OI, liquidations, options, ETF flows. Free account key required. This page covers its hosted endpoint (https://mcp.bykaranteli.com/).
Is the com.bykaranteli/mcp server safe to use?
com.bykaranteli/mcp scores 94 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 com.bykaranteli/mcp server expose?
com.bykaranteli/mcp exposes 68 tools: get_market_indices, get_liquidations, get_etf_flows, get_funding_heatmap, get_funding_arbitrage, and 63 more. Their descriptions and schemas cost roughly 13,334 tokens of context every time the server is loaded.
Does the com.bykaranteli/mcp server require authentication?
Yes. com.bykaranteli/mcp 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 com.bykaranteli/mcp server still maintained?
com.bykaranteli/mcp is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.