PredMCP MCP Server

Polymarket + HIP-4 + Hyperliquid perps for Claude. 22 tools, signals & arb. Free tier. The predmcp mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 2 defined tools rather than through you.

What it actually does

44 MCP tools that cross Polymarket prediction markets, Hyperliquid perps, and HIP-4 native predictions. Plug your agent into live trading data — without ever giving it the ability to execute orders.

• No execution endpoint. — Zero order-placement code exists in this codebase. Not gated, not commented out — not implemented. There is nothing to enable
• No private keys touched. — We use the public Hyperliquid Info API and Polymarket Gamma API. Your wallet, your seed phrase, your accounts — never seen, never asked for
• 44 tools, all queries. — Markets, orderbooks, funding rates, whale activity, signals. Every tool is a read. Your agent reasons about markets; you stay the only one who can act on them

Its toolset

Everything the assistant can do here goes through one of these:

• Family — Tools
• Polymarket — get_markets · get_odds · get_orderbook · get_whale_positions · search_markets · get_movers · get_markets_near_resolution · get_volume_spikes ·

Configuration

You will need one environment variable: YOUR_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

When to reach for it

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. PredMCP's toolset — Family, Polymarket — is a fair guide to whether it matches your workflow. It is maintained by RavioleLabs; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against PredMCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Caveats

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the predmcp mcp server does with a few real requests.