cyan-eclipse-book
mcp-name: io.github.CYAN-ECLIPSE-TECHNOLOGIES-LLC/book
What this is: the MCP server for Eclipse Book MCP - The Market Core of the Eclipse Markets suite (spec eclipse-markets-suite-spec-20261025): one canonical Instrument / Book / Quote / Order / Position / Resolution model over exchanges and prediction markets, with venue adapters that translate and never improvise. Resolution criteria are stored verbatim and hash-pinned — a venue criteria edit is a CRITERIA_CHANGED event and positions keep the criteria as of entry. Quotes carry all-in buy/sell cost for a stated size from versioned, provenance-stamped fee schedules; a stale or missing schedule degrades all-in fields to FEE_UNVERIFIED rather than quoting a wrong number. Resolutions move REPORTED -> VERIFIED only against the criteria's own named source (DISPUTED is first-class), and no core output ever carries a probability field — outputs carry price + liquidity flag + depth + verbatim criteria. M0 is data only: no accounts, no keys, no order submission at any tier; order_draft is an unsubmitted record whose mandate pre-evaluation is honestly NOT_EVALUATED until the owner-gated M2.
Run it
$ pip install cyan-eclipse-book
$ eclipse-book # MCP over stdio, Python stdlib only
MCP client config:
{ "mcpServers": { "cyan-eclipse-book": { "command": "uvx", "args": ["--from", "cyan-eclipse-book", "eclipse-book"] } } }
Tools (17)
instrument_ingest - instrument_get - instrument_search - book_ingest - quote_get - fee_schedule_register - fee_schedule_get - position_open - position_list - position_get - resolution_report - resolution_verify - resolution_get - order_draft - order_get - venue_status - receipt_list
Honest scope
- In development — v0.1.0 M0 local build (Market Core, data only; fixtures behind transport seams; CERTIFIED(local) — Eclipse Bazaar Test Bench 2026-10-25)
- State and runtime data files ship in the wheel beside
server.py, at the same relative paths the server reads them from.
Powered by Cyan Eclipse Technologies LLC (cetech.ai) - a Veteran-Owned Small Business. MIT licensed.
Metadata
Release files for cyan-eclipse-book 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| cyan_eclipse_book-0.1.0.tar.gz | 38.2 kB | With provenance | Details for cyan_eclipse_book-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cyan_eclipse_book-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for cyan_eclipse_book-0.1.0-py3-none-any.whl |
Total release size: 57.5 kB
Release files / cyan_eclipse_book-0.1.0.tar.gz
| Download URL | cyan_eclipse_book-0.1.0.tar.gz |
|---|---|
| Size | 38.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1018b789110a43f8d97e0910e47914bd9d2e901024419a6ca86a2ba1cd8a62d8
|
|
BLAKE2b-256 checksum How to use checksums |
0db6f8765b277ff9db0e8fcf780cfe99395ab2de1cac832110407c7d06f874e7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logRelease files / cyan_eclipse_book-0.1.0-py3-none-any.whl
| Download URL | cyan_eclipse_book-0.1.0-py3-none-any.whl |
|---|---|
| Size | 19.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
429b8cba6b3f15e48966443fccd4a8cf4c30cdb1731247886d0d5c56ed9a4a91
|
|
BLAKE2b-256 checksum How to use checksums |
ffdff6cad4176c52d59a93a8379639d544534dd3fe4114b1038e7aff751b5b4c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logSecurity for cyan-eclipse-book 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for cyan_eclipse_book-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 3, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.