Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

predictDEX

REMOTE · PREDICT.DEX.MK

Live Polymarket odds, order books, fee-inclusive quotes and non-custodial prediction trading.

Available components

0 this week 25 Trust /100

Last scanned (21 hours ago)

Scores higher than 10% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

What we tested

Checks we ran (5)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport

Checks we could not complete (6)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 9 Nov 26 −11
    • Endpoint reachability: behind authorisation → not serving MCP ▼ security
    • Transport: unverified → fail ▼ security
    • Authorization: fail → unverified ▼ security
    • Tool safety: Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list. security
    • Tool coverage: Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list. functional
    • Capabilities: Capabilities not yet verified: we couldn't read the endpoint's capabilities. functional
    • Schema quality: Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list. functional
  • 7 Nov 26 0
    • Endpoint reachability: reachable → behind authorisation ▼ security
  • 6 Nov 26 −54
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Oct 26 +1
    • Stability: 0.97 → pass security
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Sept 26 0

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://predict.dex.mk/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=predict.dex.mk CN=YR1,O=Let's Encrypt,C=US 24 Sept 2026 23 Dec 2026 RSA 2048 SHA256-RSA 5f8d8d800f75d056c4ab96d6cd43801d008
SANs: predict.dex.mk
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of predict.dex.mk. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
mk. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
HTTP status 503
Header Value
strict-transport-security max-age=63072000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://predict.dex.mk/mcp HTTP error 503
http (plaintext) http://predict.dex.mk/mcp HTTPS enforced 308 https://predict.dex.mk/mcp
MCP tools · 11 exposed · ~1,036 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
attest_agent ~91

Submit the signed attestation. Returns a 30-day agent token that unlocks gasless Polymarket account setup through predictDEX's signer for your address only. It grants no custody and no exemption from region rules.

NameTypeReqDescription
addressstringyes0x address that signed
messagestringyesThe exact challenge message
signaturestringyes0x EIP-191 signature

No output schema declared.

No examples provided.

create_trade_link ~132

A pre-filled predictDEX ticket URL (event, market, outcome, side, amount) for a person to review and sign in their own wallet. Opening it executes nothing. Use this when you have no wallet or need human confirmation.

NameTypeReqDescription
amountnumber–USD to spend for BUY, shares for SELL
marketstring–Market id or conditionId (defaults to the event's main market)
outcomestring–0 = first outcome (Yes), 1 = second (No)
sidestring–BUY or SELL
slugstringyesEvent slug

No output schema declared.

No examples provided.

get_agent_challenge ~60

Returns the canonical 'predictDEX Agent Attestation v1' message for your address. Sign it with EIP-191 personal_sign within 10 minutes and pass it to attest_agent.

NameTypeReqDescription
addressstringyesYour 0x wallet address

No output schema declared.

No examples provided.

get_event ~76

Full event by slug: every market, outcome names and prices, token ids, tick size, min order size, rules summary, resolution source and status. Optionally include recent trades.

NameTypeReqDescription
recentTradesinteger–Include up to N recent trades (0-50)
slugstringyesEvent slug from search_markets

No output schema declared.

No examples provided.

get_leaderboard ~57

Top Polymarket traders by profit or volume over a window.

NameTypeReqDescription
limitinteger–Rows (1-100, default 25)
metricstring–Ranking metric
windowstring–Time window

No output schema declared.

No examples provided.

get_orderbook ~73

Live order book for one outcome token: bids and asks (price 0-1, size in shares), spread, midpoint and last trade.

NameTypeReqDescription
depthinteger–Levels per side (1-100, default 20)
tokenIdstringyesOutcome token id (digits) from get_event

No output schema declared.

No examples provided.

get_positions ~54

Open positions of a Polymarket trading account or its owner address: size, average price, current price, value and P&L.

NameTypeReqDescription
addressstringyes0x address (owner EOA or Deposit Wallet)

No output schema declared.

No examples provided.

get_price_history ~43

Price (probability) history for one outcome token over a range.

NameTypeReqDescription
rangestring–Time range
tokenIdstringyesOutcome token id

No output schema declared.

No examples provided.

get_trading_setup ~68

Everything an agent with its own wallet needs to trade: chain, collateral (pUSD), builder code, signer URL, attestation steps, fees and a ready-to-run TypeScript snippet using Polymarket's official SDK. Non-custodial: you sign with your own key.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

quote_order ~206

Preview an order against the live book without placing it: average and worst price, shares, cost, payout if the outcome wins, Polymarket fee, predictDEX fee and warnings. Market BUY amount is USD to spend all-in; market SELL and limit amounts are shares.

NameTypeReqDescription
amountnumberyesUSD for a market BUY, shares otherwise
expirationinteger–GTD expiry, unix seconds
orderTypestring–FAK/FOK for market, GTC/GTD for limit
postOnlyboolean–Limit orders: rest only, never take
pricenumber–Limit price as probability 0-1 (required for limit)
sidestring–BUY or SELL
slippagenumber–Market orders: max price move in price units, e.g. 0.02
tokenIdstringyesOutcome token id
typestring–market (default) or limit

No output schema declared.

No examples provided.

search_markets ~176

Find events and their markets with live odds. Filter by free-text query, category slug (see predict://categories), sort and status. Each event lists markets with outcomes, token ids, best bid/ask, tick size and a human URL.

NameTypeReqDescription
categorystring–Category slug, e.g. politics, crypto, sports, new, breaking, ending
limitinteger–Events to return (1-50, default 20)
maxMarketsinteger–Markets per event (1-50, default 5)
offsetinteger–Pagination offset
qstring–Free-text search, e.g. 'fed rate october' or 'bitcoin 150k'
sortstring–Sort order
statusstring–active (default), resolved or all

No output schema declared.

No examples provided.

Install

How do I install the predictDEX MCP server?

predictDEX is a hosted endpoint at https://predict.dex.mk/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · predict.dex.mk

# add to Claude Code
claude mcp add --transport http mk-dex-predictdex 'https://predict.dex.mk/mcp'
Common questions

What is the predictDEX MCP server?

predictDEX is an MCP server listed in the public MCP registry as mk.dex/predictdex. Live Polymarket odds, order books, fee-inclusive quotes and non-custodial prediction trading. This page covers its hosted endpoint (https://predict.dex.mk/mcp).

Is the predictDEX MCP server safe to use?

predictDEX scores 25 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the predictDEX MCP server expose?

predictDEX exposes 11 tools: search_markets, get_event, get_orderbook, get_price_history, quote_order, and 6 more. Their descriptions and schemas cost roughly 1,036 tokens of context every time the server is loaded.

Does the predictDEX MCP server require authentication?

Its publisher declares no required credentials for predictDEX. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the predictDEX MCP server still maintained?

predictDEX is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the predictDEX MCP server?

VerifyMCP ran 5 checks on predictDEX, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 1 more. 6 items could not be completed, a gap on our side rather than a finding about predictDEX: Authorization, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.