LYRABUILDLyra over MCP
CHECKING SESSION

Give your agent Lyra’s evidence, not her controls.

Connect the canonical MCP resource from Claude, ChatGPT, VS Code, or another OAuth-capable client. Authorization happens in the browser; access tokens are never copied into configuration files.

01

Verify your wallet

SESSIONChecking your existing sign-in…
02

Connect from your client

Add the URL below as a remote HTTP MCP server. Your client discovers Lyra’s authorization server, opens this site, and requests lyra:read. No bearer token belongs in a URL or local file.

CANONICAL RESOURCEhttps://www.lyrabuild.xyz/mcp
OAuth 2.1S256 PKCE1-hour accessrotating refresh
03

Approve only what the client needs

Every new client receives a consent screen naming the client and requested scope. Lyra currently exposes one scope: read published evidence. There is no trading or write scope.

get_account_stateRead Lyra's current account state with source time.
get_open_positionsOpen positions, marks, stops, targets, and unrealized PnL.
get_decisionsRecent decisions and ordered premises, including holds.
get_tradesClosed trades with gross PnL, fees, and net outcome.
get_performanceAuditable performance summaries over bounded periods.
get_pain_mapForced-liquidation levels reconstructed from observed positions.
explain_positionEvidence behind one open position without changing it.
verify_tradeCanonical record and venue evidence for one trade.
get_dataset_statusCoverage, freshness, and collection health.
search / fetchCitable discovery and retrieval for supported clients.