← All servers

Dr. NoVo

warnings

novo-options.trade

Dealer gamma maps for SPY, QQQ, IWM and 90+ cryptos, plus NoVo's own session record. 20 free tools.

https://novo-options.trade/api/mcpWebsiteNo authMCP 2025-06-18v1.40.0last checked 12 Oct 2026spoke MCP on 1 of 1 check (30 days)initialize in 346 ms

Will my client connect?

Decided from what the probe found at the endpoint, and from what each client's own documentation says it can complete. Every row carries the day that documentation was read.

✓Claude CodeConnects

The endpoint answers an anonymous handshake, so no credential is needed.

claude mcp add --transport http dr-novo https://novo-options.trade/api/mcp

Claude Code docs · read on 2026-08-30

✓Claude (claude.ai & Desktop)Connects

The endpoint answers an anonymous handshake, so no credential is needed.

Settings → Connectors → Add custom connector, then paste https://novo-options.trade/api/mcp.

Claude (claude.ai & Desktop) docs · read on 2026-08-30

✓ChatGPTConnects

The endpoint answers an anonymous handshake, so no credential is needed.

Settings → Apps → Advanced settings → Developer mode, then create a connector pointing at https://novo-options.trade/api/mcp.

ChatGPT docs · read on 2026-08-30

✓CursorConnects

The endpoint answers an anonymous handshake, so no credential is needed.

{
  "mcpServers": {
    "dr-novo": {
      "url": "https://novo-options.trade/api/mcp"
    }
  }
}

Cursor docs · read on 2026-08-30

✓VS Code (Copilot)Connects

The endpoint answers an anonymous handshake, so no credential is needed.

{
  "servers": {
    "dr-novo": {
      "type": "http",
      "url": "https://novo-options.trade/api/mcp"
    }
  }
}

VS Code (Copilot) docs · read on 2026-08-30

How to authenticate

Checked against the endpoint by our probe on 12 Oct 2026. These are the capabilities the server advertises, not a prediction about any particular client.

Scheme	No auth
Protected-resource metadata	✕Not found Without it a client has to guess where the authorization server lives.
Anonymous access	Handshake succeeds; 40 tools listable
Credentials demanded in prose	✕get_crypto_map, get_crypto_depth, read_crypto_regime, get_gamma_profile, get_session_history, get_crypto_breadth, get_stocks_onchain, get_robinhood_trending, get_prediction_markets, get_perps, get_perp_history, get_implied_open, get_stock_tokens, get_eye_readings, get_equity_map, get_base_rates, get_crypto_screen These tools are listed anonymously and their own descriptions ask for an account or key, but no challenge is issued — so a client has nothing to act on and the refusal arrives as a tool error.

What the probe found

warningTools needing credentials are listed without a challenge

17 of the 40 tools listed anonymously say in their own descriptions that they need an account or a key (get_crypto_map, get_crypto_depth, read_crypto_regime, get_gamma_profile, get_session_history, get_crypto_breadth, get_stocks_onchain, get_robinhood_trending, get_prediction_markets, get_perps, get_perp_history, get_implied_open, get_stock_tokens, get_eye_readings, get_equity_map, get_base_rates, get_crypto_screen), but the endpoint issued no WWW-Authenticate challenge. The requirement is stated only in prose, so a call reaches the tool and comes back as a tool error instead of an authorization step.

Tools

ask_novocancel_alertcreate_alertget_alertsget_base_ratesget_congress_tradesget_crowd_sentimentget_crypto_breadthget_crypto_coinget_crypto_depthget_crypto_mapget_crypto_screenget_crypto_sweepget_daily_strikeget_dealer_levelsget_earnings_datesget_economic_calendarget_equity_mapget_eye_readingsget_futures_positioningget_gamma_profileget_implied_openget_market_pulseget_moversget_perp_historyget_perpsget_prediction_marketsget_quotesget_retail_chatterget_robinhood_trendingget_sector_heatmapget_session_historyget_short_volumeget_stock_tokensget_stocks_onchainget_ticker_briefget_volatility_recordget_wire_newsread_crypto_regimesearch_journal

Contract history

12 Oct 2026v1.40.0first recorded contract

Watch this server

Save its public contract as a baseline and manage breaking-change email alerts.

Own this server?

Sign in to claim this listing by proving control of its host.

Status badge

Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.

[![MCP status](https://mcpi.app/servers/dr-novo/badge.svg)](https://mcpi.app/servers/dr-novo)