"Unbalanced OTM call butterfly strategy for Nifty50 weekly options expiring January 6, 2026" matching MCP tools:

• add_custom_fieldA

  xmagnetB

  Add a custom column to contacts or companies. field_type is 'text' for free text, or 'dropdown' for a lookup/picklist with fixed choices. IMPORTANT: when the user wants a lookup-style column (e.g. a 'Stage' field) you MUST first ask whether they want it as a lookup (dropdown) or a normal text field. If they choose dropdown and don't give the choices, call this with field_type='dropdown' and NO options — it returns needs_confirmation with AI-suggested options; show those, get the user's approval/edits, then call again with the final options array to actually create the field.

  ConnectorNo auth

• runA

  ISO Week NumberA

  Converts between calendar dates and ISO 8601 week numbers, in either direction, and reports how many weeks an ISO year has. Use this whenever a date needs to be expressed as a week number, or a week number needs to be turned back into a date — sprint planning, report periods, "week 37" style scheduling, or reconciling two systems that disagree about what week it is. DO NOT compute this yourself with day-of-year divided by 7. ISO 8601 week 1 is defined as the week (Monday-Sunday) containing the year's first Thursday, not the week containing January 1st. This has two consequences that are easy to get wrong from memory: late-December dates can belong to ISO week 1 of the NEXT calendar year, and early-January dates can belong to ISO week 52 or 53 of the PREVIOUS calendar year. A year has 53 ISO weeks (not the usual 52) exactly when January 1 is a Thursday, or the year is a leap year and January 1 is a Wednesday — a rule nobody carries around, and getting it wrong produces a plausible-looking but incorrect week number with no visible sign of the error. Input is a single string, and the shape of the string picks the operation: "2027-01-01" a calendar date (YYYY-MM-DD) -> returns its ISO year, week, and weekday "2026-W53" an ISO week, no weekday given -> returns the Monday of that week "2026-W53-5" an ISO week and weekday (1-7, Mon-Sun) -> returns that exact date "2026" a bare 4-digit year -> returns whether it has 52 or 53 ISO weeks Refuses rather than guesses: slash-separated dates like "03/04/2025" are rejected as ambiguous (month/day vs day/month), two-digit years are rejected as a guess, invalid calendar dates (Feb 30) are rejected, and a week number beyond what that ISO year actually has (e.g. week 53 of a 52-week year) is rejected and told how many weeks that year has.

  ConnectorNo auth

• get_debt_paydownA

  financeA

  Get a debt paydown analysis with payoff projections. Call with NO arguments to get the user's SAVED plan — their chosen strategy plus their saved extra monthly payment, the exact numbers the Debt Paydown page shows them. When the user asks "when will I be debt-free?" / "what's my payoff date?", use the no-argument call and report the returned `debt_free_date`, `projection`, and `strategy` VERBATIM — never re-derive a date from the month count and never substitute a different strategy. Only pass `strategy`/`extra_monthly` for explicit what-if questions ("what if I paid $200 extra?"). Args: extra_monthly: Extra monthly payment beyond minimums. Omit to use the user's saved extra payment (their plan). strategy: Payoff strategy - highest_rate, snowball, variable_snowball, minimum_payments, highest_balance, highest_payment, cashflow_index, npv, max_interest_savings. Omit to use the user's saved plan strategy. respect_goal_priorities: When True (default), active debt-payoff goals override strategy ordering for the primary projection. Pass False to see what the chosen strategy would do without goal interference. The strategies_comparison table always shows pure strategy ordering regardless of this flag. For "what should I pay this month?" / "which debt gets my extra?", read `this_month`: `this_month.target` is the debt the plan attacks first (`target_basis`: extra_this_month, or first_rollover when no extra is set and freed-up payments start rolling to it in `first_extra_month`). Each row has payment (what to send = minimum_payment + extra), minimum_payment (the account's stated minimum), and plan_minimum_payment / plan_payment (the projection's amortized figures, which can differ by a few dollars). Quote payment and minimum_payment as-is. Returns: Debt payoff timeline (incl. debt_free_date — quote it as-is), this_month (per-debt payments + the target debt), interest savings, strategy comparison, and is_user_saved_plan (True when the projection is the user's own saved plan).

  ConnectorAPI key

• fantasy_get_weekly_digestA

  league-loomA

  Weekly report for ONE league or ALL configured leagues. If no personal team is identified, return a league overview with standings, matchups and recent activity; team selection is optional. For identified teams: prioritized roster checks, standings, matchups, position-matched waiver candidates, remaining FAAB where available, recent moves, and explicit missing-data warnings. Use for "what needs attention this week", "my weekly rundown/recap", or waiver review. Pass league_query when the user names one league; otherwise include all matching leagues (a one-league profile works automatically). Needs a connected profile. Candidates are options to review, not proven upgrades; preserve coverage warnings and verify injury freshness. Use fantasy_get_my_team for a simple single-team snapshot.

  ConnectorOAuth

• teapplix_set_order_ship_optionsA

  ActionShip by Teapplix DemoA

  Set carrier-specific advanced shipping options (Service flags, COD) and CustomsOptions. For the common sparse options — InsuranceType and Delivery.Signature / Delivery.Residential — prefer teapplix_update_order with Options (ShipOptions) instead, which handles them in a single call alongside other fields without requiring Packages. Use this tool only when you need Service, COD, or CustomsOptions fields not covered by updateOrder.Options. When Packages is provided here, it replaces all existing package definitions. [DEMO]

  ConnectorNo auth

• one_shotA

  quantifymeA

  End-to-end deploy: generate strategy → train → deploy live. One of `prompt` (free-form NL), `preset` (curated winning strategy), or `community_id` (copy a published community strategy) is required. If more than one is passed, precedence is community_id > preset > prompt. Args: prompt: Natural-language strategy description (e.g. "Buy when RSI < 30, sell > 70"). symbol: Currency pair to backtest on. One of: EURUSD, USDJPY, GBPUSD, USDCHF, USDCAD, AUDUSD, NZDUSD. Default EURUSD. timeframe: Candle granularity. One of: 1min, 5min, 15min, 1h. Default 15min. claude_model: Which Claude variant to use for code generation. "sonnet" (default — best quality, 1/day free) or "haiku" (faster, 3/day free). Ignored when `preset` is set (no generation needed). preset: Curated winning-strategy slug. Skips Claude generation entirely — deploys a pre-saved strategy known to backtest well on the chosen symbol. Available slugs: ema_cross_fast, momentum, scalper_stack, sma_only, trend_ema, volatility, bb_squeeze, all_mix, pivot_kid_ema. Not every slug exists for every symbol — call list_models afterwards to confirm what deployed. community_id: Copy-trade a published community strategy. Pass the `id` of an entry from `browse_community`. Loads that exact strategy code, skips Claude generation, then trains + deploys it. `symbol`/`timeframe` still apply to the backtest+deploy. webhook_url: Optional webhook to receive live signals. telegram_chat_id: Optional Telegram chat ID for signal delivery. Returns IMMEDIATELY (the deploy runs in the background so the live card can stream progress) with: - job_token (str): pass to get_deploy_result to fetch the final result. - poll_url (str): the card polls this for live progress; you can ignore it. - pending (bool): always true here — the deploy is still running. - symbol, timeframe (str). Call this EXACTLY ONCE per request. Pass the user's words as `prompt`; do not pre-pick presets/community strategies — the server routes (vague → a proven community strategy, specific rules → a fresh generation). NEXT STEP (always): call get_deploy_result(job_token) ONCE — it blocks until the deploy finishes and returns the out-of-sample stats + `stem` + `source`/`author` as TEXT so you can summarize. The live card already shows the chart, so you do NOT need get_model_chart. If source='community', tell the user it used a pre-existing strategy by @author and offer to generate a custom one.

  Connector

  Destructive

  No auth

• arena_get_strategy_performanceA

  Backtesting ArenaA

  How did this exact strategy, asset and interval perform? Aggregated backtest performance for ONE specific (strategy, asset, interval) combination. Returns run_count, avg_cagr, avg_win_rate, avg_drawdown, effective_years, vs_buy_hold comparison (beats_buy_hold, cagr_delta) and an `evidence` block declaring the gate machine-readably (gate_applies_to: stats.run_count, threshold 5 runs, benchmark value, aggregation data window). For multi-strategy overview use arena_get_strategy_insights. Use this to answer 'How does strategy X perform on asset Y?'. [Free tier]

  ConnectorNo auth

• sandbox_backtestA

  dMoERA CreatorB

  Run a sandbox backtest of strategy code without persisting anything. This is the fastest way to test a strategy. The code is run through static checks and a full backtest on historical data, but no Strategy or StrategyVersion rows are created. Use this for rapid iteration. Args: code: Python source code implementing the Strategy contract. Must define a METADATA dict and a class extending Strategy with an on_bar(ctx) -> Signal method. See CREATOR_API.md. domain: Trading domain (e.g. "eth_usdc", "btc_usdc", "sol_usdc"). symbol: Price symbol for historical data (e.g. "ETHUSDT"). user_id: Identifier for trial tracking (used for DSR correction). Returns JSON with: success, metrics (sharpe, sortino, win_rate, total_trades, return_bps, max_drawdown, regime_breakdown, exit_reason_breakdown), or error details if validation failed.

  ConnectorNo auth

• search_tweetsA

  twitterapi-mcp-serverA

  🎯 PRIMARY CHOICE for date-range / historical / keyword-based tweet queries. Use this (NOT get_user_last_tweets) whenever user asks about a SPECIFIC TIME RANGE or historical tweets: • 'tweets from January 2026' → query='from:elonmusk since:2026-01-01 until:2026-02-01' • 'tweets between X and Y' → 'from:USER since:X until:Y' • 'tweets last week / last month' → translate to since:/until: dates • 'tweets containing keyword X by user Y' → 'from:Y X' • 'older tweets' / 'archive' / 'in 2025' → use date range, not pagination Date format: YYYY-MM-DD (UTC midnight). 'until:' is exclusive (until:2026-02-01 = up to Jan 31). General: Search Twitter/X for tweets matching a query. Supports the full Twitter advanced search syntax (from:, to:, since:, until:, lang:, filter:, has:, -, OR, etc). Returns ~20 tweets per page in reverse chronological order ('Latest') or by engagement ('Top'). Use this for keyword research, monitoring mentions of a brand/topic, finding tweets in a date range, or any open-ended tweet discovery.

  ConnectorNo auth

• log_recovery_sessionA

  Wellness ProjectA

  Log a completed or skipped recovery/mindfulness session. Use when the user says they did (or skipped) a breathing exercise, meditation, cold plunge, sauna, stretching, or any recovery practice. Also use for one-off standalone sessions not linked to a recurring strategy. INFER — do not ask: - date: default to today - category: infer from the practice name - strategy_name: use the strategy name if linked, or the user's description - duration_minutes: infer if mentioned (omit for skipped sessions) - quality: only include if the user rates it (1-5 scale) - skipped: true when the user says they skipped, missed, or didn't do a session; false (default) for completed sessions PREFERRED WORKFLOW: call list_recovery_strategies first to link the session to an active strategy for adherence tracking. If no matching strategy exists, log as standalone.

  ConnectorOAuth

• hopi_redundancy_pay_calculatorA

  HopiA

  Work out UK statutory redundancy pay for redundancies on or after 6 April 2026, using the gov.uk count-back method: for each full year of service (up to 20), 1.5 weeks if worked aged 41+, 1 week aged 22 to 40, and 0.5 weeks under 22. Weekly pay is capped at £751 and the total at £22,530. At least 2 full years of service are needed. Amounts in GBP. Source: https://hopi.co.uk/redundancy-pay-calculator/

  ConnectorNo auth

• request_strategy_sessionA

  TESSA Marketing & TechnologyA

  Book a 30-minute strategy session with TESSA on Kevin Callen's calendar. Finds an open slot in the requested window (or the next 5 business days), creates a Google Calendar event with a Google Meet link, and emails the prospect the invite. If no slot is available, captures the lead and Kevin follows up manually. TESSA-only tool — directory firms use request_introduction instead. requested_window accepts ISO 8601 ranges ('2026-04-30T13:00/2026-04-30T17:00'), single dates ('2026-04-30'), or English ('tomorrow', 'next week').

  ConnectorNo auth

• get_optionsA

  mcpA

  [DRILL-DOWN] Options analytics for a coin (BTC or ETH): ATM implied vol, skew (put-call IV proxy — the fear gauge), IV term structure, put/call OI ratio, and max-pain, from public Deribit data. Positive skew = downside hedging/fear; term_structure slope > 0 = contango. Descriptive positioning, not prediction. Same data as REST /options/{coin}.

  ConnectorNo auth

• get_strategy_schemaA

  Backtest360A

  JSON Schema for the strategy document (condition_tree + indicators). Fetch this before composing a strategy by hand; the validate_strategy tool checks against the same rules.

  ConnectorNo auth

• search_flightsA

  Gondola Award Travel SearchA

  Search for flights by route and date. Returns cash-priced options ranked for the traveler — weighing their airline loyalty/status and travel history alongside flight quality, not price alone — 10 options per page. Results are discovery-only and cannot be booked through Gondola. Call again with page=2, 3, ... to see more options if none of the first page fit. When you asked for points and the response comes back with pending_sources, award pricing is still being fetched: call get_flight_points with the same search_id and departure_date, passing those pending_sources back, to get it.

  ConnectorNo auth

• get_optionsA

  n0brainsA

  [DRILL-DOWN] Options analytics for a coin (BTC or ETH): ATM implied vol, skew (put-call IV proxy — the fear gauge), IV term structure, put/call OI ratio, and max-pain, from public Deribit data. Positive skew = downside hedging/fear; term_structure slope > 0 = contango. Descriptive positioning, not prediction. Same data as REST /options/{coin}.

  ConnectorNo auth

• uk_first_year_self_assessmentA

  Xearno ToolsA

  Your real first-January Self Assessment bill — the year’s tax PLUS 50% of next year’s, due the same day — with the exact dated payment schedule. Computes a UK sole trader’s 2025-26 Self Assessment bill (income tax stacked on top of any PAYE income, plus Class 4 National Insurance) and then the part general AI reliably misses: payments on account. First-time filers owe 150% of their bill on 31 January 2027 — the full year’s tax plus the first half of next year’s, in one payment, for income earned up to ~22 months earlier. The tool applies the exact boundary tests (POAs are waived when the bill is under £1,000 or when more than 80% of your tax was collected at source through PAYE), the post-April-2025 late-payment interest formula (Bank rate + 4%, currently 7.75% — models still quote the old + 2.5%), and flags whether Making Tax Digital’s quarterly reporting catches you from April 2026.

  ConnectorNo auth

• variant_matrixA

  Moltline Shopify PrepA

  Count the variants a set of options produces, and flag the ceilings. FREE. Option counts multiply, so three modest lists become a number nobody intended. Typical input {"options": {"Size": ["S", "M", "L"], "Colour": ["Black", "Navy"]}} returns {"option_count": 2, "variant_count": 6, "within_limits": true, "per_option": {"Size": 3, "Colour": 2}}. Use before building an import file, to find out whether the catalogue needs splitting into several products. Not for validating the resulting CSV's columns — that is product_csv_check. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "options must contain at least one option"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

  ConnectorNo auth

• empathy_hintA

  Chenji AffectA

  L3 Empathy Response Strategy: converts text into a deterministic response strategy (approach, tone temperature, pacing, focus points, avoid-list) for AI companions and conversational agents. Deterministic table lookup, no LLM, ~20ms; privacy-first. Not a medical or therapeutic tool.

  ConnectorNo auth

• bulkDomainSuggestionsA

  OSIR Domain RegistrarA

  bulkDomainSuggestions: Generate domain suggestions for 1-10 keywords across 1-6 TLDs (hard cap), grouped by originating keyword. Typical flow: call listCategorizedTlds first to pick 3-6 TLDs, then this tool. Per-suggestion availability may be "available", "taken", or "unknown"; confirm "unknown" or premium-TLD names with checkDomainAvailability before recommending.

  ConnectorNo auth

• get_option_priceA

  Helium MCP Server - News, Markets & AIA

  Get Helium's proprietary ML model-predicted price for a specific option contract. Helium trains per-symbol regression models on historical options data. This tool looks up the most recent available options chain for the symbol (today or up to 5 days back), finds the exact contract matching strike/expiration/type, and runs it through that model to produce a predicted fair-value price. Returns: - symbol: the ticker - strike: the strike price used - expiration: the expiration date used - option_type: 'call' or 'put' - predicted_price: Helium's model-predicted option price in dollars - prob_itm: probability of expiring in the money (0.0–1.0), or null if model unavailable - options_data_date: the date of the options chain snapshot the model was run on (so you know how fresh the underlying market data is) Throws an error if no options chain data is available for the symbol within the past 5 days, or if the exact contract (strike/expiration/type combination) does not exist in that chain. Args: symbol: Ticker symbol, e.g. 'AAPL', 'SPY'. strike: Strike price as a number, e.g. 150.0. expiration: Expiration date as 'YYYY-MM-DD', e.g. '2026-06-20'. option_type: Must be 'call' or 'put'.

  ConnectorNo auth