Tickory MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TICKORY_API_KEY | Yes | Scoped API key (tk_...) | |
| TICKORY_API_BASE_URL | Yes | Tickory API base URL | |
| TICKORY_TIMEOUT_SECONDS | No | HTTP timeout for API requests | 15 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| tickory_list_scansA | List scans visible to the API key owner. |
| tickory_get_scanB | Fetch one scan by ID. |
| tickory_create_scanB | Create a new user-owned scan. |
| tickory_update_scanA | Replace an existing user-owned scan. Pass the full desired scan state, including timeframe. |
| tickory_run_scanB | Run a scan immediately and return matching symbols with indicator values. |
| tickory_run_ad_hoc_scanB | Execute a one-off scan immediately without creating or modifying a saved scan. |
| tickory_describe_indicatorsA | Describe the CEL variables, guards, ranges, and example expressions available for Tickory scan rules. |
| tickory_list_alert_eventsC | List alert events for the API key owner. |
| tickory_get_alert_eventA | Fetch one alert event by ID. |
| tickory_explain_alert_eventB | Explain why an alert event triggered or was suppressed. |
| tickory_get_market_dataA | Get live price, indicators, and metadata for one or more symbols. |
| tickory_list_symbolsA | List tracked symbols with optional filters for exchange, contract type, and search query. |
| tickory_create_relay_sourceA | Create a TradingView relay source and return the webhook URL, source secret, and TradingView-ready payload template. |
| tickory_list_relay_sourcesA | List TradingView relay sources, optionally including direct-route summaries. Non-TradingView sources and legacy scan-backed routes are omitted. |
| tickory_add_relay_routeB | Add one direct relay destination to a TradingView source for telegram, webhook, discord, or email delivery. |
| tickory_list_relay_eventsA | List recent inbound relay events for one TradingView source with per-route summary status. |
| tickory_get_relay_traceA | Fetch the full lifecycle trace for one inbound TradingView relay event, including the stored payload and per-route outcomes. |
| tickory_replay_relay_eventB | Replay one failed route from a TradingView relay event trace when the downstream alert event is still replayable. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 18 tools
All 18 tools have clearly distinct purposes. List vs. get, run vs. ad-hoc, and relay lifecycle tools (sources, events, traces, replay) are all well-separated, minimizing agent confusion.
All tools follow a consistent 'tickory_verb_noun' pattern (e.g., tickory_create_scan, tickory_list_alert_events). No mixing of styles or vague verbs.
18 tools is above the typical 3-15 range but still justified for the breadth of functionality (relays, scans, alerts, market data). Each tool has a distinct role, so it feels well-scoped rather than bloated.
Core workflows for scans, relays, and alerts are present (create, read, list, update, run). However, no delete or deactivate operations exist for scans, relay sources, or alerts, which are notable gaps for a complete lifecycle.