Skip to main content
Glama
Tickerbot MCP Server

Tickerbot MCP Server

Official
by tickerbot

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
TICKERBOT_API_KEYYesYour API key. Sent as Authorization: Bearer <key> on every call.
TICKERBOT_API_URLNoOverride 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

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
tickerbot_scanA

Screens every ticker with a SQL WHERE clause and returns the matches. Run it now, or add asof to backtest it on any past date. The q grammar is a flat SQL WHERE over signal names: AND/OR/NOT, comparisons, numeric and string literals, custom signals by name. No JOIN or subqueries. With group_by the result is rollup rows, not tickers. Example: gap_up AND market_cap < 2000000000 AND NOT earnings_this_week.

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: q: golden_cross AND rsi_14 > 70.

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 q vocabulary before composing a scan; custom signals appear with kind: custom. Narrow it with category, group, type, search and select=type,description rather than reading all ~460 rows.

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 asof: a screen on that one signal. Returns catalog (what the signal is) every time. Booleans list their matches with no condition; every other type lists them only with one, typed like the signal: ">70" (numeric), "<YYYY-MM-DDTHH:MM:SSZ" (timestamp), ">=YYYY-MM-DD" (date), "=ETF" (string); without it you get the catalog entry and a note. Without order, a non-boolean sorts by its value in the direction the condition implies (< ascending, > descending). To know when each ticker started matching, use tickerbot_query_events with kind=signal, signal=, transition=enter.

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 condition; any other signal needs one (<30). For a compound condition use tickerbot_subscribe_scan.

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 asof. A comma list returns data keyed by symbol plus not_found. Crypto is the X-prefixed pair (X:BTCUSD); bare BTC/ETH are US-listed ETFs.

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 select, or * for every signal the grain stores, every ticker on one shared grid. series is keyed by symbol, one flat row per grain step. Paged backward: pass next_cursor back as cursor with the same params. For when a yes/no signal flipped, use tickerbot_query_events with kind=signal.

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 target_url for in-app delivery.

tickerbot_get_barsB

Returns OHLCV bars from 1s to monthly for one ticker or a comma list of up to 50 in the path, such as a screen's matches.

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 1m span is not a gap: sub-hour bars load on the first request for a symbol.

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 data.holdings and the sector mix data.sectors. When the ticker is not an ETF, data.is_etf is false and both are empty; data.is_etf: true with zero holdings means a real ETF whose holdings are not ingested yet. The reverse lookup ("which ETFs hold NVDA") is the etf_holders signal on tickerbot_get_ticker, or a scan: 'SMH' = ANY(etf_holders).

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); q alone is not a bound. With one kind, its payload fields are bare names in q/select/group_by (q: firm ILIKE 'Morgan Stanley', q: relevance >= 0.8 on news); tickerbot_list_event_kinds lists them. join: state adds the ticker's signals as of each event. Every result has a stable id: use it to drop duplicates. kind: signal takes custom signals too.

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 ts means, and the fields you can name in q, select and group_by when you ask for that kind alone.

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 q covers the event's fields (with one kind, bare: firm = 'Goldman Sachs') and the ticker's signals at fire time (market_cap > 1e10); on a name clash (price, cik) the ticker signal wins; the event's own value is payload->>'price'. Latency is the ingest cadence (analyst ≤1h, corporate kinds daily), not sub-minute.

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. ticker (one or a comma list) keeps articles that mention it; add min_relevance: 0.8 to keep only articles about it. Each article carries mentions: per ticker, relevance and sentiment_score/sentiment. Naming ticker, relevance, sentiment_score or sentiment in q/select/group_by gives one row per article per mention: q: ticker = 'NVDA' AND sentiment_score < -0.3 is articles negative about NVDA. search is full-text over title and summary. Rollups with group_by/having return truncated: true instead of paging.

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 event: "news.fired" with articles, each the Query news row (or select) plus mentions.

tickerbot_list_universesA

Lists every universe you can use: your own ticker lists and the built-in ones. kind: builtin lists the built-in universes (top_10, top_100); omit it for yours; builtin,custom lists both. Use a slug as universe on scan, signal and subscribe tools.

tickerbot_create_universeC

Saves a named list of tickers to scope screens and subscriptions.

tickerbot_get_universeB

Returns one universe: a built-in (top_10, top_100) or one you own.

tickerbot_update_universeA

Updates one of your universes: its name, description or members. tickers replaces the whole list; add/remove adjust it. Built-in universes cannot be edited.

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

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.6/5.0

Scored across 35 tools

Disambiguation4/5

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.

Naming Consistency4/5

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.

Tool Count3/5

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.

Completeness5/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues