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

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

Available components

−82 this week 0 Trust /100

Last scanned (2 days ago)

Scores higher than 0% of remote servers

Unreachable for 7 days in a row. Last reached 29 Oct 2026.

Category Finance and Payments

Dead

Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.

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 Security0
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

What we tested

Checks we ran (2)

  • DNSSEC
  • Transport

Checks we could not complete (9)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • TLS certificate in Endpoint SecurityTLS not yet verified: we couldn't open a connection to check the certificate.
  • Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement.
  • HSTS header in Endpoint SecurityHSTS not yet verified: we couldn't read the response headers to check for it.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 5 Nov 26 −16

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 4 Nov 26 −17

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 3 Nov 26 −16

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 2 Nov 26 −17

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 1 Nov 26 −16

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 30 Oct 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • HSTS header: fail → unverified ▼ security
    • Stability: pass → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • HTTPS: pass → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Schema quality: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 3 Oct 26 −1
    • Tool “query_outcomes” rewrote its description, which is the text the model reads security
  • 30 Sept 26 0
    • Tool “get_market_calendar_status” rewrote its description, which is the text the model reads security
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 5 Nov 2026 · Probed https://mcp.gammarips.com/mcp

TLS unreached
DNSSEC insecure

Validation of mcp.gammarips.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
gammarips.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive

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 Unreachable
http (plaintext) http://mcp.gammarips.com/mcp Inconclusive 404
MCP tools · 9 exposed · ~4,390 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 ~395

Market-calendar reference. Three `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 raw scan's data-availability calendar). * view="freshness" — is the pool you are about to trade the right pool? Returns schema "pool-freshness/1": expected_scan_date (the last NYSE session before today), each pipeline stage (scan, enrichment, liquidity) with its latest date, row count for the expected date, and ok (true / false = overdue / null = could not check); the enrichment stage also gives expected_rows (the rows the enrichment filter must produce, so rows < expected_rows is a partial pool); the scan_date get_pool(view="enriched") serves by default (pool_scan_date) and its row count (pool_rows), `fresh`, and machine `reasons` (scan-stale, enrichment-stale, liquidity-stale, pool-stale, pool-empty, unknown-<stage|pool>). Fail-closed: an unknown is never fresh. A stage not yet due reports ok=true, due=false; before the 06:00 ET enrichment, fresh is false with reason pool-stale because the next pool does not exist yet. No row floor is applied; apply your own to pool_rows. Cached up to 60 s. Args: view: "status" (default) | "scan_dates" | "freshness".

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,354

The realized-outcome history behind the pool: use it to set a target and a stop from what past pool contracts actually did. One tool, nine `view`s. A pool-wide result under one fixed exit describes that one rule, not a forecast for the plan you build. * 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 broad pool (NOT option…

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.

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'
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 0 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,390 tokens of context every time the server is loaded.

Does the GammaRips Options Intelligence MCP server require authentication?

Its publisher declares no required credentials for GammaRips Options Intelligence. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the GammaRips Options Intelligence MCP server still maintained?

GammaRips Options Intelligence has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 29 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the GammaRips Options Intelligence MCP server?

VerifyMCP ran 2 checks on GammaRips Options Intelligence, covering DNSSEC and Transport. 9 items could not be completed, a gap on our side rather than a finding about GammaRips Options Intelligence: TLS certificate, Authorization, HTTPS, HSTS header and 5 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.