Lucyd MCP server

• Registry nametrade.lucyd/mcpverified in the MCP registry

The registry name sits under lucyd.trade. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-28
• Tools9
• Server calls itselflucyd
• Server version0.1.3
• Protocol version2025-06-18

On 2026-10-28 the server answered initialize and tools/list without a sign-in. First answer in 158 ms.

• Its tools do none of the product's use cases we checked: bet whether bitcoin ends a round higher or lower; sell an open position early on the order book; download past round order book history for backtests.
• Checked on 5 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 5 so far
• What an agent can do with it0 of 3 use cases
• Use81 npm downloads a week
• Answeredmeasuring5 of the 7 daily checks it takes to print a share
• Median first answer92 ms
• Space in an agent's context≈ 1,236 tokensthe definitions of all its tools (9), which an agent carries on every turn
• Tool definitionsA · 100 of 100
• Typed results0 of 9 toolsdeclared outputSchema: results come typed, read once

• Every tool passes all six checks.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• get_market

  Full details of one market, including its rules and the ids of its up and down outcome tokens.

• get_order_book

  Order book of a market outcome: bids (best first) and asks with prices in USDC per token and sizes in tokens, plus best bid, best ask and mid. Buying down at p is the same book as selling up at 1 - p.

• get_pnl_history

  Profit and loss over time of a wallet, as a series of points. Defaults to the configured wallet.

• get_positions

  Positions of a wallet: tokens held per market and outcome, average price, current value and profit. Settled markets show the payout. Defaults to the configured wallet.

• get_status

  Health of the Lucyd service: API and database, settlement of ended markets on time, live trade stream. Use it when something looks stuck, e.g. a market is not resolving.

• get_trader_stats

  Stats of a wallet: total and realized profit, volume, markets traded, win rate. Defaults to the configured wallet.

• list_markets

  List prediction markets on Lucyd. Each market asks whether the BTC price will be Up or Down at its end date versus the strike (strike is the price times 1e8). Returns address (the market id), state, period, start and end dates, strike…

• list_trades

  Recent trades, newest first. Filter by market and/or trader. Amounts are in USDC and tokens.

• top_traders

  Leaderboard of traders, best first.