Lucyd
REMOTE · MCP.LUCYD.TRADE · 2 COMPONENTS
Trade Bitcoin Up/Down prediction markets on Lucyd: markets, order books, orders, positions.
Available components
Last scanned (14 hours ago)
Scores higher than 63% of remote servers
Reachable. Last reached 22 Oct 2026.
Category Finance and Payments
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 925 tokens (~102/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 20 Oct 26 71
First indexed and scored.
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 22 Oct 2026 · Probed https://mcp.lucyd.trade/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=lucyd.trade | CN=WE1,O=Google Trust Services,C=US | 7 Oct 2026 | 5 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 1378769f6fd51e900e3fa5334353e47d |
| SANs: lucyd.trade, *.lucyd.trade, *.testnet.lucyd.trade | ||||||
| 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.lucyd.trade. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| trade. | present | 64969 | 8 | Verified |
| lucyd.trade. | absent | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.lucyd.trade/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.lucyd.trade/mcp | HTTPS enforced | 301 | https://mcp.lucyd.trade/mcp |
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 →
get_market Get market ~45
Full details of one market, including its rules and the ids of its up and down outcome tokens.
| Name | Type | Req | Description |
|---|---|---|---|
| market | string | yes | Market address (its id), from list_markets. |
No output schema declared.
No examples provided.
get_order_book Get order book ~90
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.
| Name | Type | Req | Description |
|---|---|---|---|
| market | string | yes | Market address. |
| outcome | string|null | – | Outcome whose book to show: up or down. Default up. |
No output schema declared.
No examples provided.
get_pnl_history Get P&L history ~75
Profit and loss over time of a wallet, as a series of points. Defaults to the configured wallet.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string|null | – | Wallet address. Default: the configured wallet. |
| range | string|null | – | Period: 1d, 1w, 1m or all. Default 1w. |
No output schema declared.
No examples provided.
get_positions Get positions ~115
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer|null | – | How many positions, 1 to 100. Default 50. |
| market | string|null | – | Only this market address, or several comma separated. |
| state | string|null | – | Market state filter: open, pending, settled or voided. |
| trader | string|null | – | Wallet address. Default: the configured wallet. |
No output schema declared.
No examples provided.
get_status Service status ~46
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_trader_stats Get trader stats ~50
Stats of a wallet: total and realized profit, volume, markets traded, win rate. Defaults to the configured wallet.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string|null | – | Wallet address. Default: the configured wallet. |
No output schema declared.
No examples provided.
list_markets List markets ~194
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, winner and volume.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer|null | – | How many markets to return, 1 to 100. Default 20. |
| offset | integer|null | – | Skip this many markets, for paging. |
| order | string|null | – | Sort by end date: asc or desc. Default desc. |
| period | string|null | – | Market period: 5m, 15m, 30m, 1h, 4h or Daily. Comma separated for several. |
| state | string|null | – | Market state: open, pending (ended, waiting for result), settled or voided. Comma separated for several. |
No output schema declared.
No examples provided.
list_trades List trades ~120
Recent trades, newest first. Filter by market and/or trader. Amounts are in USDC and tokens.
| Name | Type | Req | Description |
|---|---|---|---|
| from | integer|null | – | Only trades after this time, unix seconds. |
| limit | integer|null | – | How many trades, 1 to 100. Default 20. |
| market | string|null | – | Only trades on this market address. |
| to | integer|null | – | Only trades before this time, unix seconds. |
| trader | string|null | – | Only trades of this wallet. Use "me" for the configured wallet. |
No output schema declared.
No examples provided.
top_traders Top traders ~60
Leaderboard of traders, best first.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer|null | – | How many traders, 1 to 50. Default 10. |
| sort | string|null | – | Sort field: pnl, volume, markets or win_rate. Default pnl. |
No output schema declared.
No examples provided.
How do I install the Lucyd MCP server?
Lucyd is a hosted endpoint at https://mcp.lucyd.trade/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 · mcp.lucyd.trade
claude mcp add --transport http trade-lucyd-mcp 'https://mcp.lucyd.trade/mcp'
What is the Lucyd MCP server?
Lucyd is an MCP server listed in the public MCP registry as trade.lucyd/mcp. Trade Bitcoin Up/Down prediction markets on Lucyd: markets, order books, orders, positions. This page covers its hosted endpoint (https://mcp.lucyd.trade/mcp).
Is the Lucyd MCP server safe to use?
Lucyd scores 72 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 Lucyd MCP server expose?
Lucyd exposes 9 tools: get_market, get_order_book, get_pnl_history, get_positions, get_status, and 4 more. Their descriptions and schemas cost roughly 795 tokens of context every time the server is loaded.
Does the Lucyd MCP server require authentication?
No. We connected to Lucyd without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Lucyd MCP server still maintained?
Lucyd is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.