io.github.junct-bot/hyperliquid-mcp vs io.github.whitmorelabs/polymarket-mcp
io.github.junct-bot/hyperliquid-mcp is an MCP server published by junct-bot. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.whitmorelabs/polymarket-mcp is an MCP server published by whitmorelabs. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  io.github.junct-bot/hyperliquid-mcp | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.1.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.1.2 Downloads/month (PyPI): 198 Downloads/week (PyPI): 70 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | io.github.junct-bot/hyperliquid-mcp | io.github.whitmorelabs/polymarket-mcp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (hyperliquid.mcp.junct.dev/mcp) | On your machine (polymarket-trading-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/junct-bot/hyperliquid-mcp | github.com/whitmorelabs/polymarket-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Not responding since 2026-10-14 | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
io.github.junct-bot/hyperliquid-mcp
Hyperliquid - 2 tools for perpetuals, options, and position data
io.github.whitmorelabs/polymarket-mcp
Trading intelligence tools for Polymarket: slippage, liquidity, arbitrage, price feeds
How to run each
io.github.junct-bot/hyperliquid-mcp As a remote MCP server
claude mcp add --transport http hyperliquid-mcp https://hyperliquid.mcp.junct.dev/mcpio.github.whitmorelabs/polymarket-mcp As a local MCP server: PyPI package
claude mcp add --transport stdio polymarket-mcp -- uvx polymarket-trading-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.junct-bot/hyperliquid-mcp has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: io.github.junct-bot/hyperliquid-mcp · What it can do: io.github.whitmorelabs/polymarket-mcp · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.