
mcp-server
The stock market, in SQL — scan, replay, or subscribe across ~12k US tickers and top 100 cryptos.
What it can do
What data it sees
Do you need an account
An API key from the service settings is required
The stock market, in SQL — scan, replay, or subscribe across ~12k US tickers and top 100 cryptos.
How to connect
How to connect mcp-server to Claude
The server address to paste into Claude settings:
https://api.tickerbot.io/mcp
- Open Claude (claude.ai or the desktop app).
- Go to Settings → Connectors.
- Click Add custom connector.
- Paste the server address copied below into Remote MCP server URL and click Add.
- In a chat, click + → Connectors and switch the new connector on.
Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.
Authorization
After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.
How to connect mcp-server to ChatGPT
The server address to paste into ChatGPT settings:
https://api.tickerbot.io/mcp
- Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
- Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
- Open Settings → Connectors and click Create.
- Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
- Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
- In a new chat open + → Apps/Connectors and enable the connector.
OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.
Authorization
On first use ChatGPT opens the service's sign-in window. Sign in and approve access.
How to connect mcp-server to Cursor
The server address to paste into Cursor settings:
https://api.tickerbot.io/mcp
Fastest: click Open in Cursor below and confirm the prompt.
Manually:
- In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
- Paste the JSON copied below into
~/.cursor/mcp.json(per project:.cursor/mcp.jsonin the repo root). - Save the file. The server appears in the MCP list; authorize it there if asked.
Authorization
If the service needs sign-in, an authorize button appears next to the server in the MCP list.
Server tool list (32)
Raw names from tools/list. Only developers need these.
| tickerbot_list_tickers | Every symbol we track, active or delisted, as one identity row each. Use `/v2/tickers/{ticker}` for the full row. |
| tickerbot_get_ticker | The full ticker row, every signal on the schema page, for one symbol or a comma list of up to 50. Right now, or with `asof`, as of any past date. Pass a comma list of up to 50 symbols for a batch (`data` keyed by symbol plus `not_found`). Crypto is the X-prefixed pair (X:BTCUSD) — bare BTC/ETH are US-listed ETFs. |
| tickerbot_subscribe_ticker | Push one ticker: we POST your endpoint whenever it matches the condition you give. Webhooks need a paid plan (Free has no webhook slots). Omit `target_url` for in-app delivery. |
| tickerbot_get_ticker_coverage | For one ticker, what we hold and how far back — so an empty result is never ambiguous. Ask this before treating a gap in bars or series as an outage. `minute_tier.included: false` with `on_demand: true` is not a gap — sub-hour bars fetch from the provider on first request. |
| tickerbot_list_signals | Every signal you can name in a query — the built-in signals and your own custom signals, in one catalog. Use to discover the signal names and `q` vocabulary before composing a scan; custom signals appear with `kind: custom`. |
| tickerbot_create_custom_signal | A named boolean predicate you can reference anywhere a built-in signal goes. |
| tickerbot_update_custom_signal | Update a custom signal you own — its expression, description, or name. |
| tickerbot_delete_custom_signal | Delete one of your custom signals. Refused by default if another of your signals references it. |
| tickerbot_get_signal | The state of a signal is the set of tickers matching it right now, or with `asof`, as of any moment. One name, the whole market, one call. Booleans need no `condition`; numerics need one like ">70". Sorted by signal value desc for numerics. |
| tickerbot_subscribe_signal | Push one signal: we POST your endpoint whenever any ticker starts matching it. Webhooks need a paid plan (Free has no webhook slots). Omit `ticker` to watch the whole universe. |
| tickerbot_scan | Every ticker matching a SQL WHERE clause. Right now, or with `asof`, as of 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_scan | Push a whole query: we POST your endpoint every time the match set changes. Webhooks need a paid plan (Free has no webhook slots). Use for "alert me when this happens" requests. |
| tickerbot_get_series | Any signals for any tickers on one shared time grid — up to 50 tickers by 25 columns per call. One flat row per ticker per interval step, cursor-paged backward. `transitions_only: true` with boolean signals returns only the rows where a boolean flipped. |
| tickerbot_get_bars | OHLCV bars from 1-second through monthly. The feed underneath the table. |
| tickerbot_list_events | One timeline across every ticker: earnings, dividends, splits, insider filings, analyst actions, plus opt-in signal firings and news. Requires at least one bound: a ticker scope (ticker/tickers/universe), a time window (from/to), or firm/action — `q` alone is not a bound. `firm`/`action` match case-insensitively; a `q` payload match is case-sensitive. `join: state` attaches the ticker state as of each event. |
| tickerbot_subscribe_events | Push new events: we POST your endpoint when events of the kinds you chose land in the archives. Webhooks need a paid plan (Free has no webhook slots). `q` filters the ticker STATE; `event_q` filters the EVENT payload in the /v2/events grammar. Latency is the ingest cadence (analyst ≤1h, corporate kinds daily), not sub-minute. |
| tickerbot_search_news | SQL query over the news archive. Article rows, or rollups when you group them. Filter to a ticker with the `ticker` param, or in `q` via the auto-unnest alias `tk = 'NVDA'`. `search` is full-text over title and summary. Rollups with group_by/having return `truncated: true` instead of paging. |
| tickerbot_get_etf_holdings | Returns an ETF's constituents and their weights, heaviest first. When the ticker is not an ETF, `is_etf` is false and `holdings` is empty; `is_etf: true` with zero holdings means a real ETF whose holdings are not ingested yet. The reverse lookup ("which ETFs hold NVDA") is a scan filter on `etf_holders`, not this tool. |
| tickerbot_get_etf_sectors | Returns an ETF's sector weights, heaviest first. Always complete, since sector breakdowns are small. When the ticker is not an ETF, `is_etf` is false and `sectors` is empty. |
| tickerbot_list_universes | Every universe you can reference: your own named ticker lists and the built-in ones. `owner: system` lists the built-in universes (top_10, top_100); `all` lists both. Use a slug as `universe` on scan, signal, and subscribe tools. |
| tickerbot_create_universe | Create a named ticker list owned by your account. |
| tickerbot_get_universe | Returns the universe doc. Use `top_10`/`top_100` to fetch a system universe; any other slug must be one your account owns. |
| tickerbot_update_universe | Update one of your universes: its name, description, or members. `tickers` replaces the whole list; `add`/`remove` adjust it. System universes cannot be edited. |
| tickerbot_delete_universe | Permanently delete one of your universes. Webhooks that reference the deleted universe fail on their next eval — clean those up first. |
| tickerbot_list_webhooks | Every webhook subscription on this account, newest first. |
| tickerbot_create_webhook | Canonical create: a webhook is a trigger plus a delivery. Trigger shapes: scan {type:"scan", q, universe?}; ticker {type:"ticker", ticker, condition}; signal {type:"signal", signal, ticker?, universe?, condition?}; event {type:"event", kinds, tickers?, universe?, event_q?}. The subscribe tools are flat sugar over exactly this. Webhooks need a paid plan (Free has no webhook slots). |
| tickerbot_get_webhook | The current state of one webhook subscription. |
| tickerbot_update_webhook | Edit a webhook in place — send only the fields you want to change. The trigger and channel are immutable — delete and re-create to change what fires or where it delivers. Unknown fields are a 400. |
| tickerbot_delete_webhook | Delete a webhook subscription, and its delivery history with it. |
| tickerbot_list_webhook_deliveries | Recent deliveries for one webhook — what was sent, and what came back. |
| tickerbot_enable_webhook | Re-enable a disabled webhook and start it clean. Clears match-state, so the next eval treats every currently-matching ticker as new. |
| tickerbot_test_webhook | Send a real-shape test POST to your endpoint, instantly. One-shot: a failed test never retries and never auto-disables the webhook. 400 when the webhook has no target_url. |