Problee

What it can reach

From its install config and its own description; a sandbox run will confirm this later.

Checks on v1.0.6

1. Real tool

   passrules 2026-09-29.1 · 3 hours ago

2. Static scan

   passrules 2026-09-29.1 · 3 hours ago

3. Claims check

   skippedrules 2026-09-29.1 · 3 hours ago
   • infoLLM claims check is not configured on this deploy.

Install

Each app still asks you to confirm. Everything is pinned to the version checked above.

{
  "servers": {
    "problee": {
      "type": "http",
      "url": "https://mcp.problee.com"
    }
  }
}

Tools it offers

As the server describes them. This text comes from the publisher and is shown as-is.

• problee_get_server_time

  Return the protocol server wall-clock time as Unix epoch milliseconds. Use before quoting to measure client clock skew. Unauthenticated. Examples: Current server epoch ms

• problee_list_capabilities

  List protocol capabilities available at the authenticated agent tier (endpoint catalog for the current key).

• problee_list_chains

  List all supported blockchain networks

• problee_get_token_release

  Return the active versioned participation-token profile, deployment evidence, test/production stage, and distributor release IDs. This is separate from live market collateral discovery.

• problee_list_collateral

  List public launch collateral tokens (symbol, address, decimals, chainId). chainId is optional only when exactly one chain is active.

• problee_get_contracts

  Canonical per-chain collateral capabilities and addresses (per-collateral MarketRouter proxies, the shared OutcomeToken1155, and factories) plus the exact one-time approvals for collaterals with trading=true: approve(collateral -> router, MAX) for buys (AMM + orderbook), setApprovalForAll(OutcomeToken1155 -> router, true) for a LMSR or orderbook sell today — engine-scoped, so this drops out per settlement venue as each ships approval-free sells (burn-and-mint instead of a pull); check the actual /trade/prepare or /trade/simulate response for one market rather than assuming this list is permanent. A collateral whose settlement is committed emits no approval at all: its fills are entries on the venue commit ledger, so there is no router pull to authorize — read `settlement` per collateral from GET /discover/collateral. Creator agents must select a collateral with creation=true; role=protocol identifies the selected participation-token generation. Cancel and direct market-local claims need no approval. Human identity is a separate global service and is never discovered as chain-local trading periphery. All addresses are stable/permanent (UUPS) where applicable.