Koskamo

Mantis MCP MCP server

Mantis provides a cross-venue prediction market routing and intelligence layer for AI agents. It aggregates live data from multiple prediction platforms including Polymarket, Kalshi, and PredictIt. The server enables agents to query market probabilities, find arbitrage opportunities across venues, get live quotes, and execute trades via referral links. It supports natural language queries to identify the best market venue and provides demand intelligence for market creation.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by Mantis
MCP endpoint (Streamable HTTP)
https://mantiss.store/mcp
Vendor documentation

What you can do with it

  • Route natural-language queries to find the best prediction market venue and probability
  • Scan live markets for cross-venue arbitrage spreads and profitability
  • Get live yes/no prices, liquidity, and order book depth for specific markets
  • Return unmet demand queries to identify opportunities for new market creation
Tools advertised by the last live check:
  • route_market
  • get_arbitrage
  • execute_url
  • get_quote
  • get_history
  • get_unmet_demand

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http mantis-mcp https://mantiss.store/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add mantis-mcp --url https://mantiss.store/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable mantis-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "mantis-mcp": {
      "url": "https://mantiss.store/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.
Cline configuration
{
  "mcpServers": {
    "mantis-mcp": {
      "type": "streamableHttp",
      "url": "https://mantiss.store/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start mantis-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "mantis-mcp": {
      "type": "http",
      "url": "https://mantiss.store/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http mantis-mcp https://mantiss.store/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "mantis-mcp": {
      "url": "https://mantiss.store/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "mantis-mcp": {
      "serverUrl": "https://mantiss.store/mcp"
    }
  }
}

Do you run Mantis MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing