Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

GammaRips Options Intelligence

REMOTE · MCP.GAMMARIPS.COM · SCANNED SEP 22

Anti-firehose options-flow data for AI agents: curated daily pool, features, realized outcomes.

0 this week 83 Trust /100
Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security74
Transport & Reachability100
Schema Quality & AI Usability74
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 4347 tokens (~483/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (56% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

How do I install the GammaRips Options Intelligence MCP server?

GammaRips Options Intelligence is a hosted endpoint at https://mcp.gammarips.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.gammarips.com

# add to Claude Code
claude mcp add --transport http devdizzle-gammarips 'https://mcp.gammarips.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "devdizzle-gammarips": {
      "url": "https://mcp.gammarips.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "devdizzle-gammarips": {
      "type": "http",
      "url": "https://mcp.gammarips.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.devdizzle-gammarips]
url = "https://mcp.gammarips.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "devdizzle-gammarips": {
      "type": "remote",
      "url": "https://mcp.gammarips.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add devdizzle-gammarips --url 'https://mcp.gammarips.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  devdizzle-gammarips:
    url: "https://mcp.gammarips.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "devdizzle-gammarips": {
      "Transport": "http",
      "Url": "https://mcp.gammarips.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add devdizzle-gammarips -t streamable-http -u 'https://mcp.gammarips.com/mcp'
// mcp.json
{
  "mcpServers": {
    "devdizzle-gammarips": {
      "type": "http",
      "url": "https://mcp.gammarips.com/mcp"
    }
  }
}

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

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 1 Sept 26 +7
    • Authorization: unverified → partial security
    • Tool “get_daily_report” changed its title: Daily Report cosmetic
    • Tool “get_liquidity” changed its title: Contract Liquidity cosmetic
    • Tool “get_market_calendar_status” changed its title: Market Calendar Status cosmetic
    • Tool “get_playbook” changed its title: Methodology Playbook cosmetic
    • Tool “get_pool” changed its title: Candidate Pool cosmetic
    • Tool “get_regime_context” changed its title: Market Regime Context cosmetic
    • Tool “get_signal” changed its title: Signal Detail cosmetic
    • Tool “query_outcomes” changed its title: Realized Outcomes cosmetic
    • Tool “replay_contract” changed its title: Contract Price Replay cosmetic
  • 29 Aug 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 27 Aug 26 0
    • Tool “get_pool” rewrote its description, which is the text the model reads security
  • 26 Aug 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 +1
    • Stability: 0.97 → pass security
  • 21 Aug 26 0
    • Tool “get_pool” rewrote its description, which is the text the model reads security
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 8 Aug 26 0
    • Tool “query_outcomes” rewrote its description, which is the text the model reads security
    • Schema quality: good → poor functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 22 Sept 2026 · Probed https://mcp.gammarips.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.gammarips.com CN=WR3,O=Google Trust Services,C=US 12 Sept 2026 11 Dec 2026 RSA 2048 SHA256-RSA af6127ca962f953d09bfb0e33ca3a3f1
SANs: mcp.gammarips.com
CN=WR3,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7ff005a91568d63abc22861684aa4b5a
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.gammarips.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
gammarips.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.gammarips.com/mcp Verified 200
http (plaintext) http://mcp.gammarips.com/mcp HTTPS enforced 302 https://mcp.gammarips.com/mcp
MCP tools · 9 exposed · ~4,126 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_daily_report ~166

The daily intelligence report. Two `view`s: * view="report" (DEFAULT) — the full report (title, markdown content, scan_date) for `date`, or the most recent report if `date` is omitted. * view="list" — recent reports, most recent first (scan_date, title, created_at), titles deduped. Use `limit`. Args: date: report date YYYY-MM-DD (report view; default: most recent). view: "report" (default) | "list". limit: list view — how many reports (default 10, clamped 1-30).

NameTypeReqDescription
date
limitinteger
viewstring

No output schema declared.

No examples provided.

get_liquidity ~369

FRESH (entry-day) liquidity — the read the pool's session-frozen `recommended_oi`/`recommended_volume` cannot give you (the overnight sweep only becomes OI the next morning). Two modes, chosen by whether you pass a single `contract`: * `contract` given — ONE contract's snapshot: open interest, session volume, last trade, day range, underlying price, greeks. Cache-first (the engine re-reads the pool every ~10 min in market hours); pass live=true to force a fresh upstream fetch or read a contract NOT in today's pool. * `contract` omitted — the WHOLE current pool (or your `contracts` shortlist, max 60) in ONE call — the batch companion for the ~10:00 ET decision window. Most-recent read per contract with explicit `as_of`. Deliberately serves NO bid/ask/mid/spread (not available on the current data plan — absent, not NULL). Judge fill risk from open_interest (updates once each morning), day_volume (live session), last_trade recency, and the day range. Args: contract: OCC ticker for the single-contract mode (verbatim from the pool's `recommended_contract`). Omit for the whole-pool batch. scan_date: pool date YYYY-MM-DD (batch mode; default: latest pool). contracts: optional shortlist filter for the batch mode (max 60). live: single-contract mode — force a fresh upstream fetch.

NameTypeReqDescription
contract
contracts
liveboolean
scan_date

Structured output declared, but exposes no named fields.

No examples provided.

get_market_calendar_status ~130

Market-calendar reference. Two `view`s: * view="status" (DEFAULT) — is the US equity market open today, plus the next open/close, holiday, and early-close flags (NYSE calendar, deterministic — no "is the market open?" hallucination). * view="scan_dates" — which recent scan dates have GammaRips data, with per-date signal counts (the pool's data-availability calendar). Args: view: "status" (default) | "scan_dates".

NameTypeReqDescription
viewstring

No output schema declared.

No examples provided.

get_playbook ~300

Methodology + reference, versioned server-side (re-fetch rather than caching long-term). Arg-driven: * `field` given — the plain-English DEFINITION + role of a signal field (deterministic lookup, no LLM). e.g. field="mom_60". The response's `available_fields` lists every documented field. * `name` given — a methodology playbook (markdown) by name, OR two special reference pages: - name="schema" (or "data-contract") -> the machine-readable substrate DATA CONTRACT: every outcome/label column with its leakage classification (feature|label|opportunity| regime_telemetry|identity) and as-of boundary. Only `feature` columns are safe as selection inputs. - any other name -> the playbook markdown (start-here, daily-workflow, run-your-own-tournament, exit-lab, leakage-and-data-contract, changelog). * neither — the CATALOG of published playbooks (name/title/summary), plus a pointer to the field dict (`field=`) and schema page. Args: name: playbook name, or "schema"/"data-contract" for the data contract. field: a signal field name to explain (overrides `name`).

NameTypeReqDescription
field
name

No output schema declared.

No examples provided.

get_pool ~791

The GammaRips candidate pool for a scan date. One tool, four `view`s: * view="enriched" (DEFAULT) — the AI-enriched pool: news, technicals, catalyst, the recommended contract (an OTM call chosen on contract liquidity), and the 60-day momentum feature `mom_60`. Funnel for scan_date >= 2026-08-24 (liquid-universe era): the 100 most liquid optionable names, BULLISH only, one call each, roughly 40-50 rows. Liquidity decides membership, not unusual activity; the $500K UOA floor is retired and `overnight_score>=1` is a cosmetic floor. Earlier scan dates come from the prior UOA-gated funnel (UOA>$500K, top-50 BULLISH); the two eras are not one population. This is the daily candidate set your agent reasons over to its OWN contract (see get_playbook("run-your-own-tournament")). Served from a leakage-safe view (forward-outcome columns physically stripped); `summary=True` gives ~21 decision columns, `fields=[...]` a strict projection, `summary=False` full rows, `offset` pages. * view="raw" — the wide overnight scan BEFORE the pool cut (the ranked liquid universe for scan_date >= 2026-08-24; the market-wide unusual-activity scan for earlier dates). Honors `direction`, `min_score`, `ticker`, `limit`. * view="features" — point-in-time FEATURE VECTORS from the leakage-safe allowlist view `enriched_features_v1` (identity + features + cohort metadata only; no outcome/label/telemetry column can appear). The quantitative substrate for joining against query_outcomes. Lags the live pool by ~1-2 trading days. * view="preview" — a minimal public teaser (ticker, direction, score, headline, directional UOA) for the most recent scan; no contract specifics or thesis. TIER: view="preview" is FREE (no key). The enriched / raw / features views are the paid product — they require an a…

NameTypeReqDescription
direction
fields
limitinteger
min_scoreinteger
offsetinteger
scan_date
summaryboolean
ticker
viewstring

No output schema declared.

No examples provided.

get_regime_context ~230

Point-in-time market-regime context for a scan date: VIX close, VIX3M, SPY trend state, and the 5-day VIX delta — all as-of <= scan_date (the selection point, leakage-safe), plus the engine's regime safety rail evaluated on those values. The rail: the engine fail-closes (no trade) when spot VIX > VIX3M (backwardation — the market pricing imminent volatility is an adverse regime for short-dated directional longs). Served from the labeled substrate, which lags the live pool by ~1-2 trading days. Values are constant per scan_date. Args: scan_date: YYYY-MM-DD. Defaults to the latest scan date carrying regime features. Returns: {scan_date, vix_at_scan, vix3m_at_enrich, spy_trend_at_scan, vix_5d_delta_at_scan, regime_rail_pass, rail_definition}

NameTypeReqDescription
scan_date

Structured output declared, but exposes no named fields.

No examples provided.

get_signal ~358

Deep dive on a single ticker/contract. Two `view`s: * view="detail" (DEFAULT) — the full enriched signal for one ticker: thesis, catalyst, the recommended contract, and point-in-time features (leakage-safe view). `full=true` includes the long narrative (news_summary, flow_intent_reasoning). If the ticker isn't in the pool for the date, the error lists the dates on which it does appear. * view="earnings" — the doctrine earnings-window check (RM-003): the next scheduled earnings date and whether it lands ON OR BEFORE the contract expiration (`earnings_in_window`). The engine applies this rail only at its own pick time, NOT in the pool, so pool rows CAN carry earnings-window names — check every candidate yourself. Pass the pool's `recommended_contract` and both ticker and expiration are derived. FAIL-CLOSED: unknown date -> earnings_in_window=null, treat as in-window. Args: ticker: underlying symbol (required for detail; optional for earnings if `contract` is given). view: "detail" (default) | "earnings". scan_date: detail only — YYYY-MM-DD (default: latest for the ticker). full: detail only — include the long narrative fields. expiration: earnings only — option expiration YYYY-MM-DD to test. contract: earnings only — OCC ticker supplying ticker+expiration.

NameTypeReqDescription
contract
expiration
fullboolean
scan_date
ticker
viewstring

Structured output declared, but exposes no named fields.

No examples provided.

query_outcomes ~1,355

The realized-outcome + receipts substrate behind the engine. One tool, nine `view`s. Whole-pool composites under any FIXED exit are NEGATIVE by construction — these are a research surface (how outcomes distribute across features and exits), never a strategy track record. * view="labels" (DEFAULT) — row-level realized bracket LABELS joined to point-in-time features. horizon "same_day" (live V7.1 GIGO +40/-30) or "3d" (legacy +80/-60) — never pooled. NULL-label and illiquid rows excluded (counts in meta). `aggregate_only=True` returns summary stats instead of rows. Filters: scan_date_from/to, ticker, delta_min/max, min_overnight_score, exit_reason. * view="summary" — grouped aggregates over the labeled pool. `group_by` one of none|delta_bucket|overnight_score|premium_score|exit_reason| day_of_week|moneyness_bucket. * view="surface" — the OPPORTUNITY SURFACE: per-contract realized MFE/MAE excursions with NO exit applied (profit potential, exit free). Uses scan_date OR a `days` lookback, `ticker`, `delta_min/max`, `include_open`. `aggregate_only=True` returns MFE/MAE quantiles over the FULL filtered set — use it for exit design. The row mode is capped at 200 and truncates oldest-first WITHIN a scan_date, so its oldest date is a highest-MFE-only slice; it reports `truncated`, `matched_rows`, and `partial_scan_date` so you can see that happen. * view="harvest" — the touch-probability curve: P(premium touched +X%) with CIs, day-of-peak buckets, stop-touch rates. `targets`, `stops`, date range, delta band. * view="exit_rule" — RESEARCH-ONLY "bring your exit, we score it": rule="bracket" (target_pct/stop_pct) or rule="trailing" (trail_pct, activation_pct) scored against the surface / minute tape. * view="signal_performance" — UNDERLYING-STOCK direction outcomes for the br…

NameTypeReqDescription
activation_pctnumber
aggregate_onlyboolean
daysinteger
delta_max
delta_min
direction
exit_reason
group_bystring
horizon
include_openboolean
limitinteger
min_overnight_score
min_premium_score
outcome
policy_version
rulestring
scan_date
scan_date_from
scan_date_to
stop_pctnumber
stops
target_pct
targets
ticker
trail_pct
viewstring

Structured output declared, but exposes no named fields.

No examples provided.

replay_contract ~427

Raw option price data for YOUR OWN entry/exit rule. This server does NOT simulate or validate exits — it returns bars (the RM-002/RM-004 boundary). Two `granularity` modes: * granularity="minute" (DEFAULT) — the intraday minute path for one session (`date` required). Optionally pass a bracket (target_pct/ stop_pct, PERCENT of the 10:00 ET anchor) and the response also reports the exact FIRST-CROSSING sequence measured from the tape. Pool excursion windows are served from the engine's minute-path table; anything else falls back to an upstream minute fetch. * granularity="day" — the DAILY mark series (OHLCV) over a date range, to mark a live paper position day by day or replay a closed one. Uses `from_date`/`to_date` (span capped at 120 days); `date` is ignored. Option tape is THIN — minutes/days with no prints have no bar; treat touch times as evidence, not tick-perfect truth. Paper-trade research data; not investment advice. Args: contract: OCC option ticker (e.g. "O:UNIT260717C00030000"). date: minute mode — ET session date YYYY-MM-DD (required). granularity: "minute" (default) | "day". target_pct: minute mode — optional +X% level for first-crossing. stop_pct: minute mode — optional -Y% level for first-crossing. from_date: day mode — start YYYY-MM-DD (default: 30d before to_date). to_date: day mode — end YYYY-MM-DD inclusive (default: today ET).

NameTypeReqDescription
contractstringyes
date
from_date
granularitystring
stop_pct
target_pct
to_date

Structured output declared, but exposes no named fields.

No examples provided.

Common questions

What is the GammaRips Options Intelligence MCP server?

GammaRips Options Intelligence is an MCP server listed in the public MCP registry as io.github.DevDizzle/gammarips. Anti-firehose options-flow data for AI agents: curated daily pool, features, realized outcomes. This page covers its hosted endpoint (https://mcp.gammarips.com/mcp).

Is the GammaRips Options Intelligence MCP server safe to use?

GammaRips Options Intelligence scores 83 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the GammaRips Options Intelligence MCP server expose?

GammaRips Options Intelligence exposes 9 tools: get_pool, get_signal, get_liquidity, query_outcomes, replay_contract, and 4 more. Their descriptions and schemas cost roughly 4,126 tokens of context every time the server is loaded.

Does the GammaRips Options Intelligence MCP server require authentication?

No. We connected to GammaRips Options Intelligence without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the GammaRips Options Intelligence MCP server still maintained?

GammaRips Options Intelligence is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.