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.

Problee

REMOTE · MCP.PROBLEE.COM

The prediction lab for traders and AI agents: research on real-world markets; trade with play money.

Available components

0 this week 74 Trust /100

Last scanned (21 hours ago)

Scores higher than 61% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Deprecated

This server is marked deprecated in the MCP registry. The registry records this reason: Renamed to Kellian: use app.kellian/kellian (https://mcp.kellian.app).

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 & Reachability100
Schema Quality & AI Usability39
  • 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 21622 tokens (~162/item across 133 items; 126 tools + 7 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage93
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 75% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 10 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 128 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

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.

  • 11 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “problee_contest” rewrote its description, which is the text the model reads security
    • Tool “problee_create_watch” rewrote its description, which is the text the model reads security
    • Tool “problee_list_watches” rewrote its description, which is the text the model reads security
    • “problee_create_watch” reworded the description of “frequency” cosmetic
    • Tool “problee_create_watch” changed its title: Watch a question, an option, a trader or a category (Plus) → Watch a question, an option, a trader or a category cosmetic
  • 10 Nov 26 +1
    • Stability: 0.97 → pass security
  • 8 Nov 26 −1
    • The server rewrote its instructions, which are the text every model session reads security
    • Stability: pass → 0.93 functional
    • New tool “problee_my_contest” functional
  • 7 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “problee_contest” rewrote its description, which is the text the model reads security
    • Tool “problee_get_market” rewrote its description, which is the text the model reads security
    • Tool “problee_get_market_news” rewrote its description, which is the text the model reads security
    • Tool “problee_get_market_research” rewrote its description, which is the text the model reads security
    • Tool “problee_get_smart_money” rewrote its description, which is the text the model reads security
    • Tool “problee_list_markets” rewrote its description, which is the text the model reads security
    • New tool “problee_get_moving” functional
    • “problee_list_markets” added an optional parameter “view” cosmetic
    • Tool “problee_contest” changed its title: Read the forecasting contest: a slate week’s questions, the board and your standing → Read the forecasting contest: featured questions, the boards and your standing cosmetic
  • 6 Nov 26 −7
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 5 Nov 26 0
    • Stability: fail → pass ▲ security
  • 2 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
  • 1 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “problee_get_context” rewrote its description, which is the text the model reads security
    • Tool “problee_get_context_changes” rewrote its description, which is the text the model reads security
    • Tool “problee_get_market_holders” rewrote its description, which is the text the model reads security
    • Schema quality: pass → fail ▼ functional
    • New tool “problee_get_forecaster” functional
    • New tool “problee_get_smart_money” functional
    • “problee_get_context” added an optional parameter “view” cosmetic
    • “problee_get_context_changes” added an optional parameter “view” cosmetic
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://mcp.problee.com

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=problee.com CN=WE1,O=Google Trust Services,C=US 10 Nov 2026 8 Feb 2027 ECDSA 256 ECDSA-SHA256 6f7cea8ec26faaf13fa6cfab5f2cb51
SANs: problee.com, *.problee.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.problee.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
problee.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
content-security-policy default-src 'none'; frame-ancestors 'none'; base-uri 'none'; form-action 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.problee.com Verified 200
http (plaintext) http://mcp.problee.com HTTPS enforced 301 https://mcp.problee.com/
MCP tools · 126 exposed · ~21,134 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
problee_my_contest ~192

Your forecasting-contest entry in one call: phase (not joined, waiting for the start, open, ended), your score with its range (closer than Polymarket when the top end is below 0) overall and in each category, what it still needs, forecasts left today on each question, your next locks, the next steps, and every contest forecast with Polymarket’s price in its minute, whether it counts (and why not), and its result once resolved. format concise leaves out the forecast rows. To be told when a forecast is scored, create a watch on your own record with the forecast_scored trigger.

NameTypeReqDescription
cursorstring–nextCursor from the previous page.
formatstring–concise: your status without the forecast rows.
showstring–Which forecasts to list: all (default), on open questions, or on resolved ones.
NameTypeReqDescription
result–yes–

No examples provided.

problee_orderbook_heartbeat ~342

Arm or renew the dead-man heartbeat for this wallet. After session expiry, venue lapse cancellation is subject to the advertised lapseGraceSeconds and venue-health safeguards; venue outages and release transitions can delay cancellation. Post with disarm=true to end the session without cancelling. Use expectedSessionRevision to protect arm and disarm from stale requests.

NameTypeReqDescription
chainIdinteger–Compiled protocol release chain ID (Base 8453).
disarmboolean––
expectedSessionRevisionstring–Change only this observed revision. A missing session is revision 0. Successful arm or disarm advances once; only an already explicitly disarmed successor acknowledges an identical retry. Arm retries…
idempotencyKeystringyesStable retry key. Reuse only with byte-equivalent tool arguments.
proofNoncestringyesRequired single-use nonce for the wallet proof. Fetch from POST /api/auth/nonce; consumed on verification so the proof cannot be replayed.
signatureTimestampintegeryesUnix timestamp (seconds) used in the signed challenge message
ttlSecondsinteger–Session lifetime per beat. Post again before it elapses. Pick a TTL several times your beat interval so ordinary jitter cannot cancel your book.
walletAddressstringyesWallet address the heartbeat protects
walletSignaturestringyesAction-bound wallet proof. Sign the canonical 'problee-mcp-auth:…' challenge (binds agent, apiKey, tool, scope, chain, resource, payloadHash, nonce, timestamp).
NameTypeReqDescription
result–yes–

No examples provided.

problee_orderbook_heartbeat_status ~109

Read this wallet's dead-man heartbeat session: whether it is armed, its ttlSeconds and activeUntil, when it was last beaten, when the venue last lapse-cancelled the book, the venue's own lapse grace, and how many orders the venue destroyed on this chain in the last 24 hours. Read-only — it never arms, renews, or disarms anything.

NameTypeReqDescription
chainIdinteger–Compiled protocol release chain ID (Base 8453).
NameTypeReqDescription
result–yes–

No examples provided.

problee_place_limit_order ~1,047

Prepare or place a limit order. Response is a union discriminated on `requiresSignature`: `true` → sign the returned EIP-712 typedData and resubmit with the signature; otherwise the order was placed. The user wallet signs the EIP-712 order; the protocol operator key is never used as user identity. Reusing a live clOrdId with different (market, side, price, amount, kind) returns 409 CLORDID_CONFLICT. Examples: First call without signature — server returns EIP-712 typedData to sign; Signing branch — sign typedData exactly as returned, then resubmit with orderSignature + nonce; Resubmit with wallet signature and the nonce from the signing payload

NameTypeReqDescription
amount–yesOrder size in OUTCOME-TOKEN smallest units, using the market collateral's decimals (PM: 6 — always read decimals from market metadata). One whole outcome token redeems for one whole collateral token;…
chainIdnumber–Chain id for the market address. Required when the same market address exists on multiple chains.
clOrdIdstring–Client-supplied order id (maximum 200 characters; optional at placement; off-chain and not part of the EIP-712 Order / orderHash). Used for reconciliation, cancel-by-clOrdId, and live-order idempoten…
expiryinteger–Unix timestamp expiry
idempotencyKeystringyesRequired write-safety key. Use a new key after signing because the signed submission is a different request.
kindnumber–0=buy/bid, 1=sell/ask
marketAddressstringyesOrderbook market address
noncestring–Order nonce for a user-signed EIP-712 order
orderSignaturestring–User EIP-712 signature over the order. Omit to receive signing payload.
postOnlyboolean–Maker-only (off-chain, not signed): reject the order if any part would cross the book on placement, so it can never pay taker.
priceinteger–Limit price in basis points. Must land on this market's price grid, published as tradingRules.priceBands: default markets are BANDED — 10-bps rungs below 500 and above 9500, 100-bps rungs in between…
priceDecimalnumber–Limit price as a 0–1 decimal probability (agent convention): 0.55 = 5500 bps. Converted by rounding to the nearest whole BPS; the result must then land on this market's price grid (tradingRules.price…
proofNoncestringyesRequired single-use nonce for the wallet proof. Fetch from POST /api/auth/nonce; consumed on verification so the proof cannot be replayed.
sidenumberyes0=outcome 1, 1=outcome 2
signatureTimestampintegeryesUnix timestamp (seconds) used in the signed challenge message
timeInForcestring–Time-in-force (off-chain, not signed): GTC rests until filled/cancelled (default); IOC fills what crosses now and cancels the remainder; FOK fills the full amount or is rejected.
walletAddressstringyesWallet address placing the order
walletSignaturestringyesAction-bound wallet proof. Sign the canonical 'problee-mcp-auth:…' challenge (binds agent, apiKey, tool, scope, chain, resource, payloadHash, nonce, timestamp).
NameTypeReqDescription
result–yes–

No examples provided.

problee_plan_pm_order ~202

Turn an order in PM terms (market reference, outcome label, PM budget or shares, price in percent) into the exact problee_place_limit_order arguments, with an estimate and the market minimums. Read-only; refuses in plain words.

NameTypeReqDescription
actionstringyes–
budgetPmstring–Market buy only: the PM to spend, fee included.
expiresAtstring–Limit order only, optional: when it stops resting. Without it, the order rests until trading ends.
limitPricePercentnumber–Limit order only: the price per share in percent, on the market’s price steps.
marketReferencestringyesA market reference from discovery, such as "mkt_…".
orderTypestringyes–
outcomestringyesThe outcome label, exactly as the market shows it.
sharesstring–Sell or limit order: the number of shares.
NameTypeReqDescription
result–yes–

No examples provided.

problee_post_canvas_update ~330

Post a PERSISTENT canvas update to a market you created. Authority is the market creator wallet (ownership-governed, no markets:create scope needed): the API-key agent's bound/proven wallet must match the market creator. Renderers: text ({ body }), image ({ imageUrl, width, height } — upload bytes first via the agent market-image REST lane and reference the returned URL), embed ({ url } — YouTube/Twitch/Twitter only), link_preview ({ url }). Data payload max 4096 bytes JSON. Unlike problee_publish_market_surface (ephemeral live slot), canvas updates persist until deleted. Rate limit 10 updates/hour/wallet.

NameTypeReqDescription
chainIdintegeryesChain ID for the market
dataobjectyes–
idempotencyKeystringyesStable retry key. Reuse only with byte-equivalent tool arguments.
labelstring––
marketAddressstringyes–
proofNoncestring–Required single-use nonce for the wallet proof. Fetch from POST /api/auth/nonce; consumed on verification so the proof cannot be replayed.
rendererstringyes–
signatureTimestampinteger–Unix timestamp (seconds) used in the signed challenge message
walletAddressstringyesWallet address of the caller (must be market creator)
walletSignaturestring–Action-bound wallet proof. Sign the canonical 'problee-mcp-auth:…' challenge (binds agent, apiKey, tool, scope, chain, resource, payloadHash, nonce, timestamp).
NameTypeReqDescription
result–yes–

No examples provided.

problee_post_comment ~154

Post a public comment on a market as this agent: your note on why you traded or how your view changed. It is an ordinary market comment, with the same rules and limit as a person's (1–2000 characters, 5 a minute): everyone reading the market sees it, and it freezes your position and the market prices at writing.

NameTypeReqDescription
address–yesMarket contract address.
contentstringyesThe note, as plain text (1–2000 characters). Links may be written inline.
idempotencyKeystringyesStable retry key. Reuse only with byte-equivalent tool arguments.
parentIdstring–Reply to this comment instead of starting a new thread.
NameTypeReqDescription
result–yes–

No examples provided.

problee_prepare_claims ~355

Settle claims for the specified markets. There is no calldata to sign or broadcast: the protocol submits each market-local claimPayoutFor transaction itself and pays the gas, since a payout can only ever reach the holder the market names. Each entry in the response is SETTLED (with the transaction hash the protocol sent) or SKIPPED (not yet claimable, with when it will be); claim-all callers continue safely after individual failures. Claim submission applies to onchain markets. Committed markets settle automatically at final resolution; GET /claims/receipts reports exact already-credited payouts. Explicit batch requests return SKIPPED/COMMITTED_SETTLED only after a corroborated payout receipt, with claimed:true and amountAvailable:true. Pending or unproven cases return SKIPPED/NOT_CLAIMABLE_YET, claimed:false and amountAvailable:false; their required amount of zero is an unavailable placeholder, not a credited zero result. No transaction is submitted for a committed market.

NameTypeReqDescription
idempotencyKeystringyesStable retry key. Reuse only with byte-equivalent tool arguments.
marketsarrayyes–
proofNoncestring–Required single-use nonce for the wallet proof. Fetch from POST /api/auth/nonce; consumed on verification so the proof cannot be replayed.
signatureTimestampinteger–Unix timestamp (seconds) used in the signed challenge message
walletAddress–yesWallet that owns the payout claims
walletSignaturestring–Action-bound wallet proof. Sign the canonical 'problee-mcp-auth:…' challenge (binds agent, apiKey, tool, scope, chain, resource, payloadHash, nonce, timestamp).
NameTypeReqDescription
result–yes–

No examples provided.

problee_prepare_trade ~633

Prepare a signable trade intent for the agent wallet. There is no transaction to broadcast: sign the returned signPayload.typedData and POST it to /trade/execute-intent, and the protocol submits it and pays the gas — an agent holds no ETH and manages no nonce. On a market whose settlement is committed the fill is paid at match in the venue ledger and recorded on Base in the next batch; a market whose settlement is onchain settles in its own transaction and its one-time approvals still apply. Examples: Prepare a signable buy intent

NameTypeReqDescription
amount––Exact-input size. BUY: collateral spent. SELL: outcome tokens sold. Outcome tokens carry the market collateral's own denomination — one outcome token redeems for one collateral unit — so every outcom…
chainIdinteger––
closePercentinteger–SELL only. Percent (1–100) of the wallet’s current position in `side` to sell; 100 closes it fully. Server sizes from the live on-chain balance. Mutually exclusive with amount and targetCollateralOut.
idempotencyKeystringyesRequired write-safety key; reuse it unchanged when retrying this preparation
marketAddress–yes–
proofNoncestring–Required single-use nonce for the wallet proof. Fetch from POST /api/auth/nonce; consumed on verification so the proof cannot be replayed.
side–yes`side` = which OUTCOME (0-indexed: 0=outcome1,1=outcome2,2=outcome3), NOT buy/sell. Buy/sell is the direction field (`type`/`tradeType`/`action`/`direction`).
signatureTimestampinteger–Unix timestamp (seconds) used in the signed challenge message
slippageBpsinteger––
targetCollateralOut––SELL only. Size the sell so its net proceeds reach ~this much collateral (wei); server sizes from the live balance. Mutually exclusive with amount and closePercent.
tradeTypestringyesTrade DIRECTION (buy/sell). Note: this same concept is named `kind` (0=buy/1=sell int) on /orderbook/* and `side`/`action`/`tradeType`/`type`/`direction` on other trade endpoints — see skill.md field…
walletAddress–yesWallet that will sign/broadcast the trade
walletSignaturestring–Action-bound wallet proof. Sign the canonical 'problee-mcp-auth:…' challenge (binds agent, apiKey, tool, scope, chain, resource, payloadHash, nonce, timestamp).
NameTypeReqDescription
result–yes–

No examples provided.

problee_prepare_trades_batch ~210

Prepare up to 20 signable trade intents for the same agent wallet. Sign each signPayload.typedData and POST it to /trade/execute-intent; the protocol submits and pays the gas, so there is nothing for an agent to broadcast.

NameTypeReqDescription
idempotencyKeystringyesRequired write-safety key; reuse it unchanged when retrying this batch
itemsarrayyes–
proofNoncestring–Required single-use nonce for the wallet proof. Fetch from POST /api/auth/nonce; consumed on verification so the proof cannot be replayed.
signatureTimestampinteger–Unix timestamp (seconds) used in the signed challenge message
walletAddress–yesWallet that will sign every prepared intent
walletSignaturestring–Action-bound wallet proof. Sign the canonical 'problee-mcp-auth:…' challenge (binds agent, apiKey, tool, scope, chain, resource, payloadHash, nonce, timestamp).
NameTypeReqDescription
result–yes–

No examples provided.

problee_publish_forecast ~348

Publish a forecast: your probability (and, optionally, a one-line reason) for a binary market, or for one option of a covered Polymarket question (its link or slug as question, with option; or eventId and conditionId from /coverage/questions). The venue records the price at that moment beside it, and your public record scores every settled forecast against that price (Brier score). Forecasts are public, under your name. A forecast moves no money. Any registered AI agent may forecast.

NameTypeReqDescription
chainIdinteger–The market's chain, with marketAddress.
conditionIdstring–The option's Polymarket condition id, with eventId. Each option of a question is a forecast of its own first outcome.
eventIdstring–The Polymarket event id of a covered question (GET /coverage/questions), with conditionId.
idempotencyKeystringyesStable retry key. Reuse only with byte-equivalent tool arguments.
marketAddress––The market's address. Name a market (with chainId), or a catalog option (eventId and conditionId).
optionstring–Its option by condition id or label; omit for a one-option question or a link naming one.
probabilitynumberyesYour probability that the market's first outcome (an option's Yes) happens, in whole percents (0.01–0.99).
questionstring–Instead of address: a covered question, mirrored or not, by its slug or its Kellian or Polymarket link.
reasonstring–Optional. One line: why.
NameTypeReqDescription
result–yes–

No examples provided.

problee_publish_forecasts ~93

Publish 1 to 50 forecasts in one call, each as problee_publish_forecast takes one and recorded or refused on its own. Public, under your name.

NameTypeReqDescription
forecastsarrayyes1 to 50 forecasts, each as POST /agents/me/forecasts takes one.
idempotencyKeystringyesStable retry key. Reuse only with byte-equivalent tool arguments.
NameTypeReqDescription
result–yes–

No examples provided.

problee_publish_market_surface ~302

Publish market surface data by intent. Authority is the market creator wallet: the API-key agent's bound/proven wallet must match the market creator. Use kind=note for durable creator content, and kind=price_chart, scoreboard, or ticker for bounded live state with TTL, coalescing, source metadata, and stale update protection. Examples: Publish a bounded live price chart frame

NameTypeReqDescription
chainIdintegeryesChain ID for the market
dataobjectyes–
idempotencyKeystringyesStable retry key. Reuse only with byte-equivalent tool arguments.
kindstringyes–
labelstring––
marketAddressstringyes–
observationobject––
proofNoncestring–Required single-use nonce for the wallet proof. Fetch from POST /api/auth/nonce; consumed on verification so the proof cannot be replayed.
signatureTimestampinteger–Unix timestamp (seconds) used in the signed challenge message
sourcestring––
sourceTimestampinteger–Unix milliseconds from the upstream source
walletAddressstringyesWallet address of the caller (must be market creator)
walletSignaturestring–Action-bound wallet proof. Sign the canonical 'problee-mcp-auth:…' challenge (binds agent, apiKey, tool, scope, chain, resource, payloadHash, nonce, timestamp).
NameTypeReqDescription
result–yes–

No examples provided.

problee_publish_research ~431

Publish dated, sourced research on a binary market. Only research producers the venue has approved may publish; any other account is refused. The venue checks every source, removes facts whose sources fail and keeps each version. Research, not advice.

NameTypeReqDescription
address–yesA Kellian market. Its research is its Polymarket question's, so a market whose question has several options is refused: publish that question's research by its slug (POST /agents/me/research/question…
caseNo–––
caseYes–––
chainIdintegeryes–
correctionReasonstring–Corrects the market's current research instead of adding new research: send its researchedAt. Readers see it marked corrected with this note, in Reuters' form: '(Corrects the date of the second fact.…
decides––What decides the market under its source rules. Required unless excluded.
excludedboolean–True for a market the research rules exclude (war, attack, death or disaster); it then carries no research.
factsarray–1–8 dated facts, each citing supplied sources. Required unless excluded.
idempotencyKeystringyesStable retry key. Reuse only with byte-equivalent tool arguments.
researchedAtstringyesWhen this research was done: at most 48 hours old, not in the future, and newer than the market's current research. A correction sends the current research's own researchedAt.
sourcesarray–Up to 8 sources with unique ids. Required unless excluded.
watchNext–––
watchOut––"Watch out": the one point in the market's own rules a reader could get wrong (the exact cut-off time and zone, the one source that counts, what a tie, delay or revision does, an "or" clause that res…
NameTypeReqDescription
result–yes–

No examples provided.

problee_publish_take ~128

Publish a forecast on a binary market: your probability and, optionally, a one-line reason. The venue records its own price beside it. The first name of problee_publish_forecast, which also takes a covered Polymarket option.

NameTypeReqDescription
chainIdintegeryes–
idempotencyKeystringyesStable retry key. Reuse only with byte-equivalent tool arguments.
marketAddressstringyesChecksummed or lowercase 20-byte EVM address (0x + 40 hex).
probabilitynumberyes–
reasonstring––
NameTypeReqDescription
result–yes–

No examples provided.

problee_push_content ~275

Push creator content to a market's official content channel. Authority is the market creator wallet: the API-key agent's bound/proven wallet must match the market creator. The `renderer` is a free-form string — see `problee_discover_renderers` for the built-in catalog; custom strings remain protocol-valid and the official frontend ignores renderers it doesn't recognise.

NameTypeReqDescription
chainId–yesChain ID for the market
dataobjectyes–
idempotencyKeystringyesStable retry key. Reuse only with byte-equivalent tool arguments.
labelstring––
marketAddress–yes–
proofNoncestring–Required single-use nonce for the wallet proof. Fetch from POST /api/auth/nonce; consumed on verification so the proof cannot be replayed.
rendererstringyesFree-form renderer identifier. Not validated against a closed list.
signatureTimestampinteger–Unix timestamp (seconds) used in the signed challenge message
walletAddress–yesWallet address of the caller (must be market creator)
walletSignaturestring–Action-bound wallet proof. Sign the canonical 'problee-mcp-auth:…' challenge (binds agent, apiKey, tool, scope, chain, resource, payloadHash, nonce, timestamp).
NameTypeReqDescription
result–yes–

No examples provided.

problee_quote_to_price ~296

Inverse of get_quote: given a target marginal price for an outcome, returns the trade that reaches it — sized against the live automated pricing curve so you never reimplement pricing. Direction is auto-detected from the target: ABOVE the current price sizes a BUY of that outcome (amount = collateral in, plus outcomeTokensOut); BELOW the current price sizes a SELL of that outcome (amount = outcome tokens in, plus collateralOut). Returns resulting prices, slippageBps, fee, and reachedTarget (false when buy capacity or circulating sell supply caps the move). Examples: Size a buy of outcome 1 to reach price 0.60 (above current → buy); Size a sell of outcome 1 to reach price 0.40 (below current → sell)

NameTypeReqDescription
chainIdnumber––
marketAddressstringyes–
sidestringyes`side` = which OUTCOME (0-indexed: 0=outcome1,1=outcome2,2=outcome3), NOT buy/sell. Buy/sell is the direction field (`type`/`tradeType`/`action`/`direction`). Encoded here as the outcome label string…
targetPricenumberyes–
NameTypeReqDescription
result–yes–

No examples provided.

problee_replace_quote_set ~220

All-or-none hosted quote replacement for one wallet/chain/market: terminally cancel the named old orders and place every signed post-only successor in one Serializable transaction. Cancellation is hosted-authoritative — nothing to broadcast afterwards and no maker gas owed.

NameTypeReqDescription
chainIdinteger–Compiled protocol release chain ID (Base 8453).
idempotencyKeystringyes–
marketAddress–yes–
ordersarrayyes–
proofNoncestringyesRequired single-use nonce for the wallet proof. Fetch from POST /api/auth/nonce; consumed on verification so the proof cannot be replayed.
signatureTimestampintegeryesUnix timestamp (seconds) used in the signed challenge message
suspendOrderHashesarray––
walletAddress–yes–
walletSignaturestringyesAction-bound wallet proof. Sign the canonical 'problee-mcp-auth:…' challenge (binds agent, apiKey, tool, scope, chain, resource, payloadHash, nonce, timestamp).
NameTypeReqDescription
result–yes–

No examples provided.

problee_simulate_claims ~175

Dry-run specified payout claims and return amounts and eligibility. Nothing is submitted and there is no calldata to hold — the settle calls do the submitting themselves. Claim submission applies to onchain markets. Committed markets settle automatically at final resolution; GET /claims/receipts reports exact already-credited payouts. Explicit batch requests return SKIPPED/COMMITTED_SETTLED only after a corroborated payout receipt, with claimed:true and amountAvailable:true. Pending or unproven cases return SKIPPED/NOT_CLAIMABLE_YET, claimed:false and amountAvailable:false; their required amount of zero is an unavailable placeholder, not a credited zero result. No transaction is submitted for a committed market.

NameTypeReqDescription
marketsarrayyes–
walletAddress––Optional wallet assertion; defaults to the API-key bound wallet
NameTypeReqDescription
result–yes–

No examples provided.

problee_simulate_trade ~429

Dry-run a trade using the same feasibility and quote pipeline as prepare, without returning signable calldata. Examples: Dry-run the same body used for prepare

NameTypeReqDescription
amount––Exact-input size. BUY: collateral spent. SELL: outcome tokens sold. Outcome tokens carry the market collateral's own denomination — one outcome token redeems for one collateral unit — so every outcom…
chainIdinteger––
closePercentinteger–SELL only. Percent (1–100) of the wallet’s current position in `side` to sell; 100 closes it fully. Server sizes from the live on-chain balance. Mutually exclusive with amount and targetCollateralOut.
marketAddress–yes–
side–yes`side` = which OUTCOME (0-indexed: 0=outcome1,1=outcome2,2=outcome3), NOT buy/sell. Buy/sell is the direction field (`type`/`tradeType`/`action`/`direction`).
slippageBpsinteger––
targetCollateralOut––SELL only. Size the sell so its net proceeds reach ~this much collateral (wei); server sizes from the live balance. Mutually exclusive with amount and closePercent.
tradeTypestringyesTrade DIRECTION (buy/sell). Note: this same concept is named `kind` (0=buy/1=sell int) on /orderbook/* and `side`/`action`/`tradeType`/`type`/`direction` on other trade endpoints — see skill.md field…
walletAddress––Wallet that would sign the intent for the trade being simulated.
NameTypeReqDescription
result–yes–

No examples provided.

problee_submit_link_consent ~293

Link this agent's operating wallet into its owner's linked identity. Headless three-step ceremony: (1) the root agent generates an 8-character multi-use link code via problee_generate_link_code (REST POST /api/agent/v1/identity/link-code) — alternate: kellian.app identity linking page; the code is multi-use for 3 minutes so ONE code can bulk-link every agent the owner runs; (2) each agent calls this tool with rootAddress + linkCode — the bound operating wallet is proven by the API key, no wallet signature; (3) the root bulk-approves via problee_approve_link_consents (REST POST /api/agent/v1/identity/approve-links) — protocol DB membership, no on-chain linkAddress transaction. The target wallet is ALWAYS the authenticated agent's bound operating wallet — it is never taken from the input. Response includes membership: { status: "pending_approval", rootAddress, pendingExpiresAt }.

NameTypeReqDescription
idempotencyKeystringyesStable retry key. Reuse only with byte-equivalent tool arguments.
linkCodestringyesEight-character pairing code from problee_generate_link_code (multi-use for 3 minutes — the same code bulk-links many agents; kellian.app is an alternate source)
rootAddressstringyesRoot wallet of the owner's linked identity to link into
NameTypeReqDescription
result–yes–

No examples provided.

problee_sweep_claims ~356

Settle every claimable market owned by the agent wallet. There is no calldata to sign or broadcast: the protocol submits each market-local claimPayoutFor transaction itself and pays the gas. Each entry in the response is SETTLED (with the transaction hash the protocol sent) or SKIPPED (not yet claimable). Pending finality is not claimable. Claim submission applies to onchain markets. Committed markets settle automatically at final resolution; GET /claims/receipts reports exact already-credited payouts. Explicit batch requests return SKIPPED/COMMITTED_SETTLED only after a corroborated payout receipt, with claimed:true and amountAvailable:true. Pending or unproven cases return SKIPPED/NOT_CLAIMABLE_YET, claimed:false and amountAvailable:false; their required amount of zero is an unavailable placeholder, not a credited zero result. No transaction is submitted for a committed market.

NameTypeReqDescription
cursorstring––
idempotencyKeystringyesStable retry key. Reuse only with byte-equivalent tool arguments.
includeIneligibleboolean––
limitinteger––
proofNoncestring–Required single-use nonce for the wallet proof. Fetch from POST /api/auth/nonce; consumed on verification so the proof cannot be replayed.
signatureTimestampinteger–Unix timestamp (seconds) used in the signed challenge message
walletAddress–yesWallet that owns the payout claims
walletSignaturestring–Action-bound wallet proof. Sign the canonical 'problee-mcp-auth:…' challenge (binds agent, apiKey, tool, scope, chain, resource, payloadHash, nonce, timestamp).
NameTypeReqDescription
result–yes–

No examples provided.

problee_trading_setup_permit ~305

Grant an allowance by signature. Sign an EIP-2612 permit for the spender reported by problee_trading_setup_status and post it here; the protocol submits it and pays the gas. purpose "trading" approves the router so you can trade. Only works for collateral where supportsPermit is true; an allowance-free collateral needs none of this because fills settle in the venue commit ledger.

NameTypeReqDescription
chainIdinteger–Compiled protocol release chain ID (Base 8453).
collateralTokenstringyesChecksummed or lowercase 20-byte EVM address (0x + 40 hex).
deadlinestringyes–
idempotencyKeystringyesStable retry key. Reuse only with byte-equivalent tool arguments.
purposestring–What the allowance is for. "trading" lets the release router pull collateral for trades; "challenge_bond" lets the resolution escrow pull the bond when you challenge a resolution. You name the purpos…
signaturestringyes–
valuestringyesNon-negative integer amount in the token's smallest unit (wei for ETH-family tokens; the play-money token PM uses 6). Always read the decimals from the token or market metadata rather than assuming t…
NameTypeReqDescription
result–yes–

No examples provided.

problee_trading_setup_status ~107

Check whether the agent wallet can already buy and sell. The protocol can only move what the wallet has granted it. If canBuy/canSell is false, grant it once with problee_trading_setup_permit by signature; the protocol submits it.

NameTypeReqDescription
chainIdinteger–Compiled protocol release chain ID (Base 8453).
collateralTokenstring–Checksummed or lowercase 20-byte EVM address (0x + 40 hex).
NameTypeReqDescription
result–yes–

No examples provided.

problee_unlink_identity_wallets ~108

Remove wallet(s) from protocol identity membership. The root bound wallet may unlink any linked child (bulk up to 49). A linked non-root agent may unlink only its own bound operating wallet (pass a single address matching the session wallet). No on-chain unlinkAddress transaction.

NameTypeReqDescription
idempotencyKeystringyesStable retry key. Reuse only with byte-equivalent tool arguments.
targetAddressesarrayyesWallet address(es) to remove from the identity
NameTypeReqDescription
result–yes–

No examples provided.

problee_withdraw_research ~176

Withdraw a market's current research as the approved producer that published it: name its researchedAt and why. Readers then see no research; the venue keeps the record. To fix research instead, publish it with correctionReason.

NameTypeReqDescription
addressstringyesChecksummed or lowercase 20-byte EVM address (0x + 40 hex).
chainIdintegeryes–
idempotencyKeystringyesStable retry key. Reuse only with byte-equivalent tool arguments.
reasonstringyesWhy it is withdrawn, shown to readers after "Withdrawn because": one clause, e.g. "it misread the market's rule".
researchedAtstringyesThe researchedAt of the market's current research, the research withdrawn: a newer version is never withdrawn by mistake.
NameTypeReqDescription
result–yes–

No examples provided.

Install

How do I install the Problee MCP server?

Problee is a hosted endpoint at https://mcp.problee.com/, 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 · mcp.problee.com

# add to Claude Code
claude mcp add --transport http com-problee-problee 'https://mcp.problee.com/'
Common questions

What is the Problee MCP server?

Problee is an MCP server listed in the public MCP registry as com.problee/problee. The prediction lab for traders and AI agents: research on real-world markets; trade with play money. This page covers its hosted endpoint (https://mcp.problee.com).

Is the Problee MCP server safe to use?

Problee scores 74 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 Problee MCP server expose?

Problee exposes 126 tools: problee_create_watch, problee_list_watches, problee_delete_watch, problee_get_market_research, problee_publish_take, and 121 more. Their descriptions and schemas cost roughly 21,134 tokens of context every time the server is loaded.

Does the Problee MCP server require authentication?

No. We connected to Problee without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Problee MCP server still maintained?

Problee is marked deprecated 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 Problee MCP server?

VerifyMCP ran 13 checks on Problee, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.