GammaRips Options Intelligence MCP server
io.github.DevDizzle/gammaripsDevDizzlestreamable-httpv4.6.0Scanned
Nightly Combo A options dataset, 10-min liquidity snapshots, and 3-day excursion history for agents.
9 tools: 1 change things and 8 only read.
- Reads private data · 1
- Reads text others write · 2
- Can send data out · 0
- 2 findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the GammaRips Options Intelligence MCP server can do
The GammaRips Options Intelligence MCP server is published by the GitHub account DevDizzle. It has 9 tools. It can create or change data (1 tool: replay_contract), but cannot delete data. 8 tools only read.
1 tool reads private data (get_market_calendar_status); 2 tools bring in text other people can write (get_liquidity and replay_contract).
The fixed checks matched 2 findings (long-description). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 16, 2026, version 4.6.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
9 tools
Changes things 1Claude Code: ask
replay_contractRaw option price data for YOUR OWN entry/exit rule.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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).
Annotations the server declares
- title: Contract Price Replay
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
Only reads 8Show 8 read-only tools
get_daily_reportThe daily intelligence report.No findings
Why it is in this group
- The name "get_daily_report" says "get": a word for reading.
Description, as the server wrote it 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).
Annotations the server declares
- title: Daily Report
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_liquidityFRESH (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).Reads text others writeNo findings
Why it is in this group
- The name "get_liquidity" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Contract Liquidity
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
get_market_calendar_statusMarket-calendar reference.Reads private dataNo findings
Why it is in this group
- The name "get_market_calendar_status" says "get": a word for reading.
What it can reach
- private-dataThe name "get_market_calendar_status" says "get" and "calendar": it reads calendars.
- private-dataThe description's first sentence says "calendar": it reads calendars.
Description, as the server wrote it 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".
Annotations the server declares
- title: Market Calendar Status
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_playbookMethodology + reference, versioned server-side (re-fetch rather than caching long-term).No findings
Why it is in this group
- The name "get_playbook" says "get": a word for reading.
Description, as the server wrote it 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`).
Annotations the server declares
- title: Methodology Playbook
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_poolThe GammaRips candidate pool for a scan date.1 finding
Why it is in this group
- The name "get_pool" says "get": a word for reading.
Findings
- Info
The description is 3,120 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...strict column projection. offset: enriched only — pagination offset."
Description, as the server wrote it 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 3-contract public sample teaser for the most recent scan (3 sample contracts, total pool count that passed today's filter, `gated=True`, and an `upgrade_notice` with a link to https://gammarips.com/pricing). TIER: view="preview" is FREE (no key, 3-contract sample). The enriched / raw / features views are the paid product — they require an active Pro subscription ($29/mo); an anon/free call to them returns `subscription_required` (get_pool(view='preview') is named as the free entry point). Liquidity caveat (all views): `recommended_oi`/`recommended_volume` are scan-time snapshots, not live values; `recommended_spread_pct` is permanently NULL on the current data plan — re-check with get_liquidity. Args: view: "enriched" (default) | "raw" | "features" | "preview". scan_date: YYYY-MM-DD (default: latest available scan for the view). direction: "bull"/"bear" prefix filter (enriched / raw). ticker: exact ticker filter (enriched / raw / features). min_score: overnight_score floor (raw view only; clamped 0-10). limit: max rows (enriched/raw clamp 1-50, features 1-100, preview 1-3). summary: enriched only — True=compact columns, False=full rows. fields: enriched only — explicit strict column projection. offset: enriched only — pagination offset.
Annotations the server declares
- title: Candidate Pool
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_regime_contextPoint-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 t…No findings
Why it is in this group
- The name "get_regime_context" says "get": a word for reading.
Description, as the server wrote it 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}
Annotations the server declares
- title: Market Regime Context
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_signalDeep dive on a single ticker/contract.No findings
Why it is in this group
- The name "get_signal" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Signal Detail
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
query_outcomesThe realized-outcome history behind the pool: use it to set a target and a stop from what past pool contracts actually did.1 finding
Why it is in this group
- The name "query_outcomes" says "query": a word for reading.
Findings
- Info
The description is 4,888 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...oting any number from it. min_premium_score: performance view floor."
Description, as the server wrote it 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 PnL). Filters scan_date, ticker, direction, outcome. * view="win_rate" — aggregate UNDERLYING-direction win rate over `days` (NOT option PnL; headline key carries its universe). * view="positions" — history of a RETIRED engine test: closed paper trades from the engine's former one-pick-a-day tournament under one fixed exit (retired 2026-09-28). Not the product and not the pool; do not use it to judge the pool. Row-level, over `days`, `limit`. * view="performance" — aggregate of that retired test over `days` (`direction`, `min_premium_score`, `policy_version`). Same caveat: history of one retired rule, not a GammaRips result. When it has no closed trades, every aggregate is `null` and `total_trades` is 0. All returns are FRACTIONS (0.40 = +40%). Realized data serves closed windows only. Paper-traded research data; not investment advice. Args: view: which surface (see above). Default "labels". horizon: "same_day" | "3d" (labels/summary/exit_rule). If omitted, the native default per view is used: labels/summary => "same_day" (the live GIGO policy), exit_rule => "3d" (its excursion window). group_by: summary grouping dimension. scan_date / scan_date_from / scan_date_to: date filters (per view). ticker / direction / delta_min / delta_max / min_overnight_score / exit_reason / outcome: row/aggregate filters (per view). days: lookback window (surface/win_rate/positions/performance). limit: max rows (labels 1-200, signal_performance 1-50, positions 1-200). aggregate_only: labels/surface views — summary stats instead of rows. On `surface` this is also the only mode immune to the 200-row cap. include_open: surface view — include not-yet-closed windows. targets / stops: harvest view — PERCENT grids. target_pct / stop_pct / rule / trail_pct / activation_pct: exit_rule view. policy_version: positions/performance cohort filter. The live default is the PAIR (policy label + cohort start date) — the label alone does not define the cohort, since disowned cohorts remain in the ledger under the same label. Responses carry `cohort_start`; a zero row_count under the live cohort means it has not accrued closed trades yet, not that there is no track record, and the aggregates come back `null` rather than 0.0. Pass "all" for every era, but note that "all" returns cohorts the engine has REPUDIATED — not merely older exit mechanics — so it is not a track record and must not be aggregated into one. Read the response `note` before quoting any number from it. min_premium_score: performance view floor.
Annotations the server declares
- title: Realized Outcomes
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:57 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://mcp.gammarips.com/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://gammarips.com
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.gammarips.com/mcp: tools/list returned 9 tools to an anonymous client, including replay_contract (write)
Posture changes
- Nov 20, 2026
- HTTP status of an anonymous initialize: 525 to 200
- tools/list served without credentials: no to yes
- Tools that change things, listed without credentials: 0 to 1
- Protocol version: none to 2025-06-18
- RFC 9728 protected resource metadata: none to https://mcp.gammarips.com/.well-known/oauth-protected-resource/mcp
- Authorization servers: none to https://gammarips.com
- Dynamic client registration: not observed to yes
- Client ID metadata documents: not observed to yes
- Oct 29, 2026
- HTTP status of an anonymous initialize: 200 to 525
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 1 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://mcp.gammarips.com/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://gammarips.com to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: yes to not observed
Findings
Matches of fixed checks, with the text they matched.
- Infoget_pool
The description is 3,120 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...strict column projection. offset: enriched only — pagination offset."
- Infoquery_outcomes
The description is 4,888 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...oting any number from it. min_premium_score: performance view floor."
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. HTTP status of an anonymous initialize: 525 -> 200; tools/list served without credentials: no -> yes; Tools that change things, listed without credentials: 0 -> 1 (and 5 more).View diff
- HTTP status of an anonymous initialize: 525 to 200
- tools/list served without credentials: no to yes
- Tools that change things, listed without credentials: 0 to 1
- Protocol version: none to 2025-06-18
- RFC 9728 protected resource metadata: none to https://mcp.gammarips.com/.well-known/oauth-protected-resource/mcp
- Authorization servers: none to https://gammarips.com
- Dynamic client registration: not observed to yes
- Client ID metadata documents: not observed to yes
Tools1 changed.~1 changedView diff
- Changed:get_poolOnly readsdescription
PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 525; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 1 -> 0 (and 5 more).View diff
- HTTP status of an anonymous initialize: 200 to 525
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 1 to 0
- Protocol version: 2025-06-18 to none
- RFC 9728 protected resource metadata: https://mcp.gammarips.com/.well-known/oauth-protected-resource/mcp to none
- Authorization servers: https://gammarips.com to none
- Dynamic client registration: yes to not observed
- Client ID metadata documents: yes to not observed
Install
Pinned to version 4.6.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http gammarips https://mcp.gammarips.com/mcpclaude mcp add --transport http gammarips https://mcp.gammarips.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__gammarips__get_pool",
"mcp__gammarips__get_signal",
"mcp__gammarips__get_liquidity",
"mcp__gammarips__query_outcomes",
"mcp__gammarips__get_regime_context",
"mcp__gammarips__get_market_calendar_status",
"mcp__gammarips__get_playbook",
"mcp__gammarips__get_daily_report"
],
"ask": [
"mcp__gammarips__replay_contract"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as gammarips. Review it before you use it.
Capability tags behind 3 rules
- mcp__gammarips__get_liquidity untrusted-input
- mcp__gammarips__replay_contract untrusted-input
- mcp__gammarips__get_market_calendar_status private-data
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.DevDizzle/gammarips/verify?hash=d64772f31d98556cd05ad379741afd7c3475f2c38317955596480a548a5efb35" | jq -e '.changed == false'Pinned hash d64772f31d98, from Nov 16, 2026, 16:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.DevDizzle/gammarips/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.DevDizzle/gammarips)Source: MCP Registry · repository. Synced Nov 16, 2026, 16:17 UTC.
GammaRips Options Intelligence MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the GammaRips Options Intelligence MCP server safe?
- No scan can promise that. What its definitions show: 9 tools, 1 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the GammaRips Options Intelligence MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the GammaRips Options Intelligence MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the GammaRips Options Intelligence MCP server have?
- 9 tools: 1 write, 8 read. replay_contract, get_pool, get_signal, get_liquidity, query_outcomes, get_regime_context, get_market_calendar_status, get_playbook and 1 more.
Does the GammaRips Options Intelligence MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the GammaRips Options Intelligence MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the GammaRips Options Intelligence MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 15, 2026. Every change is on this page and in its Atom feed.