Skip to content
Changelog

Public Updates

Release notes, methodology adjustments, and transparency announcements from the ByKaranteli ops team. Only reports flagged public land here; the full internal ops log stays on the admin console.

Follow changes: RSS · JSON Feed

MCP

MCP 0.32.0: get_etf_flows takes XRP

get_etf_flows accepts asset XRP next to BTC, ETH and SOL and returns the US spot XRP ETF daily rows from 2026-09-08 with the same fields: net inflow, total net assets, cumulative inflow since launch and value traded, in USD. The tool description now gives each asset's first day (BTC and ETH since 2025-05-20, SOL since 2025-10-28, XRP since 2026-09-08) instead of one history length for all. Developers, ETF tracker.

MCP

Hosted MCP: the consent page names where an approval sends you

When an app asks to connect to your account through the hosted MCP server, the consent page now shows, under the name the app gave itself, the address your browser returns to once you allow it, and asks you to allow only a connection you started yourself. It also states in full what a connected app may do: use the data tools and read or change your alerts, your watchlist and your tracked addresses, never your account, keys or billing. Apps that are already connected keep working as before.

MCP

MCP 0.31.0: any recorded series, your alerts and watchlist by key, alerts from a sentence, provenance on every answer

get_series returns any recorded series (price, volume, CVD, open interest, funding, liquidations, long/short, RSI, Coinbase premium, ETF flows, borrow, Hyperliquid whale net) by metric, symbol, period and window, with the metric list at /api/series/metrics. New account tools list and change your own alerts and watchlist with your key: create, delete, add and remove are marked as writes, count on your plan and are recorded on your account. parse_alert_text turns a sentence such as "BTC funding above 0.05%" into the exact alert without inventing a threshold. Every market answer now carries a provenance block: the venues behind the number, full or sampled coverage, stale feeds, the first recorded day and the proof page. The account routes these tools use answer a key call with the same rate and quota headers as the public API. Connect guide, developers.

MCP

Hosted MCP: sign in with OAuth 2.1, the key path stays

MCP clients that offer a sign-in (claude.ai custom connectors, ChatGPT connectors, Claude Code, Cursor) can now connect to mcp.bykaranteli.com with OAuth 2.1: the client registers itself, you approve it once on a consent page, and it runs on a key of your own account that the Data and API page lists under connected apps and can disconnect. PKCE S256, one-use codes, rotated refresh tokens, public clients only. The account key in a header or in the address works as before; a keyless tool call still gets the sign-up steps as a readable answer. Discovery documents live at /.well-known/oauth-protected-resource on the MCP host and /.well-known/oauth-authorization-server on bykaranteli.com. Connect guide.

MCP

bykaranteli-mcp 0.30.6 and 0.30.7

0.30.6 points the source link of every tool at a page that exists and brings the option and options flow tool descriptions in line with the changes above. 0.30.7 describes the new expiries block of the options snapshot, ships a CHANGELOG.md inside the package and links it from the README. Setup and the tool list are on /developers.

MCPBreaking

Access policy: every hosted MCP tool call needs an account key

Every tool call on mcp.bykaranteli.com now needs an account key, free at /dashboard/api; connecting the server and listing its tools still work without one. The key goes in the x-api-key or Authorization header, and clients that cannot send headers (ChatGPT) use the address form ?key=bk_..., which should be kept like a password. The keyless pool is closed. The JSON API now decides its browser class by the Sec-Fetch-Site header. x402 pay-per-call and the Proof API stay open without an account.

MCPBreaking

Hosted MCP without a key: 100 tool calls a day per client, counted in the database

The keyless pool on mcp.bykaranteli.com now allows 100 tool calls a day per client address and 20 a minute, down from 600 a day. The count lives in the database, so it no longer starts over when the site is deployed. Someone asking questions through an assistant stays far below these numbers; the change is aimed at scripts that polled the endpoint around the clock. A free account key from /dashboard/api carries 15,000 calls a month in its own pool, and Builder and above lift the cap. A refused call answers 429 with the limit, the calls used and the reset time.

MCP

MCP server 0.9 · 33 tools + hosted endpoint

The bykaranteli-mcp package reached 0.9 with 33 tools covering signals, liquidations, funding, options, ETF flows and more. The hosted MCP endpoint serves the same tools with zero install. See /developers.