Tickory MCP server wrapper for saved scans, ad hoc scan execution, and relay routing
Drift inferred · capture-to-capture
No drift recorded — single capability capture; advisories appear once its surface changes.
tools
-
tickory_add_relay_route
Add one direct relay route to telegram, webhook, discord, or email
-
tickory_create_relay_source
Create a TradingView relay source and return the paste-ready TradingView setup payload
-
tickory_create_scan
Create a new scan with CEL expression and hard gates
-
tickory_describe_indicators
Describe available CEL variables, recommended guards, and example expressions
-
tickory_explain_alert_event
Explain why an alert triggered or was suppressed
-
tickory_get_alert_event
Fetch one alert event by UUID
-
tickory_get_relay_trace
Fetch the full lifecycle trace for one relay source event
-
tickory_get_scan
Fetch one scan by ID
-
tickory_list_alert_events
List alert events with cursor pagination
-
tickory_list_relay_events
List recent inbound relay events for one TradingView source
-
tickory_list_relay_sources
List TradingView relay sources and direct-route summaries
-
tickory_list_scans
List scans visible to the API key owner
-
tickory_replay_relay_event
Replay one failed relay route when the backend allows it
-
tickory_run_ad_hoc_scan
Execute a one-off expression immediately without creating a saved scan
-
tickory_run_scan
Trigger a scan run immediately
-
tickory_update_scan
Replace an existing scan definition
code files: 4
filesystem 2
- fs package/bin/tickory-mcp.js :4
const fs = require("node:fs"); - fs (weak) package/scripts/lib/install.js :3
const fs = require("node:fs");
shell / exec 1
- shell package/bin/tickory-mcp.js :6
const { spawn } = require("node:child_process");
install hooks 1
- postinstall package/package.json :24
node ./scripts/postinstall.js