DEBYKO for AI agents
DEBYKO runs a remote MCP server at https://mcp.debyko.com/mcp. An AI client connected to it reads crypto derivatives market data from 16 venues, and every value comes with the venue that published it, when DEBYKO received it and how old it is.
Instructions for an AI client: https://debyko.com/skill.md
Nothing to install. Sign in with a DEBYKO account (a new email address opens a Free account, no card) or send an API key. The tools only read: none of them places an order, moves money or changes a setting.
01What an AI gets #
- Market data from 16 venues: venues and their listings, the latest ticker, mark price, funding, open interest, order book and 24 h statistics, the same values as they stood at a past moment, and completed candles.
- Provenance on every value: the venue that published it, the time DEBYKO received it and its age. A value that is not current comes back with its status (
stale,missing,not_published,off) and the reason, not a number. A period no venue reported is a gap, never an invented candle. - DQL, a query language that screens instruments across venues, for example "where is funding positive on at least one venue".
- Nine read-only tools:
venues,instruments,snapshots,history,screen,candles,agent_state,anchor_proof,account. The full list with arguments is on MCP server.
What a client may read is the plan of the account it signed in with, counted and limited as for any other client of the API. account shows the plan, its venues and what is left of today's limits.
02Connect #
The server URL is the same for every client: https://mcp.debyko.com/mcp (MCP Streamable HTTP). With only the URL, the client opens a DEBYKO page where you sign in with a code sent to your email and allow it. No key is copied anywhere.
- Claude.ai and Claude Desktop
- Settings, Connectors, Add custom connector. Give it the URL
https://mcp.debyko.com/mcpand nothing else, then sign in and choose Allow. - ChatGPT
- Add a custom connector in developer mode with the URL
https://mcp.debyko.com/mcp; ChatGPT signs in with OAuth. - Cursor
- Add to Cursor opens Cursor with the server filled in. By hand: in
.cursor/mcp.json,{"mcpServers": {"debyko": {"url": "https://mcp.debyko.com/mcp"}}}. - Claude Code
claude mcp add --transport http debyko https://mcp.debyko.com/mcp
Then run/mcpinside Claude Code and choose to authenticate.- Any MCP client
- Streamable HTTP at
https://mcp.debyko.com/mcp. The client discovers sign-in by itself: OAuth 2.1 with PKCE and dynamic client registration, described athttps://mcp.debyko.com/.well-known/oauth-protected-resource. - API key
- Where a client lets you set a header, send
Authorization: Bearer <key>instead of signing in. Keys are made on your account page.
Step by step for each client: Connect an AI agent.
03A prompt to start with #
Paste it into a new chat. It is the one the AI menu at the top of this page opens in Claude or ChatGPT.
Read https://debyko.com/skill.md and set up DEBYKO for me.
04What to ask #
- "Compare BTC funding across venues."
- "Show ETH candles on Hyperliquid for the last 24 h."
- "Which venues does DEBYKO collect, and how many listings does each have?"
05Alerts #
Alerts are made in Agent, which is in closed testing and not available to the public yet. There a rule is a DQL condition; when it fires, Agent sends a notification to Telegram or to a webhook, set up under Channels. Over MCP, agent_state reads whether your rules are true, false or unknown right now.
06Account and plans #
The Free plan costs nothing and needs no card; it reads a few venues and instruments and a week of history. Paid plans add venues, instruments, history and higher limits. What each plan includes is in the pricing section.
07Documentation and listings #
- Getting started with an AI client
- Alerts
- MCP tools
- DQL guide and API reference
- Official MCP Registry:
com.debyko/mcp - llms.txt: this site for a model; the documentation has its own at docs.debyko.com/llms.txt.