Polymarket Mcp

io.github.whitmorelabsPublished by GitHub account whitmorelabsv0.1.2Updated Oct 24, 2026

Trading intelligence tools for Polymarket: slippage, liquidity, arbitrage, price feeds

VerifiedSTDIODesktop onlyFinance

Overview

AI-generated overview

Local MCP server giving an assistant Polymarket trading intelligence: slippage, liquidity, arbitrage and price feeds.

What you can do
  • Analyze Polymarket markets for slippage and liquidity.
  • Compare markets to surface arbitrage opportunities.
  • Read price feeds for prediction-market pricing.
  • No tool list is published, so the exact operations are not documented.
When to use it
Worth adding when you want an assistant to reason about Polymarket prediction markets — checking liquidity, estimating slippage, or looking for arbitrage between markets — from a local desktop setup.
Requirements
Runs as a local process over stdio, installed from the PyPI package polymarket-trading-mcp, so a Python environment is needed. No authentication, environment variables or headers are declared. Desktop only; not available as a web executable.
Before you install
The name and description point at trading, but no tools, README or instructions are published, so what it can actually do — and whether it can place or modify orders — cannot be verified. No credentials are declared, yet trading-related servers often need wallet or API access; review the package before installing and avoid exposing funds.

Installation

In SourceWeft

  1. Open Polymarket Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.2LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.