MCP server
DEBYKO runs a remote MCP server. It gives an AI client 11 read-only tools for API v2 data and saved Agent rule definitions. Beside them, 6 Agent tools let the AI set up alerts with you: link Telegram or a webhook, create, pause, edit and delete your alert rules, and turn Agent on or off. The Agent tools are being turned on account by account; a connection whose account does not have them yet is not offered them, and the AI gives the steps to do the same at agent.debyko.com. No tool places an order, moves money or changes your plan, keys or billing. How to add the server to a particular client (ChatGPT, Claude, Claude Code, Cursor) is on Connect an AI agent; every tool with its arguments and annotations is in MCP tools.
Endpoint
Section titled “Endpoint”| URL | https://mcp.debyko.com/mcp |
| Transport | Streamable HTTP |
| Sign-in | OAuth 2.1 with your DEBYKO account, or an API key as Authorization: Bearer <key> |
| Tools | 11 read-only tools (readOnlyHint: true); 6 Agent write tools for alerts, on per account during the rollout |
A request without credentials is answered 401 with a WWW-Authenticate header that points the client to the sign-in.
Signing in with OAuth
Section titled “Signing in with OAuth”- You add
https://mcp.debyko.com/mcpto the client. Nothing else: no key, no client id. - The client registers itself with DEBYKO (Dynamic Client Registration, RFC 7591) and opens a DEBYKO page in your browser.
- You sign in to your DEBYKO account with the six-digit code we email you. A new address opens a Free account; no card is asked for.
- The page names the client and asks you to allow it. You allow it once.
- The client receives a token tied to your account and its plan. You can revoke it at any time on your account page.
The client never sees your API keys, and DEBYKO never sees your conversation with the client, only the tool calls it makes.
With a key instead: create one on your account page and give the client the header Authorization: Bearer <key>.
The tools
Section titled “The tools”Each market data tool is one call to API v2 and counts as one request on your plan, except venues and instruments (free) and account (not counted against the day). agent_rule_get reads Agent’s saved definition without counting against requests or evaluations. Every market value comes with the venue that
published it, when it arrived and how old it is; a value that is not current comes back with its status (stale, missing, not_published, off)
and a reason instead of a number.
| Tool | What it answers |
|---|---|
venues |
Every venue DEBYKO collects, with how many listings it has and how many are collected. |
instruments |
The listings of a venue: symbol, tick and lot size, and which data layers are collected. |
snapshots |
The latest ticker, mark, funding, open interest, book or 24 h stats of the selected listings. |
history |
The same snapshot as it stood in the past: one row per period, per named instant, or per message. |
screen |
A DQL query across venues, for example “where is funding positive”, and what matched. |
candles |
Completed candles in any stored period; a period nobody reported is a gap, never an invented bar. |
agent_state |
The state of your Agent rules (true, false or unknown, with the reason). |
agent_rule_get |
The saved DQL and settings of one of your Agent rules, by ID or label; available with an account connection. |
anchor_proof |
A stored history row and the Merkle path to the daily root DEBYKO posts on Base. |
account |
Your plan, its venues and limits, and what is left of them today. |
The Agent tools, for an account that has them (they are calls to Agent, not to the API, and are not counted against your requests; Agent’s own plan limits apply):
| Tool | What it does |
|---|---|
agent_channels |
Where your alerts can go: Telegram (linked, waiting for Start, not linked) and webhooks, with your plan’s limits. Changes nothing. |
agent_channel_connect |
Telegram: a one-time link you open in Telegram (10 minutes). Webhook: adds your https receiver and sends it a test. |
agent_rule_create |
Creates an alert rule from a DQL condition and a label you give, with a dry run of what it answers right now and how to turn it off. |
agent_rule_set |
Pauses, resumes or edits a rule. |
agent_rule_delete |
Deletes a rule; its past firings stay. |
agent_set_enabled |
Turns Agent off (no rule is checked) or on again. |
Examples
Section titled “Examples”venues takes no arguments:
{}instruments: the BTC listing on Hyperliquid.
{ "where": "venue = HYPERLIQUID and base = BTC" }snapshots: funding and open interest for BTC and ETH on Bybit.
{ "where": "venue = BYBIT-PERP and base in (BTC, ETH)", "layers": ["funding", "oi"] }history: Hyperliquid BTC funding, one row per hour over three hours.
{ "where": "venue = HYPERLIQUID and base = BTC", "layers": ["funding"], "interval": "1h", "from": "2026-10-06T06:00:00Z", "to": "2026-10-06T09:00:00Z" }screen: instruments with positive funding on at least one venue, three at a time.
{ "query": "any(venues where funding > 0)", "limit": 3 }candles: hourly ETH candles on Binance USD-M.
{ "where": "venue = BINANCE-USDM and base = ETH", "timeframe": "1h", "from": "2026-10-06T06:00:00Z", "to": "2026-10-06T09:00:00Z" }agent_state: every rule of the account, from the last scheduled evaluation. fresh: true evaluates them now and uses the plan’s daily evaluations.
{}agent_rule_get: retrieve the original DQL of a named rule before explaining what it checks.
{ "label": "BYKO_V2_BREAKOUT_LONG" }anchor_proof: the proof for one stored row. at is the row’s own time, to the microsecond, as history returned it.
{ "venue": "HYPERLIQUID", "symbol": "BTC", "layer": "funding", "at": "2026-09-28T12:00:00Z" }account takes no arguments:
{}The full arguments of each tool are in the API reference; the selection grammar used by where and the query language of
screen are in DQL.
Limits by plan
Section titled “Limits by plan”The MCP server applies the limits of the plan of the account you signed in with, the same as the API. account returns the live figures for yours.
| Plan | Price | Venues | Instruments | History | Book levels | DQL / minute | Requests / second | Requests / day |
|---|---|---|---|---|---|---|---|---|
| Free | $0 | all | all | 7 days | 5 | 10 | 2, burst 10 | 5,000 |
| Mini | $9 / month | all | all | 30 days | 25 | 30 | 5, burst 20 | 50,000 |
| Standard | $29 / month | all | all | 365 days | all | 120 | 20, burst 80 | 500,000 |
| Pro | $99 / month | all | all | all | all | 600 | 50, burst 200 | 5,000,000 |
| Pro Plus | $249 / month | all | all | all | all | 3,000 | 200, burst 800 | 10,000,000 |
Prices and trials are on the pricing page. A call refused for the plan says so in its error, with what to do next.
Privacy and support
Section titled “Privacy and support”What is recorded when a client connects and calls the tools is in the Privacy policy (section 02, “Connecting an AI client”). Questions: support@debyko.com.