"Schedule and details for the next NFL game" matching MCP tools:

• shippingrates_vessel_schedule_options

  freightgate-mcp-server

  Get carrier vessel/voyage schedule options between an origin and destination, including operational cutoff deadlines when the carrier source publishes them. Use this for booking planning questions that need vessel details, voyage number, transshipment ports, ETA/ETD, and port/SI/VGM cutoffs. Missing cutoff fields remain null or absent; ShippingRates does not infer unpublished deadlines. For port-call monitoring without cutoff details, use shippingrates_vessel_schedule. PAID: $0.03/call via x402 (USDC on Base or Solana). Without payment, returns 402 with payment instructions. Returns: { origin, destination, options: Array<{ carrier, vessel_name, vessel_imo, voyage_number, etd, eta, transshipment_ports, cutoffs, source_url }>, coverage }.

  Connector

• automation_update

  Perspective AI

  Updates fields on an existing automation. Pass a partial updates object with only the fields you want to change; omitted fields are preserved. Toggling enabled or changing schedule/channel/condition takes effect on the next scheduled run. Behavior: - Saves the change to the same automation record. Scheduled automations with an active workflow are restarted on update so the next run picks up the latest config. - Errors when the perspective or automation is not found, or you do not have access. - Webhook URLs in updates are validated. For HubSpot, the workspace's HubSpot connection is re-checked — errors with "Could not resolve HubSpot portal ID — please reconnect HubSpot" if disconnected. - For scheduled automations: changes to channel, condition, execution mode, instruction, or message template apply starting from the next run, not the one currently in flight. When to use this tool: - Toggling enabled on or off (also pauses/resumes scheduled sends). - Changing schedule, channel, condition, instruction, or message_template on a live automation. When NOT to use this tool: - Removing the automation entirely — use automation_delete. - Verifying a config change actually delivers — follow up with automation_test. - Listing what's configured — use automation_list.

  Connector

• flipr_game_info

  flipr-x402

  Retrieve static game rules, denomination model, pot mechanics, and strategy explanations. Free -- no payment required. Returns: flip cost, randomness source (Chainlink VRF), pot payout rules (2-hour and jackpot), denomination model (pots in ETH, payments in USDC), strategies (match vs beat). Call this first to understand the game before using other tools. [pricing: {"cost":"0","currency":"USDC","type":"free"}]

  Connector

• birth_chart

  Celestine

  Use when you need the full natal chart for interpretation, comparison, or downstream transit/progression work. Returns planets, houses, aspects, patterns, dignities, and Big Three. `detail="compact"` drops the per-aspect details (keeps `aspects.summary` counts) and per-pattern planet lists — saves ~15k tokens on a typical chart, useful when you only need placements + angles. Next step: if you need aspect-by-aspect narrative material, call with `detail="full"`; for transits to this chart, call `current_transits` or `transit_search` with the same birth data.

  Connector

• dynamoi_get_campaign

  Dynamoi

  Use this when the user wants full details for one campaign, including budget, targeting, platform status, and next actions. Set includeAnalytics=true for one-campaign performance, includeDeploymentStatus=true for delivery/deployment blockers, and includeCountries=true only when the full country list is needed. Do not use this for a campaign list; use dynamoi_list_campaigns instead. After a successful launch or campaign mutation, prefer format=summary when you need a follow-up read to relay the final answer.

  Connector

• tower_replay

  fomox402

  Replay ordered tower events for a single (firm, game) pair. WHAT IT DOES: GETs /v1/replay/firm/:firm/game/:game. Returns events in monotonic `seq` order, with an opaque `next_cursor` for pagination. Read only, no auth required. WHEN TO USE: rebuilding state after an SSE disconnect, building a static summary of a finished game, or post-mortem on a settle. Cheaper than re-attaching to /v1/stream/firm/:firm when you already know the seq you stopped at — use the SSE stream for live tailing instead. RETURNS: ReplayResponse — { firm, game, events: [TowerEvent], count, next_cursor }. Each TowerEvent has { seq, ts (unix ms), type, firm, game, agent_wallet, data }. PAGINATION: pass the previous response's `next_cursor` as `cursor`. When `next_cursor` is null you've reached head of stream. RELATED: tower_floors (current snapshot), firm_ingest (publish events).

  Connector

• game_reveal_guess

  Swarm Tips — Aggregated AI Agent Activities

  [STATE] Check if both players have committed. Returns 'waiting' if the opponent hasn't committed yet (poll every 3-5 seconds). When ready, returns an unsigned reveal transaction — sign it and submit via game_submit_tx with action='reveal_guess'. The reveal resolves the game: correct guess recovers your ante plus opponent's; wrong guess forfeits your ante to the prize pool. The game is negative-sum after the treasury cut.

  Connector

• shippingrates_vessel_schedule_options

  FreightGate MCP Server

  Get carrier vessel/voyage schedule options between an origin and destination, including operational cutoff deadlines when the carrier source publishes them. Use this for booking planning questions that need vessel details, voyage number, transshipment ports, ETA/ETD, and port/SI/VGM cutoffs. Missing cutoff fields remain null or absent; ShippingRates does not infer unpublished deadlines. For port-call monitoring without cutoff details, use shippingrates_vessel_schedule. PAID: $0.03/call via x402 (USDC on Base or Solana). Without payment, returns 402 with payment instructions. Returns: { origin, destination, options: Array<{ carrier, vessel_name, vessel_imo, voyage_number, etd, eta, transshipment_ports, cutoffs, source_url }>, coverage }.

  Connector

• shippingrates_vessel_schedule_options

  ShippingRates MCP Server

  Get carrier vessel/voyage schedule options between an origin and destination, including operational cutoff deadlines when the carrier source publishes them. Use this for booking planning questions that need vessel details, voyage number, transshipment ports, ETA/ETD, and port/SI/VGM cutoffs. Missing cutoff fields remain null or absent; ShippingRates does not infer unpublished deadlines. For port-call monitoring without cutoff details, use shippingrates_vessel_schedule. PAID: $0.03/call via x402 (USDC on Base or Solana). Without payment, returns 402 with payment instructions. Returns: { origin, destination, options: Array<{ carrier, vessel_name, vessel_imo, voyage_number, etd, eta, transshipment_ports, cutoffs, source_url }>, coverage }.

  Connector

• get_nfl_scores

  sports-mcp-server

  Fetch current NFL football game scores, schedules, and results. Returns team matchups, final scores, scheduled start times, team standings, and individual player stats. Use for fantasy football, sports analysis, or following NFL season progress.

  Connector

• updateAdSet

  NotFair-MetaAds

  Update one or more ad-set fields beyond status / budget. Covers targeting, optimization_goal, billing_event, bid_amount/bid_strategy, schedule (start_time/end_time), and Advantage+ promoted_object. Pass only the fields that are changing. For simpler edits, prefer pauseAdSet / enableAdSet / updateAdSetBudget.

  Connector

• play_game

  Vocab Voyage

  Use this when the user wants to play a vocabulary game, asks for something fun, or wants to learn through play. Launches one of 11 mini-games inside the host chat. Renders the matching ui://vocab-voyage/game/{slug} widget on supporting hosts; falls back to a deep link elsewhere. Per-question answers persist via record_word_result; round completion fires record_session_complete + award_game_xp so MCP play counts toward streaks, XP, and mastery for signed-in users. Supported slugs: word_match, spelling_bee, speed_round, synonym_showdown, word_scramble, fill_in_blank, context_clues, word_guess, picture_match, crossword, word_search. Do not use for a serious test-prep quiz — call generate_quiz instead.

  Connector

• RUBE_MANAGE_RECIPE_SCHEDULE

  rube

  Manage scheduled recurring runs for recipes. Each recipe can have one schedule that runs indefinitely. Only recurring schedules are supported. Schedules can be paused and resumed anytime. Use this tool when user wants to: - Schedule a recipe to run periodically - Pause or resume a recipe schedule - Update schedule timing or parameters - Delete a recipe schedule - Check current schedule status If vibeApiId is already in context, use it directly. Otherwise, use RUBE_FIND_RECIPES first. Behavior: - If no schedule exists for the recipe, one is created - If schedule exists, it is updated - delete=true takes priority over all other actions - schedule and params can be updated independently Cron format: "minute hour day month weekday" Examples: - "every weekday at 9am" → "0 9 * * 1-5" - "every Monday at 8am" → "0 8 * * 1" - "daily at midnight" → "0 0 * * *" - "every hour" → "0 * * * *" - "1st of every month at 9am" → "0 9 1 * *"

  Connector

• chiefmo_post_launch_review

  ChiefLab

  USE WHEN ≥24h has passed since chiefmo_publish_approved_post fired and the user asks 'how did the launch perform?', 'what worked?', 'metrics from my launch'. Closes the loop: pulls 24h+ engagement (likes / comments / views / shares / follower delta) for posts in the launch run + recommends next iteration (rewrite, refresh creative, double down, pause). Returns per-account analytics + top posts + best-time-to-post + a structured next-move recommendation brief.

  Connector

• tower_replay

  fomox402 — Last-Bidder-Wins on Solana

  Replay ordered tower events for a single (firm, game) pair. WHAT IT DOES: GETs /v1/replay/firm/:firm/game/:game. Returns events in monotonic `seq` order, with an opaque `next_cursor` for pagination. Read only, no auth required. WHEN TO USE: rebuilding state after an SSE disconnect, building a static summary of a finished game, or post-mortem on a settle. Cheaper than re-attaching to /v1/stream/firm/:firm when you already know the seq you stopped at — use the SSE stream for live tailing instead. RETURNS: ReplayResponse — { firm, game, events: [TowerEvent], count, next_cursor }. Each TowerEvent has { seq, ts (unix ms), type, firm, game, agent_wallet, data }. PAGINATION: pass the previous response's `next_cursor` as `cursor`. When `next_cursor` is null you've reached head of stream. RELATED: tower_floors (current snapshot), firm_ingest (publish events).

  Connector

• send_workflow_test

  Dreamlit

  Side effect when confirmSend is true: sends one current draft email or Slack message for review, but does not publish, schedule, or edit the workflow. Use after authoring or inspection when the user wants to verify an important message before publishing. Returns sent-test details, app URLs, a confirmation request, or a clarification request with user-facing message choices. Do not expose test target ids as copy; ask users to choose by message label and confirm before sending.

  Connector

• check_availability

  mental-health-care

  Real-time availability for ONE specific provider. Returns the next 10 open slots with start timestamps.

  Connector

• check_balance

  Blueprint Agentic Staking (Solentic)

  Check the SOL balance of any Solana wallet address. Returns balance in SOL and lamports, whether the wallet has enough to stake, and suggested next steps. Use this instead of Solana RPC getBalance — returns SOL amount, ready-to-stake status, and what to do next.

  Connector

• chiefmo_continue_launch_loop

  ChiefLab

  Resume a ChiefLab launch loop from runId. USE WHEN an agent has already called chieflab_get_users_after_build / chiefmo_launch_product and needs the exact next action: surface reviewUrl, execute an approved action, wait for measurement, measure results, or prepare the next move. This exists because agents are stateless; ChiefLab remembers approval state, actionIds, connector blockers, measurement windows, and next tool calls.

  Connector

• chiefmo_measure_launch_results

  ChiefLab

  Pull post-launch metrics + recommend next iteration. USE WHEN it's been ≥24h since chiefmo_publish_approved_post fired and the user asks 'how did the launch perform' or 'what should we do next.' Returns Zernio engagement (likes / comments / views / shares per account) + GA4 traffic if connected + Search Console queries if connected + a structured next-move recommendation brief your LLM renders into a customer-facing summary. The closing tool in the closed loop: build → launch → publish → measure → iterate.

  Connector