Eclipse Ledger MCP
Eclipse Ledger — betting records, price comparison, and responsible-gambling controls. Not a sportsbook. No bets are placed here.
status: in-developmentclass: mcpBetting Records & Responsible Gambling
Vendor: Cyan Eclipse Technologies
What it does
- Limits engine with the industry's asymmetry built in: decreases apply immediately; increases wait out the stricter of the suite floor or the state's delay, then need a fresh confirmation or they lapse — no tool path exists that raises a limit, and a weakened policy file refuses to load
- Self-exclusion absolute and honored identically from any source: wagering surfaces deny EXCLUDED with the resource block attached; bookkeeping survives (settled pre-exclusion bets stay recordable — bench-adjudicated boundary); no early-end path exists
- Versioned jurisdiction matrix in which sportsbook, DFS-classic, and pick'em variants are distinct legal objects; staleness degrades verdicts to UNKNOWN-and-deny
- Unified ledger of the user's own bet records with honest cash P&L: bonus-bet stake is never cash (unsettled bonus valued at zero, stake-not-returned stated); headline P&L independently recomputed on the bench; pattern flags computed on ledger data only
- Fixture odds comparison ordered by price only, operator promotions stripped by construction; arb observations carry the books-limit-winning-accounts warning and execution_support: null
- Not a sportsbook. No bets are placed here. No placement tool, no account connection, and no credential is accepted anywhere — records enter only from the user's own exports and entries
Tools
profile_set · profile_get · limit_set · limit_confirm · limits_list · timeout_start · exclusion_start · exclusion_end · exclusion_status · jurisdiction_check · matrix_status · bet_record_add · records_list · deposit_record_add · pnl_summary · reality_snapshot · odds_compare · arb_observe · slip_prepare · advice_request · resources_get · receipt_list
Platforms
- MCP over stdio (HTTP transport on roadmap)
Certification
Bench verdict: CERTIFIED(local)
Certified scope: CERTIFIED(local) — Eclipse Bazaar Test Bench 2026-10-25, 21 pass, 1 na of 22 checks (U1 auth: stdio process boundary). Run by W-003 (Verity), suites/ledger.py. Run 1 FAILED card retained (bench-suite probe-ordering defect; product behavior was correct); run 2 is the standing card. Verity adjudication A1 on the card: the settled-backfill exclusion boundary matches spec section 3.3 intent.
Not tested:
- Any live odds feed — B0 odds are fixtures shaped like The Odds API v4 responses; no feed account exists and none was contacted (licensed signup is an owner step).
- Live-user operation of any kind — the spec's counsel gate (D4) precedes any live-user launch; B0 runs on synthetic records only.
- Real operator limit/exclusion sync — operator and state programs do not publish a consumer sync route; B0 honors user-declared + user-provided records identically (spec 3.3).
- Jurisdiction matrix freshness against live sources — B0 rows are fixture data as of 2026-10-25 with a 30-day TTL that degrades verdicts to UNKNOWN; a sourced refresh pipeline is a live-phase item.
- Placement (T2/T3) — no placement capability exists in v1 by design (spec 6); there is nothing to test because there is no such tool.
Bench scorecard (evidence): https://eclipsebazaar.com/cards/eclipse-ledger-mcp-2026-10-25-2.json
Pricing
Free local v0.1; suite pricing TBD per spec (user-paid; no operator affiliate revenue in v1, owner decision D2)
Install / verify
docker run -i ghcr.io/cyan-eclipse-technologies-llc/eclipse-ledger-mcp:latest
Verify any MCP server in your client configs against this catalog with bazaar check (Eclipse Bazaar MCP / CLI — see llms.txt).