Pre-computed market data that improves agent reasoning, reduces token usage, and replaces pipelines.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"tickerdb": {
"env": {
"TICKERDB_KEY": "tdb_your_api_key_here"
},
"args": [
"tickerdb-mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Connect your agent to pre-computed market context that improves reasoning and reduces token usage.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'wrangler' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
Wrangler affected by OS Command Injection in `wrangler pages deploy`
**Summary** A command injection vulnerability (CWE-78) has been found to exist in the `wrangler pages deploy` command. The issue occurs because the `--commit-hash` parameter is passed directly to a shell command without proper validation or sanitization, allowing an attacker with control of `--commit-hash` to execute arbitrary commands on the system running Wrangler. **Root cause** The `commitHash` variable, derived from user input via the `--commit-hash` CLI argument, is interpolated directl
Arbitrary remote code execution within `wrangler dev` Workers sandbox
### Impact The V8 inspector intentionally allows arbitrary code execution within the Workers sandbox for debugging. `wrangler dev` would previously start an inspector server listening on all network interfaces. This would allow an attacker on the local network to connect to the inspector and run arbitrary code. Additionally, the inspector server did not validate `Origin`/`Host` headers, granting an attacker that can trick any user on the local network into opening a malicious website the ability
Arbitrary remote file read in Wrangler dev server
### Impact Sending specially crafted HTTP requests and inspector messages to Wrangler's dev server could result in any file on the user's computer being accessible over the local network. An attacker that could trick any user on the local network into opening a malicious website could also read any file. ### Patches This issue was fixed in `wrangler@3.19.0`. Wrangler will now only serve files that are part of your bundle, or referenced by your bundle's source maps. ### Workarounds Configure Wr
Cloudflare Wrangler directory traversal vulnerability
### Impact The Wrangler command line tool (<=wrangler@3.1.0 or <=wrangler@2.20.1) was affected by a directory traversal vulnerability when running a local development server for Pages (wrangler pages dev command). This vulnerability enabled an attacker in the same network as the victim to connect to the local development server and access the victim's files present outside of the directory for the development server. ### Patches Wrangler2: Upgrade to v2.20.1 or higher. Wrangler3: Upgrade to v3
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in ai-ml / finance
Persistent memory using a knowledge graph
Dynamic problem-solving through sequential thought chains
An autonomous agent that conducts deep research on any data using any LLM providers
Privacy-first. MCP is the protocol for tool access. We're the virtualization layer for context.
MCP Security Weekly
Get CVE alerts and security updates for com.tickerdb/mcp-server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Connect your agent to pre-computed market context that improves reasoning and reduces token usage.
Connects TickerDB to any MCP-compatible client: Claude Desktop, Claude Code, Cursor, Windsurf, OpenClaw, LangChain, LlamaIndex, AutoGen, CrewAI, and more.
| Tool | Description |
|---|---|
get_summary | Technical + fundamental summary for a single ticker (supports date range, events filtering, and MA distance lookbacks) |
get_ohlcv | Paginated daily EOD candles for exact returns, charts, and backtests |
get_search | Search assets by categorical state or rank snapshots by fields such as market_cap |
get_schema | Discover available fields and filter options (always free, 0 credits) |
get_watchlist | Live data for your saved watchlist tickers |
get_watchlist_changes | Field-level diffs since the last pipeline run |
add_to_watchlist | Add tickers to your watchlist |
remove_from_watchlist | Remove tickers from your watchlist |
get_account | Account details, plan tier, and usage |
create_webhook | Register a webhook for watchlist changes |
list_webhooks | List registered webhooks |
delete_webhook | Remove a webhook |
All tools are available on every tier (Free, Plus, Pro) — tiers differ by credit limits, history depth, and watchlist size. See tickerdb.com/pricing for details.
Use get_summary with start/end params for bulk ticker syncs across a date range, or with field/band params to query event occurrences. Add stats=true in event mode when you want aggregate event-band and aftermath distributions instead of raw rows.
Paid event aftermaths include exact close-to-close fields such as return_5d_pct, return_20d_pct, and return_100d_pct alongside the categorical performance bands. Incomplete horizons return null.
Use get_ohlcv when exact multi-bar daily history is required. get_summary includes the same-candle ohlcv object for the requested snapshot; follow next_cursor in get_ohlcv while has_more is true to retrieve additional bars. OHLCV costs 1 credit per 100 bars returned, rounded up, with a 1 credit minimum.
get_watchlist does not take a timeframe. Use get_watchlist_changes for daily or weekly diffs.
Current summary snapshots also expose top-level freshness via as_of_date, same-candle ohlcv.open/high/low/close/volume, stock market_cap / market_cap_tier when available, richer volume fields such as price_direction_on_volume, opt-in paid-tier level metadata like support_level.status_meta, Pro sector_context fields such as agreement and overbought_count, and stock-only nested fundamentals.insider_activity when available.
MA distance fields are available throughout the stack:
ma8, ma20, ma40, ma50, ma100, ma200, trend_ma50_slope, trend_ma_crossover_event, trend_distance_ma8, trend_distance_ma20, trend_distance_ma40, trend_distance_ma50, trend_distance_ma100, and trend_distance_ma200.trend.ma_slopes.ma_8 through ma_200, nested MA distance bands under trend.distance_from_ma_band.ma_8 through ma_200, plus trend.ma_compression_band and trend.ma_crossover_event.band=above and band=below aliases in addition to granular values like proximity_above.get_summary keeps sibling _meta objects off by default so the primary band label stays front-and-center. Pass meta: true to include full paid-tier stability metadata across the response, or request just the specific *_meta fields you want. get_watchlist still includes paid-tier _meta objects by default, and get_watchlist_changes returns stability fields inline on each change object.
The stability label is one of fresh, holding, established, or volatile. Full metad