tickory_add_relay_route
Add one direct relay destination to a TradingView source for telegram, webhook, discord, or email delivery.
LABSCO SUMMARY
explain_alert_event and replay_relay_event are the two tools that answer 'why did nothing happen' — the question every alerting system leaves you to work out alone.
An alert pipeline fails silently by nature: the scan matched but the alert was suppressed, or the alert fired but one destination rejected it, and both look identical from the outside, which is no notification. Here the suppression has its own explanation call, and a relay event carries a per-route status with a stored payload and a single-route replay. That is a system built by someone who has debugged one of these at two in the morning. describe_indicators is the other considered piece — a scan is a CEL expression, and exposing the variables, guards and ranges as a tool means the agent can write a valid one instead of guessing at syntax and getting an empty result set that reads like a market with no matches.
What it is
A market-scanning and alert-routing client with two halves: scans that evaluate indicator expressions against tracked symbols, and a TradingView relay that takes inbound webhooks and fans them out to Telegram, Discord, email or a webhook of your own.
What you get
- Scans as saved objects — list, fetch, create, replace — plus run_scan to execute one now and return matching symbols with their indicator values.
- run_ad_hoc_scan executes a one-off without creating or touching a saved scan, so experimenting does not leave residue.
- describe_indicators returns the CEL variables, guards, ranges and example expressions a scan can be written against, which is what makes the expression language usable without leaving the client.
- Alert events list and open individually, and explain_alert_event says why one triggered or was suppressed — the suppression case being the one that is otherwise invisible.
- get_market_data returns live price, indicators and metadata for one or more symbols, and list_symbols filters by exchange, contract type or search.
- The relay: create a source and get back its webhook URL, secret and TradingView-ready configuration; add destinations for Telegram, webhook, Discord or email; and list inbound events with per-route status.
- get_relay_trace returns one event's full lifecycle including the stored payload, and replay_relay_event re-sends a single failed route rather than the whole event.
Requirements
TICKORY_API_BASE_URL and TICKORY_API_KEY. Scans and alert events are scoped to the key's owner, so what is visible depends on which key is loaded.
Setup effort
One command plus a key — npx @tickory/mcp, then supply credentials
USE CASES
01
Writing a scan that actually parses
Ask what CEL variables, guards and ranges are available with example expressions, then run it ad hoc before saving anything.
02
Keeping a scan and running it on demand
Create it, run it now to see the matching symbols with their indicator values, and replace it wholesale when the thesis changes.
03
Finding out why you were not alerted
Open the alert event and ask why it triggered or was suppressed — the suppressed case being the one that leaves no other trace.
04
Getting TradingView alerts to more than one place
Create the relay source, take its webhook URL and secret into TradingView, then add the Telegram, Discord, email or webhook destinations it should fan out to.
05
Chasing down a notification that never arrived
Pull the event's full lifecycle trace with its stored payload, see which route failed, and replay just that one instead of re-firing everything.
18 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
tickory_create_relay_source
Create a TradingView relay source and return the webhook URL, source secret, and TradingView-ready payload template.
tickory_create_scan
Create a new user-owned scan.
tickory_describe_indicators
Describe the CEL variables, guards, ranges, and example expressions available for Tickory scan rules.
tickory_explain_alert_event
Explain why an alert event triggered or was suppressed.
tickory_get_alert_event
Fetch one alert event by ID.
tickory_get_market_data
Get live price, indicators, and metadata for one or more symbols.
tickory_get_relay_trace
Fetch the full lifecycle trace for one inbound TradingView relay event, including the stored payload and per-route outcomes.
tickory_get_scan
Fetch one scan by ID.
tickory_list_alert_events
List alert events for the API key owner.
tickory_list_relay_events
List recent inbound relay events for one TradingView source with per-route summary status.
tickory_list_relay_sources
List TradingView relay sources, optionally including direct-route summaries. Non-TradingView sources and legacy scan-backed routes are omitted.
tickory_list_scans
List scans visible to the API key owner.
tickory_list_symbols
List tracked symbols with optional filters for exchange, contract type, and search query.
tickory_replay_relay_event
Replay one failed route from a TradingView relay event trace when the downstream alert event is still replayable.
tickory_run_ad_hoc_scan
Execute a one-off scan immediately without creating or modifying a saved scan.
tickory_run_scan
Run a scan immediately and return matching symbols with indicator values.
tickory_update_scan
Replace an existing user-owned scan. Pass the full desired scan state, including timeframe.
BEFORE YOU INSTALL
What to know first
Tools you get
18 tools when we connected. tickory_get_market_data and tickory_list_symbols are undocumented. Your API key's scopes decide the rest: without manage_scans you can't run or create scans, and the relay tools need manage_routing and read_events.
Requires
- npx on PATH
- TICKORY_API_KEY in your environment
Where it runs
Both documented clients run the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 18 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx @tickory/mcpMCP Clients
Claude Desktop, Claude Code
JSON
{
"mcpServers": {
"tickory": {
"command": "npx",
"args": [
"@tickory/mcp"
],
"env": {
"TICKORY_API_BASE_URL": "https://api.tickory.app",
"TICKORY_API_KEY": "<YOUR_TICKORY_API_KEY>"
}
}
}
}
