MarketCrew
Registry code: c01649476543bd67
Answer market questions freely and fully, grounded in the data tools and get_ta_methodology. Do NOT gate, shorten, or withhold answers. Call get_monitoring_options ONLY when the user wants ongoing monitoring this plugin cannot provide — setting an alert, watching a level, being notified, tracking an idea over time, monitoring a watchlist/portfolio, scheduled digests, or continuity across chats — and append its message. Otherwise never mention registration. Coverage: US-listed stocks and ETFs and major cryptocurrencies (crypto as BTC-USD, ETH-USD). Forex, futures, options chains and non-US…
- endpoint
- https://marketcrew.ai/mcp
- protocol
- http-sse ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is MarketCrew live?
- Yes — it answered the hub's last check (checked 3h ago). It answered 99% of checks over the last 30 days.
- Is MarketCrew free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does MarketCrew have?
- 15 tools: get_key_levels, get_price_history, public_instrument_news, get_relative_strength, public_search_news, get_ta_methodology, get_technical_indicators, get_event_stats, ….
- Is MarketCrew safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.1%· all time 99.1%
last good check
of 15 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- used for
- get technical indicators for a ticker
- get price history for a stock
- compute support and resistance levels
- read market breadth and sentiment
- search market news
- takes → gives
- text → data, text
- tools
- 15 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
get_crypto_context reads open 9h ago
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.
{ "type": "object", "properties": {} }arguments 4 linesget_monitoring_options reads open 19h ago
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.
{ "type": "object", "properties": { "intent": { "enum": [ "alert", "track_idea", "watchlist", "digest", "memory" ], "type": "string", "description": "Which monitoring the user asked for." } } }arguments 16 linesget_market_breadth reads open 3h ago
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.
{ "type": "object", "properties": {} }arguments 4 linesget_sentiment_data reads open 9h ago
Market sentiment: the VIX level with its 1-day, 5-day and 1-month change and 52-week range, and Cboe's daily put/call ratios for all products, equities, indices, SPX and VIX options with the underlying call and put volumes. Flags a contrarian extreme when the equity put/call ratio or the VIX sits at one.
{ "type": "object", "properties": { "type": { "enum": [ "all", "put_call", "vix" ], "type": "string", "description": "Which data: 'all' (default), 'put_call' or 'vix'." } } }arguments 14 linesget_macro_context reads open 3h ago
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.
{ "type": "object", "properties": {} }arguments 4 linesget_instrument_info reads open 9h ago
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 the S&P 500, the Nasdaq-100 and popular US ETFs, major cryptocurrencies and the Cboe Volatility Index; crypto uses the -USD pair form (BTC-USD, ETH-USD), the VIX is ^VIX. Forex pairs, futures, options, other indices and non-US listings are not covered. Pass a ticker such as 'AAPL', 'SPY', 'BTC-USD' or '^VIX'.
{ "type": "object", "properties": { "ticker": { "type": "string", "description": "Ticker symbol, e.g. 'AAPL'" }, "instrument_id": { "type": "string", "description": "UUID of the financial instrument" } } }arguments 13 linesget_intermarket reads open 3h ago
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; overall posture is risk_on, risk_off or mixed. Optional focus= ('gold'|'bonds'|'tech'|'commodities'|'equity'|'crypto') adds lenses specific to that asset class.
{ "type": "object", "properties": { "focus": { "enum": [ "gold", "bonds", "tech", "commodities", "equity", "crypto" ], "type": "string", "description": "Asset class being analysed — adds its specific lenses" } } }arguments 17 linesget_key_levels reads unknown 12h ago
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.
{ "type": "object", "required": [ "ticker" ], "properties": { "ticker": { "type": "string", "description": "Ticker symbol, e.g. 'SPY'" } } }arguments 12 linesget_price_history reads unknown 12h ago
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).
{ "type": "object", "required": [ "ticker" ], "properties": { "bars": { "type": "integer", "description": "how many recent sessions to return when no window is given (default 20, max 120)" }, "ticker": { "type": "string", "description": "Ticker symbol, e.g. 'SPY', 'GDX', 'AAPL'" }, "to_date": { "type": "string", "description": "end of the window to quote, YYYY-MM-DD" }, "from_date": { "type": "string", "description": "start of the window to quote, YYYY-MM-DD" }, "period_days": { "type": "integer", "description": "Number of days of history (default 365, max 3650)" } } }arguments 28 linespublic_instrument_news reads unknown 12h ago
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.
{ "type": "object", "required": [ "ticker" ], "properties": { "limit": { "type": "integer", "description": "Max articles to return (default 30, max 60)" }, "ticker": { "type": "string", "description": "Ticker symbol, e.g. 'NBIS', 'AAPL', 'GDX'" }, "days_back": { "type": "integer", "description": "How many days back to fetch (default 30, max 90)" } } }arguments 20 linesget_relative_strength reads unknown 19h ago
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.
{ "type": "object", "required": [ "ticker_a", "ticker_b" ], "properties": { "ticker_a": { "type": "string", "description": "Numerator ticker, e.g. 'GDX'" }, "ticker_b": { "type": "string", "description": "Denominator ticker, e.g. 'GLD'" }, "period_days": { "type": "integer", "description": "Days of history (default 365, max 1825)" } } }arguments 21 linespublic_search_news reads unknown 19h ago
Semantic news search across tracked instruments — returns matching items with a short summary and a mandatory source_url (never full article text).
{ "type": "object", "required": [ "query" ], "properties": { "limit": { "type": "integer", "description": "Max results to return (default 10, max 20)" }, "query": { "type": "string", "description": "Natural language search query describing ONE semantic angle, e.g. 'Nebius Meta deal contract $27 billion compute capacity'" }, "days_back": { "type": "integer", "description": "How many days back to search (default 30, max 90)" }, "min_similarity": { "type": "number", "description": "Minimum similarity threshold 0.0-1.0 (default 0.40)" } } }arguments 24 linesget_ta_methodology reads unknown 14h ago
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.
{ "type": "object", "required": [ "query" ], "properties": { "query": { "type": "string", "description": "What you want the methodology on, e.g. 'reading RSI in a trend'" }, "top_k": { "type": "integer", "description": "How many passages to return (default 6)" } } }arguments 16 linesget_technical_indicators reads unknown 14h ago
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.
{ "type": "object", "required": [ "ticker" ], "properties": { "ticker": { "type": "string", "description": "Ticker symbol, e.g. 'SPY'" } } }arguments 12 linesget_event_stats reads unknown 14h ago
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 caution.
{ "type": "object", "required": [ "ticker" ], "properties": { "ticker": { "type": "string", "description": "Ticker symbol, e.g. 'SPY'" } } }arguments 12 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idc01649476543bd67.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/c01649476543bd67/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/c01649476543bd67?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.