"Deep Research on MCP (Master Control Program or Related Topic)" matching MCP tools:

• polymarket_arbitrage

  Opentopography

  Find arbitrage opportunities on Polymarket by checking for monotonicity violations across related markets. TWO MODES: (1) `event` — pass a single Polymarket event slug; walks that event's child markets and checks ordering within it. (2) `topic` — pass a topic / seed question (e.g. "Strait of Hormuz traffic returns to normal"); the tool searches across separate events for related markets, groups them, then checks monotonicity. Cross-event mode catches the cases where Polymarket lists each cutoff as its own event ("…by May 31" is event A, "…by Jun 30" is event B — single-event mode misses the May≤June rule). Returns ranked opportunities with suggested trade direction + reasoning.

  Connector

• polymarket_arbitrage

  Listen Notes

  Find arbitrage opportunities on Polymarket by checking for monotonicity violations across related markets. TWO MODES: (1) `event` — pass a single Polymarket event slug; walks that event's child markets and checks ordering within it. (2) `topic` — pass a topic / seed question (e.g. "Strait of Hormuz traffic returns to normal"); the tool searches across separate events for related markets, groups them, then checks monotonicity. Cross-event mode catches the cases where Polymarket lists each cutoff as its own event ("…by May 31" is event A, "…by Jun 30" is event B — single-event mode misses the May≤June rule). Returns ranked opportunities with suggested trade direction + reasoning.

  Connector

• polymarket_arbitrage

  Watchmode

  Find arbitrage opportunities on Polymarket by checking for monotonicity violations across related markets. TWO MODES: (1) `event` — pass a single Polymarket event slug; walks that event's child markets and checks ordering within it. (2) `topic` — pass a topic / seed question (e.g. "Strait of Hormuz traffic returns to normal"); the tool searches across separate events for related markets, groups them, then checks monotonicity. Cross-event mode catches the cases where Polymarket lists each cutoff as its own event ("…by May 31" is event A, "…by Jun 30" is event B — single-event mode misses the May≤June rule). Returns ranked opportunities with suggested trade direction + reasoning.

  Connector

• polymarket_arbitrage

  Lyrics Ovh

  Find arbitrage opportunities on Polymarket by checking for monotonicity violations across related markets. TWO MODES: (1) `event` — pass a single Polymarket event slug; walks that event's child markets and checks ordering within it. (2) `topic` — pass a topic / seed question (e.g. "Strait of Hormuz traffic returns to normal"); the tool searches across separate events for related markets, groups them, then checks monotonicity. Cross-event mode catches the cases where Polymarket lists each cutoff as its own event ("…by May 31" is event A, "…by Jun 30" is event B — single-event mode misses the May≤June rule). Returns ranked opportunities with suggested trade direction + reasoning.

  Connector

• polymarket_arbitrage

  Linkedin Humblebrag

  Find arbitrage opportunities on Polymarket by checking for monotonicity violations across related markets. TWO MODES: (1) `event` — pass a single Polymarket event slug; walks that event's child markets and checks ordering within it. (2) `topic` — pass a topic / seed question (e.g. "Strait of Hormuz traffic returns to normal"); the tool searches across separate events for related markets, groups them, then checks monotonicity. Cross-event mode catches the cases where Polymarket lists each cutoff as its own event ("…by May 31" is event A, "…by Jun 30" is event B — single-event mode misses the May≤June rule). Returns ranked opportunities with suggested trade direction + reasoning.

  Connector

• polymarket_arbitrage

  Gitlab Public

  Find arbitrage opportunities on Polymarket by checking for monotonicity violations across related markets. TWO MODES: (1) `event` — pass a single Polymarket event slug; walks that event's child markets and checks ordering within it. (2) `topic` — pass a topic / seed question (e.g. "Strait of Hormuz traffic returns to normal"); the tool searches across separate events for related markets, groups them, then checks monotonicity. Cross-event mode catches the cases where Polymarket lists each cutoff as its own event ("…by May 31" is event A, "…by Jun 30" is event B — single-event mode misses the May≤June rule). Returns ranked opportunities with suggested trade direction + reasoning.

  Connector

• polymarket_arbitrage

  Confluence

  Find arbitrage opportunities on Polymarket by checking for monotonicity violations across related markets. TWO MODES: (1) `event` — pass a single Polymarket event slug; walks that event's child markets and checks ordering within it. (2) `topic` — pass a topic / seed question (e.g. "Strait of Hormuz traffic returns to normal"); the tool searches across separate events for related markets, groups them, then checks monotonicity. Cross-event mode catches the cases where Polymarket lists each cutoff as its own event ("…by May 31" is event A, "…by Jun 30" is event B — single-event mode misses the May≤June rule). Returns ranked opportunities with suggested trade direction + reasoning.

  Connector

• polymarket_arbitrage

  wikifeed

  Find arbitrage opportunities on Polymarket by checking for monotonicity violations across related markets. TWO MODES: (1) `event` — pass a single Polymarket event slug; walks that event's child markets and checks ordering within it. (2) `topic` — pass a topic / seed question (e.g. "Strait of Hormuz traffic returns to normal"); the tool searches across separate events for related markets, groups them, then checks monotonicity. Cross-event mode catches the cases where Polymarket lists each cutoff as its own event ("…by May 31" is event A, "…by Jun 30" is event B — single-event mode misses the May≤June rule). Returns ranked opportunities with suggested trade direction + reasoning.

  Connector

• polymarket_arbitrage

  cocktails

  Find arbitrage opportunities on Polymarket by checking for monotonicity violations across related markets. TWO MODES: (1) `event` — pass a single Polymarket event slug; walks that event's child markets and checks ordering within it. (2) `topic` — pass a topic / seed question (e.g. "Strait of Hormuz traffic returns to normal"); the tool searches across separate events for related markets, groups them, then checks monotonicity. Cross-event mode catches the cases where Polymarket lists each cutoff as its own event ("…by May 31" is event A, "…by Jun 30" is event B — single-event mode misses the May≤June rule). Returns ranked opportunities with suggested trade direction + reasoning.

  Connector

• polymarket_arbitrage

  Amplitude

  Find arbitrage opportunities on Polymarket by checking for monotonicity violations across related markets. TWO MODES: (1) `event` — pass a single Polymarket event slug; walks that event's child markets and checks ordering within it. (2) `topic` — pass a topic / seed question (e.g. "Strait of Hormuz traffic returns to normal"); the tool searches across separate events for related markets, groups them, then checks monotonicity. Cross-event mode catches the cases where Polymarket lists each cutoff as its own event ("…by May 31" is event A, "…by Jun 30" is event B — single-event mode misses the May≤June rule). Returns ranked opportunities with suggested trade direction + reasoning.

  Connector

• polymarket_arbitrage

  microlink

  Find arbitrage opportunities on Polymarket by checking for monotonicity violations across related markets. TWO MODES: (1) `event` — pass a single Polymarket event slug; walks that event's child markets and checks ordering within it. (2) `topic` — pass a topic / seed question (e.g. "Strait of Hormuz traffic returns to normal"); the tool searches across separate events for related markets, groups them, then checks monotonicity. Cross-event mode catches the cases where Polymarket lists each cutoff as its own event ("…by May 31" is event A, "…by Jun 30" is event B — single-event mode misses the May≤June rule). Returns ranked opportunities with suggested trade direction + reasoning.

  Connector

• polymarket_arbitrage

  Klaviyo

  Find arbitrage opportunities on Polymarket by checking for monotonicity violations across related markets. TWO MODES: (1) `event` — pass a single Polymarket event slug; walks that event's child markets and checks ordering within it. (2) `topic` — pass a topic / seed question (e.g. "Strait of Hormuz traffic returns to normal"); the tool searches across separate events for related markets, groups them, then checks monotonicity. Cross-event mode catches the cases where Polymarket lists each cutoff as its own event ("…by May 31" is event A, "…by Jun 30" is event B — single-event mode misses the May≤June rule). Returns ranked opportunities with suggested trade direction + reasoning.

  Connector

• polymarket_arbitrage

  Emoji Oracle

  Find arbitrage opportunities on Polymarket by checking for monotonicity violations across related markets. TWO MODES: (1) `event` — pass a single Polymarket event slug; walks that event's child markets and checks ordering within it. (2) `topic` — pass a topic / seed question (e.g. "Strait of Hormuz traffic returns to normal"); the tool searches across separate events for related markets, groups them, then checks monotonicity. Cross-event mode catches the cases where Polymarket lists each cutoff as its own event ("…by May 31" is event A, "…by Jun 30" is event B — single-event mode misses the May≤June rule). Returns ranked opportunities with suggested trade direction + reasoning.

  Connector

• polymarket_arbitrage

  Noaa

  Find arbitrage opportunities on Polymarket by checking for monotonicity violations across related markets. TWO MODES: (1) `event` — pass a single Polymarket event slug; walks that event's child markets and checks ordering within it. (2) `topic` — pass a topic / seed question (e.g. "Strait of Hormuz traffic returns to normal"); the tool searches across separate events for related markets, groups them, then checks monotonicity. Cross-event mode catches the cases where Polymarket lists each cutoff as its own event ("…by May 31" is event A, "…by Jun 30" is event B — single-event mode misses the May≤June rule). Returns ranked opportunities with suggested trade direction + reasoning.

  Connector

• polymarket_arbitrage

  Temperature Random

  Find arbitrage opportunities on Polymarket by checking for monotonicity violations across related markets. TWO MODES: (1) `event` — pass a single Polymarket event slug; walks that event's child markets and checks ordering within it. (2) `topic` — pass a topic / seed question (e.g. "Strait of Hormuz traffic returns to normal"); the tool searches across separate events for related markets, groups them, then checks monotonicity. Cross-event mode catches the cases where Polymarket lists each cutoff as its own event ("…by May 31" is event A, "…by Jun 30" is event B — single-event mode misses the May≤June rule). Returns ranked opportunities with suggested trade direction + reasoning.

  Connector

• polymarket_arbitrage

  Magic 8 Ball

  Find arbitrage opportunities on Polymarket by checking for monotonicity violations across related markets. TWO MODES: (1) `event` — pass a single Polymarket event slug; walks that event's child markets and checks ordering within it. (2) `topic` — pass a topic / seed question (e.g. "Strait of Hormuz traffic returns to normal"); the tool searches across separate events for related markets, groups them, then checks monotonicity. Cross-event mode catches the cases where Polymarket lists each cutoff as its own event ("…by May 31" is event A, "…by Jun 30" is event B — single-event mode misses the May≤June rule). Returns ranked opportunities with suggested trade direction + reasoning.

  Connector

• polymarket_arbitrage

  Gleif

  Find arbitrage opportunities on Polymarket by checking for monotonicity violations across related markets. TWO MODES: (1) `event` — pass a single Polymarket event slug; walks that event's child markets and checks ordering within it. (2) `topic` — pass a topic / seed question (e.g. "Strait of Hormuz traffic returns to normal"); the tool searches across separate events for related markets, groups them, then checks monotonicity. Cross-event mode catches the cases where Polymarket lists each cutoff as its own event ("…by May 31" is event A, "…by Jun 30" is event B — single-event mode misses the May≤June rule). Returns ranked opportunities with suggested trade direction + reasoning.

  Connector

• polymarket_arbitrage

  Openrouteservice

  Find arbitrage opportunities on Polymarket by checking for monotonicity violations across related markets. TWO MODES: (1) `event` — pass a single Polymarket event slug; walks that event's child markets and checks ordering within it. (2) `topic` — pass a topic / seed question (e.g. "Strait of Hormuz traffic returns to normal"); the tool searches across separate events for related markets, groups them, then checks monotonicity. Cross-event mode catches the cases where Polymarket lists each cutoff as its own event ("…by May 31" is event A, "…by Jun 30" is event B — single-event mode misses the May≤June rule). Returns ranked opportunities with suggested trade direction + reasoning.

  Connector

• polymarket_arbitrage

  Census

  Find arbitrage opportunities on Polymarket by checking for monotonicity violations across related markets. TWO MODES: (1) `event` — pass a single Polymarket event slug; walks that event's child markets and checks ordering within it. (2) `topic` — pass a topic / seed question (e.g. "Strait of Hormuz traffic returns to normal"); the tool searches across separate events for related markets, groups them, then checks monotonicity. Cross-event mode catches the cases where Polymarket lists each cutoff as its own event ("…by May 31" is event A, "…by Jun 30" is event B — single-event mode misses the May≤June rule). Returns ranked opportunities with suggested trade direction + reasoning.

  Connector

• polymarket_arbitrage

  Figshare

  Find arbitrage opportunities on Polymarket by checking for monotonicity violations across related markets. TWO MODES: (1) `event` — pass a single Polymarket event slug; walks that event's child markets and checks ordering within it. (2) `topic` — pass a topic / seed question (e.g. "Strait of Hormuz traffic returns to normal"); the tool searches across separate events for related markets, groups them, then checks monotonicity. Cross-event mode catches the cases where Polymarket lists each cutoff as its own event ("…by May 31" is event A, "…by Jun 30" is event B — single-event mode misses the May≤June rule). Returns ranked opportunities with suggested trade direction + reasoning.

  Connector