Model Context Protocol (MCP) server for freee API integration
Market Data is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Live market data & technical analysis for US stocks, ETFs and crypto. Read-only, no signup.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http marketcrew-market-data-mcp https://marketcrew.ai/mcp
# 2 — ask your agent for something these tools do
# get_price_history, get_technical_indicators, get_relative_strength and 12 more
Market Data costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http marketcrew-market-data-mcp https://marketcrew.ai/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
15 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Get daily OHLCV price history for a ticker: open/high/low/close/volume. Use period_days to control how far back (default 365, max 3650).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ticker | string | yes | Ticker symbol, e.g. 'SPY', 'GDX', 'AAPL' |
| from_date | string | no | start of the window to quote, YYYY-MM-DD |
| to_date | string | no | end of the window to quote, YYYY-MM-DD |
| bars | integer | no | how many recent sessions to return when no window is given (default 20, max 120) |
| period_days | integer | no | Number of days of history (default 365, max 3650) |
Calculate technical indicators for a ticker: SMA(50/200), RSI(14), MACD, ATR(14), ADX(14) trend strength, Stochastic(14,3), volume (OBV trend + volume vs 20-day average), RSI/price divergence, Golden/Death Cross, and RSI regime. Computed from daily price history.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ticker | string | yes | Ticker symbol, e.g. 'SPY' |
Relative strength of one ticker against another as a price ratio A/B (e.g. GDX/GLD, HYG/LQD, XLK/SPY, NVDA/SPY): how far the ratio sits above or below its 50- and 200-day averages, the ratio's RSI and trend, recent values, and a one-line verdict on which side is leading.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ticker_a | string | yes | Numerator ticker, e.g. 'GDX' |
| ticker_b | string | yes | Denominator ticker, e.g. 'GLD' |
| period_days | integer | no | Days of history (default 365, max 1825) |
Compute key price levels for a ticker: support/resistance zones (clustered swing highs/lows with touch counts = how often price reacted there), nearby round numbers, 50/200-day moving averages, and the 52-week high/low. Returns nearest levels above (resistance) and below (support) with distance %. Use these for concrete trigger/target/invalidation levels.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ticker | string | yes | Ticker symbol, e.g. 'SPY' |
Intermarket compass — a first-pass read of the market environment through price-ratio lenses: asset-class rotation (bonds vs stocks, commodities), risk appetite (high-yield vs investment-grade credit, small vs large caps, cyclicals vs defensives), defensive flows (gold, utilities, yield-curve proxy) and the dollar. Each lens reports rising/falling vs its 50-day average plus the 20-day change; over
| Parameter | Type | Required | Notes |
|---|---|---|---|
| focus | string | no | Asset class being analysed — adds its specific lenses |
S&P 500 market breadth: the percentage of index members above their 50-day and 200-day moving averages, with RSI, trend and 52-week range for each breadth series. A gauge of how broad the current advance or decline is.
No parameter schema on file.
Market sentiment from Cboe's daily options statistics: put/call ratios for all products, equities, indices, SPX and VIX options, with the underlying call and put volumes, plus a contrarian flag when the equity put/call ratio sits at an extreme.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | no | Which data: 'all' (default) or 'put_call' — both return the Cboe put/call set. |
Get macro market context: sector P/E ratios, sector performance, US Treasury rates (2Y/10Y/30Y), CPI inflation data. Also provides key inter-market ratios (HYG/LQD, TLT/SPY) from our price data.
No parameter schema on file.
Crypto market context for a technical read: BTC/ETH dominance and total/alt market cap, Fear & Greed sentiment, perp funding rate & open interest (positioning/leverage), and the Stablecoin Supply Ratio (dry powder). Use ONLY when analysing crypto assets (BTC, ETH, crypto ETFs). Background context, not the primary signal.
No parameter schema on file.
Current snapshot of one instrument: price and recent changes, session state (regular, pre-market, after-hours, closed), 52-week range, and market cap, sector and next earnings date where they apply. Covers US-listed stocks and ETFs and major cryptocurrencies; crypto uses the -USD pair form (BTC-USD, ETH-USD). Forex pairs, futures, options and non-US listings are not covered. Pass a ticker such as
| Parameter | Type | Required | Notes |
|---|---|---|---|
| instrument_id | string | no | UUID of the financial instrument |
| ticker | string | no | Ticker symbol, e.g. 'AAPL' |
Historical base rates for the technical events firing on a ticker today (e.g. RSI below 30, golden/death cross, new 52-week high/low). For each active event: the forward returns (1w/1m/3m/6m/1y) seen historically after similar events across the US universe, with the sample size and an unconditional baseline to compare against. Answers 'what usually happened after this'; small samples warrant cauti
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ticker | string | yes | Ticker symbol, e.g. 'SPY' |
Latest news for a ticker — headline, a short summary and a mandatory source_url to the original article (never the full third-party text). Use to ground a market read in recent, attributable news.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ticker | string | yes | Ticker symbol, e.g. 'NBIS', 'AAPL', 'GDX' |
| days_back | integer | no | How many days back to fetch (default 30, max 90) |
| limit | integer | no | Max articles to return (default 30, max 60) |
Semantic news search across tracked instruments — returns matching items with a short summary and a mandatory source_url (never full article text).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Natural language search query describing ONE semantic angle, e.g. 'Nebius Meta deal contract $27 billion compute capacity' |
| days_back | integer | no | How many days back to search (default 30, max 90) |
| limit | integer | no | Max results to return (default 10, max 20) |
| min_similarity | number | no | Minimum similarity threshold 0.0-1.0 (default 0.40) |
Look up MarketCrew's distilled technical-analysis methodology — our own synthesized notes on how to read indicators, structure, levels and regime — to ground an answer in a consistent framework. Returns short passages in our words with relevance scores.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | What you want the methodology on, e.g. 'reading RSI in a trend' |
| top_k | integer | no | How many passages to return (default 6) |
Returns available options for ongoing monitoring — price alerts, idea tracking, watchlist monitoring, scheduled digests — with setup instructions and channels (email/Telegram). Call only when the user asks for ongoing monitoring or notifications; never needed to answer a question.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| intent | string | no | Which monitoring the user asked for. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Market Data or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Market Data can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.