Integrates with Binance Futures to monitor crypto markets using programmable CEL rules, allowing for the creation and management of custom scans, real-time alert event tracking, and detailed analysis of market indicators.
Tickory MCP Server
Real-time crypto scanner alerts, delivered straight to your AI agent.
Tickory monitors Binance Futures markets using programmable CEL rules and sends alerts when conditions match. This MCP server lets any agent framework create scans, read alert events, and understand why alerts triggered — all through the Model Context Protocol.
Quick demo
You: "Create a scan that fires when RSI drops below 30 on any coin with volume over $100k"
Agent (via tickory_create_scan): Done — scan "Oversold Bounce" created.
You: "Run it now"
Agent (via tickory_run_scan): 3 matches found: ETHUSDT, SOLUSDT, DOGEUSDT.
You: "Why did ETH match?"
Agent (via tickory_explain_alert_event): RSI-14 was 24.7, below your threshold of 30.
Volume gate passed: $487k USDT > $100k minimum. CEL expression evaluated true.Install
npm / npx
npx @tickory/mcpThe npm package downloads the matching GitHub Release binary for macOS and Linux during install, so npx @tickory/mcp works without a separate build step.
Go install
go install github.com/tickory/tickory-mcp@latestPre-built binaries
Download from GitHub Releases for Linux and macOS (amd64/arm64).
Build from source
git clone https://github.com/tickory/tickory-mcp.git
cd tickory-mcp
go build -o tickory-mcp .Setup
Get a Tickory account at tickory.app
Create a scoped API key in your dashboard under Settings > API Keys
Configure the MCP server:
export TICKORY_API_BASE_URL=https://api.tickory.app
export TICKORY_API_KEY=tk_xxxxxxxx_yyyyyyyyyyyyyyyyyyyyyyyyClaude Desktop
Add to your claude_desktop_config.json:
{
"mcpServers": {
"tickory": {
"command": "npx",
"args": ["@tickory/mcp"],
"env": {
"TICKORY_API_BASE_URL": "https://api.tickory.app",
"TICKORY_API_KEY": "tk_xxxxxxxx_yyyyyyyyyyyyyyyyyyyyyyyy"
}
}
}
}Claude Code
Add to your .mcp.json:
{
"mcpServers": {
"tickory": {
"command": "npx",
"args": ["@tickory/mcp"],
"env": {
"TICKORY_API_BASE_URL": "https://api.tickory.app",
"TICKORY_API_KEY": "tk_xxxxxxxx_yyyyyyyyyyyyyyyyyyyyyyyy"
}
}
}
}Cursor / Windsurf / other MCP clients
Point either to npx @tickory/mcp or to the standalone tickory-mcp binary with the environment variables above. The server uses stdio (newline-delimited JSON-RPC 2.0).
Tools
Tool | Description |
| List scans visible to the API key owner |
| Fetch one scan by ID |
| Create a new scan with CEL expression and hard gates |
| Replace an existing scan definition |
| Trigger a scan run immediately |
| Describe available CEL variables, recommended guards, and example expressions |
| List alert events with cursor pagination |
| Fetch one alert event by UUID |
| Explain why an alert triggered or was suppressed |
All tools return schema_version: "v1" for contract stability.
Configuration
Variable | Required | Default | Description |
| Yes | — | Tickory API base URL |
| Yes | — | Scoped API key ( |
| No |
| HTTP timeout for API requests |
CLI flags (--api-base-url, --api-key, --timeout) override environment variables.
Error handling
Upstream HTTP errors are mapped to deterministic MCP error codes:
HTTP Status | MCP Code | Retryable |
400 |
| No |
401 |
| No |
403 |
| No |
404 |
| No |
409 |
| No |
429 |
| Yes |
5xx |
| Yes |
Scoped API key permissions
Scope | What it allows |
| Read alert events, scan runs, activity |
| Create/read/update/delete scans, execute scans |
| Create/manage alert sources and routes |
Create keys with the minimum scopes needed. See the developer docs for details.
Protocol versions
This server negotiates MCP protocol versions: 2024-11-05, 2025-03-26, 2025-06-18, 2025-11-05, and 2025-11-25.
License
MIT
This server cannot be installed
Resources
Looking for Admin?
Admins can modify the Dockerfile, update the server description, and track usage metrics. If you are the server author, to access the admin panel.