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 | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/tickory/tickory-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server