# TickerDB (remote · mcp.tickerdb.com)

Pre-computed market data that improves agent reasoning, reduces token usage, and replaces pipelines.

- Trust score: 75/100 (medium)
- Change this week: +7
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.tickerdb.com`: 75/100 (this document), [markdown](https://verifymcp.io/servers/com-tickerdb-mcp-server/mcp.md), [page](https://verifymcp.io/servers/com-tickerdb-mcp-server/mcp)
- npm · `tickerdb-mcp`: 35/100, [markdown](https://verifymcp.io/servers/com-tickerdb-mcp-server/tickerdb-mcp.md), [page](https://verifymcp.io/servers/com-tickerdb-mcp-server/tickerdb-mcp)

## Channel facts

- Endpoint: `https://mcp.tickerdb.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.8.6`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 91/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 49/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2843 tokens (~568/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-tickerdb-mcp-server https://mcp.tickerdb.com/mcp
```

### Codex

```toml
[mcp_servers.com-tickerdb-mcp-server]
url = "https://mcp.tickerdb.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-tickerdb-mcp-server": {
      "type": "remote",
      "url": "https://mcp.tickerdb.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-tickerdb-mcp-server --url https://mcp.tickerdb.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-tickerdb-mcp-server:
    url: "https://mcp.tickerdb.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-tickerdb-mcp-server": {
      "type": "http",
      "url": "https://mcp.tickerdb.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 75, −1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “get_search” rewrote its description, which is the text the model reads
- [security] Tool “get_summary” rewrote its description, which is the text the model reads
- [functional] Schema quality: excellent → good
- [cosmetic] “get_summary” reworded the description of “fields”
- [cosmetic] “get_search” reworded the description of “sort_by”
- [cosmetic] “get_search” reworded the description of “fields”

### 2026-08-02 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 75, +6)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 69, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 68, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 67)

First indexed and scored.

## MCP tools (5)

### `get_summary` (~1445 tokens)

Get pre-computed market intelligence for a specific stock, crypto, or ETF ticker. Supports 4 modes: (1) Snapshot (default) for the latest categorical state; (2) Historical snapshot by date; (3) Historical series with start and end dates; (4) Events by field and optional band, including aftermath fields on paid tiers, weekly trend_stage analysis, pattern setup states such as pattern_bull_flag and pattern_ascending_triangle, MA signal fields, trend_ma_crossover_event, MA distance lookbacks such as trend_distance_ma40, and stock-only fundamentals_free_cash_flow events. Add stats=true in event mode to return aggregate event-band and aftermath distributions instead of raw rows. Results can include freshness via as_of_date, same-candle OHLCV, market_cap, market_cap_tier, trend, momentum (including divergence_detected, divergence_type, stochastic_zone), volatility (including squeeze_active, squeeze_days), volume (including climax_detected, climax_type), patterns, support/resistance, levels (paid tiers), sector_context (rsi_zone, trend, agreement, asset_vs_sector_rsi), and stock-only fundamentals such as raw pe_ratio (latest ratio on or before the snapshot date; negative values preserved and unavailable values null), free_cash_flow, growth_zone, earnings_proximity, earnings_proximity_basis, analyst_consensus, valuation_percentile, and nested insider_activity when available. Summary keeps sibling _meta objects off by default; set meta=true or request explicit *_meta fields when paid-tier stability metadata is needed.

Input parameters:

- `after` (string): Return events after this date (YYYY-MM-DD). Only used with field.
- `band` (string): Filter events to a specific band value (e.g. deep_oversold, strong_uptrend, stage_2_growth). For MA distance event fields such as trend_distance_ma40, grouped aliases above and below are also support…
- `before` (string): Return events before this date (YYYY-MM-DD). Only used with field.
- `context_band` (string): Only return events where the context ticker was in this band (e.g. downtrend). For MA distance context fields, grouped aliases above and below are also supported. Must be provided with context_ticker…
- `context_field` (string): Band field to check on the context ticker (e.g. trend_direction, trend_stage, or trend_distance_ma40). Must be provided with context_ticker and context_band.
- `context_ticker` (string): Cross-asset correlation: a second ticker to filter against (e.g. SPY). Requires context_field and context_band. Plus/Pro only.
- `date` (string): Historical date (YYYY-MM-DD) for a point-in-time snapshot. Requires Plus or Pro plan. Omit for latest.
- `end` (string): Range end date (YYYY-MM-DD). Use with start for historical series.
- `field` (string): Band field name for event queries (e.g. momentum_rsi_zone, extremes_condition, trend_direction, trend_stage, pattern_bull_flag, pattern_ascending_triangle, pattern_rising_wedge, trend_ma8_slope throu…
- `fields` (array): Optional summary fields to return. Identity fields such as market_cap and market_cap_tier are always kept. Pass sections like ohlcv, trend, momentum, volatility, volume, patterns, extremes, support_l…
- `limit` (integer): For event mode: max results (1-50), returned newest-first by default. For sample=even date ranges: requested sampled rows, capped by plan (Free 3, Plus 10, Pro 50).
- `meta` (boolean): Snapshot and history modes only. Add true to include sibling _meta / status_meta stability objects across the response. Explicit *_meta field paths in fields still work without this flag.
- `sample` (string): Date range mode only. Use 'even' to evenly distribute snapshots across the full start/end range.
- `start` (string): Range start date (YYYY-MM-DD). Use with end for historical series.
- `stats` (boolean): Event mode only. Add true to return aggregate stats instead of raw event rows.
- `ticker` (string, required): Ticker symbol, e.g. AAPL, BTCUSD, SPY
- `timeframe` (string): Analysis timeframe. Default: daily

Output parameters:

- `data`: The TickerDB API response payload for this tool call.

### `get_ohlcv` (~215 tokens)

Get stored daily end-of-day OHLCV candles for a stock, ETF, or crypto ticker. Use this for exact-return calculations, charts, and backtests after get_summary identifies a setup. Results are paginated; pass next_cursor back as cursor to continue. Equity and ETF bars are split-and-dividend adjusted; crypto bars are unadjusted. Credit cost is 1 credit per 100 bars returned, rounded up, with a 1 credit minimum.

Input parameters:

- `cursor` (string): Exclusive date cursor from next_cursor for pagination (YYYY-MM-DD).
- `end` (string): Inclusive end date (YYYY-MM-DD).
- `limit` (integer): Maximum candles to return (1-1000). Default: 100.
- `order` (string): Sort by candle date. Default: desc.
- `start` (string): Inclusive start date (YYYY-MM-DD). Lookback is limited by plan.
- `ticker` (string, required): Ticker symbol, e.g. AAPL, BTCUSD, SPY

Output parameters:

- `data`: The TickerDB API response payload for this tool call.

### `get_search` (~939 tokens)

Search for assets matching filter criteria, including categorical states (e.g. oversold assets, strong uptrends, bull/bear flag setups, triangle or wedge setups, free-cash-flow surplus or burn, recent golden crosses, weekly stage 2 assets near the 40w MA with high volume, volatility squeeze active, volume climax detected, insider buying zone, sector-aligned breakouts) or rankings by a field such as market_cap on a historical date. Pass filters as a JSON-encoded array of {field, op, value} objects. Use get_schema to discover valid field names; fields use clean flat names for raw values such as pe_ratio, ma8, and ma200, and full expanded names for semantic fields such as momentum_rsi_zone, pattern_bull_flag, pattern_bull_flag_breakout, pattern_bear_flag_breakdown, pattern_ascending_triangle, pattern_rising_wedge, trend_ma_crossover_event, trend_distance_ma40, trend_stage, fundamentals_free_cash_flow, insider_zone, sector_agreement, volatility_squeeze_active, volume_climax_detected, fundamentals_analyst_consensus, and fundamentals_earnings_proximity, fundamentals_earnings_proximity_basis. Use fields to control returned columns and sort_by to rank results server-side.

Input parameters:

- `date` (string): Historical snapshot date (YYYY-MM-DD). Omit for latest per asset class.
- `fields` (string): JSON-encoded array of column names to return. Example: ["ticker", "sector", "market_cap", "pe_ratio", "trend_stage", "ma40", "trend_ma50_slope", "trend_ma_crossover_event", "trend_distance_ma40", "pa…
- `filters` (string, required): JSON-encoded filter array. Each filter: {"field": "column_name", "op": "eq|neq|in|gt|gte|lt|lte", "value": "..."}. Example: [{"field": "momentum_rsi_zone", "op": "in", "value": ["oversold", "deep_ove…
- `limit` (integer): Max results to return. Tier-gated: Starter 25, Plus 100, Pro 500. Default: 20
- `sort_by` (string): Column name to sort results by (e.g. "market_cap", "pe_ratio", "extremes_condition_percentile", "fundamentals_valuation_percentile", "volume_percentile", "sector_oversold_count", "sector_breakout_cou…
- `sort_direction` (string): Sort direction. Default: desc. Use 'asc' for lowest-first (e.g. cheapest valuation percentile).
- `timeframe` (string): Analysis timeframe. Default: daily

Output parameters:

- `data`: The TickerDB API response payload for this tool call.

### `get_schema` (~71 tokens)

Get the schema of all available fields and their valid band values. Use this when the user asks 'what fields are available?', 'what bands does momentum_rsi_zone have?', 'what sectors exist?', or when you need to validate field/band names before calling get_summary with event parameters or get_search with filters.

Output parameters:

- `data`: The TickerDB API response payload for this tool call.

### `get_account` (~86 tokens)

Get your account details including current plan tier, monthly credit limits, and current usage. Response includes tier, limits (monthly_requests, overage_enabled, watchlist_limit, search_results, webhook_urls, history_days), and usage (monthly_requests_used, monthly_requests_remaining, credit_balance for pay-per-use accounts). Also returns scheduled_tier and scheduled_change_at if a plan change is pending.

Output parameters:

- `data`: The TickerDB API response payload for this tool call.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-tickerdb-mcp-server/mcp#diagnostics

## Score history

- 2026-08-03: 75
- 2026-08-02: 76
- 2026-08-01: 75
- 2026-07-31: 75
- 2026-07-30: 69
- 2026-07-29: 69
- 2026-07-28: 69
- 2026-07-27: 68
- 2026-07-26: 67

## Links

- Remote endpoint: https://mcp.tickerdb.com/mcp
- Repository: https://github.com/tickerdb/tickerdb-mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-tickerdb-mcp-server/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-tickerdb-mcp-server/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-tickerdb-mcp-server/mcp