Tickerbot MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TICKERBOT_API_KEY | Yes | Your API key. Sent as Authorization: Bearer <key> on every call. | |
| TICKERBOT_API_URL | No | Override the API base URL (for staging or self-hosted). | https://api.tickerbot.io |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| tickerbot_scanA | Screens every ticker with a SQL |
| tickerbot_subscribe_scanA | Gets you an alert by webhook each time a ticker starts matching a screen. Webhooks need a paid plan (Free has no webhook slots). Use for "alert me when this happens" requests. For one signal use tickerbot_subscribe_signal; a compound condition is a scan: |
| tickerbot_list_signalsA | Lists every signal you can screen on: the built-ins and your custom signals, in one catalog you can filter, search and page. Use to discover the signal names and |
| tickerbot_create_custom_signalB | Saves a named true/false SQL expression you can screen on, select and subscribe to like a built-in boolean. |
| tickerbot_get_signalA | Returns what one signal is (its catalog entry, the same object List signals returns for it) and every ticker matching it, live or on any past date with |
| tickerbot_update_custom_signalB | Updates a custom signal you own: its expression, description or name. |
| tickerbot_delete_custom_signalA | Deletes one of your custom signals. Refused by default if another of your signals references it. |
| tickerbot_subscribe_signalA | Gets you an alert by webhook each time a ticker starts matching one signal, bounded by a condition the way Get a signal is. Webhooks need a paid plan (Free has no webhook slots). A yes/no or custom signal takes no |
| tickerbot_list_tickersA | Lists every ticker we track, active or delisted, with its identity. For everything about one, use Get a ticker. |
| tickerbot_get_tickerA | Returns everything about one ticker or a comma list of up to 50 in the path (a screen's matches, say): every signal each one carries, live or on any past date with |
| tickerbot_get_historyA | Returns the signals of one ticker or a comma list of up to 50 in the path (a screen's matches, say) over time, all-time: up to 25 signals in |
| tickerbot_subscribe_tickerA | Gets you an alert by webhook each time one ticker starts matching a condition. Webhooks need a paid plan (Free has no webhook slots). Omit |
| tickerbot_get_barsB | Returns OHLCV bars from |
| tickerbot_get_ticker_coverageA | Reports what we hold for one ticker or a comma list of up to 50, and how far back, so an empty result is never ambiguous. Ask this before treating a gap in bars or history as an outage. An absent |
| tickerbot_get_etf_holdingsA | Returns an ETF's constituents and their weights, heaviest first, and its sector weights, for one ETF or a comma list of up to 50. Returns |
| tickerbot_query_eventsA | Queries events with SQL across every ticker or a screen's matches: earnings, dividends, splits, filings, insider trades and analyst actions, plus opt-in estimate revisions, news and signal firings. Requires at least one bound: a ticker scope (ticker/universe) or a time window (from/to); |
| tickerbot_list_eventsA | Deprecated: works until 2027-01-12. Same as tickerbot_query_events; call that instead. |
| tickerbot_list_event_kindsA | Returns every event kind: what it is, whether it is in the default stream and can be subscribed to, what its |
| tickerbot_subscribe_eventsA | Gets you an alert by webhook when new events of the kinds you choose land, filtered on the event and on the ticker's signals. Webhooks need a paid plan (Free has no webhook slots). One |
| tickerbot_query_newsA | Queries news with SQL for any ticker or a screen's matches: articles with how each one treats every ticker it mentions, or rollups when you group them. |
| tickerbot_search_newsA | Deprecated: works until 2027-01-12. Same as tickerbot_query_news; call that instead. |
| tickerbot_subscribe_newsA | Gets you an alert by webhook when a new article matches your search, tickers or SQL filter, with how it treats each ticker it mentions. Webhooks need a paid plan (Free has no webhook slots). Takes Query news's filters (search, ticker, universe, min_relevance, q); one of search/ticker/universe/q is required, since the whole market is about 6,000 articles a weekday. Fires as new matching articles land; each article fires once. Each delivery is |
| tickerbot_list_universesA | Lists every universe you can use: your own ticker lists and the built-in ones. |
| tickerbot_create_universeC | Saves a named list of tickers to scope screens and subscriptions. |
| tickerbot_get_universeB | Returns one universe: a built-in ( |
| tickerbot_update_universeA | Updates one of your universes: its name, description or members. |
| tickerbot_delete_universeA | Permanently deletes one of your universes. A universe any of your webhooks still uses answers 409 universe_referenced; force=true deletes it, and those webhooks are disabled at their next evaluation. |
| tickerbot_list_webhooksB | Lists every webhook on your account, newest first. |
| tickerbot_get_webhookA | Returns one webhook's current state. |
| tickerbot_update_webhookA | Edits a webhook in place; send only the fields you want to change. The trigger takes the filters of the subscribe that made the webhook (subscription_origin.type: scan q/universe/select/order/dir; ticker q/select; signal condition/universe/select/order/dir; event kind/ticker/universe/q/select; news search/ticker/universe/min_relevance/q/select), validated like a new subscribe; a change to the filters fires only on new matches (what already matches or already happened does not fire), while an edit of select/order/dir keeps what already matched. enabled=true turns a disabled webhook back on. Unknown fields are a 400. |
| tickerbot_enable_webhookA | Deprecated: works until 2027-01-12, then is removed. Turns a disabled webhook back on (a webhook disabled after repeated delivery failures, or one you turned off). It is tickerbot_update_webhook with enabled=true: call that instead. |
| tickerbot_delete_webhookB | Deletes a webhook and its delivery history. |
| tickerbot_list_webhook_deliveriesB | Lists a webhook's recent deliveries: what was sent and what came back. |
| tickerbot_redeliver_webhook_deliveryA | Resends a past delivery, with the exact body it carried, to the webhook's current target. The webhook must be active (409 otherwise); take delivery ids from tickerbot_list_webhook_deliveries. Test fires cannot be resent. |
| tickerbot_test_webhookA | Sends a sample delivery to your endpoint, instantly: the same shape, headers and signature as a real fire. One-shot: a failed test never retries and never auto-disables the webhook. 400 for an in-app webhook (nothing external to send to). |
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 35 tools
Most tools are cleanly separated by resource (bars vs history vs ticker vs ETF holdings vs events vs news vs universes vs webhooks), and the long descriptions call out the boundaries explicitly. The fuzzy zone is the subscribe family: subscribe_ticker (a ticker matching a condition), subscribe_signal (one signal + condition) and subscribe_scan (compound screen) are adjacent enough that an agent may pick wrong, and three deprecated aliases (list_events, search_news, enable_webhook) still sit in the catalog alongside their replacements.
Nearly all tools follow a uniform tickerbot_verb_noun pattern (get_ticker, list_universes, create_custom_signal, delete_webhook, redeliver_webhook_delivery). Deviations are minor: the bare tickerbot_scan has no noun, and the verb choice flips between list_ and query_ for the same resource pair (list_events vs query_events, search_news vs query_news), though those are the deprecated/new split.
35 tools is heavy, and three of them are deprecated aliases that add no capability. The breadth is partly justified (bars, signals, scans, history, events, news, ETF holdings, webhooks, universes are genuinely separate domains), but the surface could be trimmed toward the 15-20 range without losing functionality.
Full lifecycle coverage appears present: CRUD for universes, custom signals and webhooks, plus deliveries, redelivery and test-fire; read/query paths for tickers, coverage, bars, history, signals, scans, ETF holdings, events and news, with asof backtesting and paging. I can't identify a dead end an agent would hit for the stated purpose.