Tickory MCP server wrapper for saved scans, ad hoc scan execution, and relay routing
Tickory MCP MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Tickory MCP server wrapper for saved scans, ad hoc scan execution, and relay routing.
Real-time crypto scanner alerts, ad hoc scan execution, and TradingView relay routing, delivered straight to your AI agent.
Once Tickory MCP is connected, these are the calls the assistant has available:
tickory_list_scans — List scans visible to the API key ownertickory_get_scan — Fetch one scan by IDtickory_create_scan — Create a new scan with CEL expression and hard gatestickory_update_scan — Replace an existing scan definitiontickory_run_scan — Trigger a scan run immediatelytickory_run_ad_hoc_scan — Execute a one-off expression immediately without creating a saved scantickory_describe_indicators — Describe available CEL variables, recommended guards, and example expressionstickory_list_alert_events — List alert events with cursor paginationtickory_get_alert_event — Fetch one alert event by UUIDtickory_explain_alert_event — Explain why an alert triggered or was suppressedtickory_create_relay_source — Create a TradingView relay source and return the paste-ready TradingView setup payloadtickory_list_relay_sources — List TradingView relay sources and direct-route summaries@tickory/mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
You will need 2 environment variables: TICKORY_API_BASE_URL, TICKORY_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Among the team communication options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Tickory MCP's toolset — tickory_list_scans, tickory_get_scan, tickory_create_scan and 11 more — is a fair guide to whether it matches your workflow. It is maintained by tickory; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| tickory_list_scans | List scans visible to the API key owner |
| tickory_get_scan | Fetch one scan by ID |
| tickory_create_scan | Create a new scan with CEL expression and hard gates |
| tickory_update_scan | Replace an existing scan definition |
| tickory_run_scan | Trigger a scan run immediately |
| tickory_run_ad_hoc_scan | Execute a one-off expression immediately without creating a saved scan |
| tickory_describe_indicators | Describe available CEL variables, recommended guards, and example expressions |
| tickory_list_alert_events | List alert events with cursor pagination |
| tickory_get_alert_event | Fetch one alert event by UUID |
| tickory_explain_alert_event | Explain why an alert triggered or was suppressed |
| tickory_create_relay_source | Create a TradingView relay source and return the paste-ready TradingView setup payload |
| tickory_list_relay_sources | List TradingView relay sources and direct-route summaries |
| tickory_add_relay_route | Add one direct relay route to telegram, webhook, discord, or email |
| tickory_list_relay_events | List recent inbound relay events for one TradingView source |
{
"mcpServers": {
"tickory": {
"command": "npx",
"args": ["-y", "@tickory/mcp"],
"env": {
"TICKORY_API_BASE_URL": "your-value",
"TICKORY_API_KEY": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| TICKORY_API_BASE_URL | Endpoint or connection string the server talks to. | Yes |
| TICKORY_API_KEY | Credential the server authenticates with. | Yes |
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Inbox intelligence — search, read, draft and send Gmail through your assistant with OAuth auto-setup.
Read and write Jira, Confluence, Bitbucket, JSM and Compass from your AI client — with your own permissions.
Read and send Telegram messages through your assistant — chats, channels and history via the client API.
Enables Discord bot integration with Model Context Protocol (MCP) compatible applications like Claude Desktop.
Exposes REST APIs defined by OpenAPI specifications as Model Context Protocol (MCP) tools, facilitating seamless integration into MCP-based workflows.