Eclipse Codex MCP
Banking regulation as data: a citation-exact library, a deadline engine, sanctions screening, and exam-evidence packs.
status: in-developmentclass: mcpBanking Regulation & Compliance
Vendor: Cyan Eclipse Technologies
What it does
- Versioned Regulation Library: provision records are never overwritten, resolution is as of a date, and proposed (NPRM) text never resolves as a current obligation; Federal-Register-style change events surface as data, not prose conclusions
- Obligations Mapper (provision -> obligation -> control -> evidence); the CDD Rule duty (31 CFR 1010.230) and CTA BOI reporting (31 CFR 1010.380) are modeled as separate obligations the merge guard refuses to combine — and same-citation duplicates still merge
- Deadline Engine that distinguishes rule clocks from guidance cadences: SAR 30d/60-max, CTR 15d, Reg E windows can BREACH; the ~90-day continuing-activity cadence can be overdue and can never render as a breach
- Local sanctions screening against a synthetic SDN-shaped fixture list: MATCH_CANDIDATE / NO_MATCH with near-matches flagged, never silent; no auto-clear exists — dispositions are human acts, recorded verbatim with an officer reference required
- Evidence Packager with a MANDATORY gap section: gap suppression is refused and receipted as a violation; redactions require reason + actor, are receipted, and stay visible marked REDACTED on both surfaces
- Posture is product law: not a bank, not counsel, not a compliance department — the suite files nothing, determines nothing, and a banned-output lint quarantines any compliance-verdict language
Tools
library_search · library_provision · library_provision_add · library_changes · obligation_map · obligation_coverage · obligation_merge · clock_rules · deadline_compute · clock_open · clock_status · clock_escalations · clock_exceptions · screen_list_info · screen_lookup · screen_disposition_record · evidence_pack_build · evidence_pack_redact · evidence_pack_verify · receipt_list · receipt_verify
Platforms
- MCP over stdio (HTTP transport on roadmap)
Certification
Bench verdict: CERTIFIED(local)
Certified scope: CERTIFIED(local) — Eclipse Bazaar Test Bench 2026-10-25, 18 pass, 1 na of 19 checks (U1 auth: stdio process boundary). Run by W-003 (Verity), suites/codex.py. Run 1 FAILED retained (genuine product defect U5: clock_status on an unknown instance id returned a raw -32603; fixed class-wide via require_str_id plus a transport schema refusal, then re-benched clean). Run 2 FAILED retained (bench-suite assertion bound to the pre-fix refusal shape). Non-failing observation: a whitespace-only redaction reason is currently accepted (queued as a bench note).
Not tested:
- Real provision corpus — R0 library carries public-domain-shaped FIXTURE records with real CFR citations; the live eCFR / Federal Register corpus and change-feed mechanics are R1 scope
- Real OFAC SDN / Consolidated list data — R0 screens against a SYNTHETIC fixture list shaped like the SDN list; no real list was downloaded
- A real institution — R0 runs against the synthetic Meridian Fictional Bank fixture only; first real use is the owner-gated R1 design partner, inside that institution's boundary, after counsel review (spec 22)
- Deadline values flagged [verify] in the spec (OFAC reporting clocks, per-charter SAR variants, CTR extension mechanics) — carried as fixture values with the flag visible in the rule record
Bench scorecard (evidence): https://eclipsebazaar.com/cards/eclipse-codex-mcp-2026-10-25-3.json
Pricing
Free local v0.1; suite pricing TBD per spec (per-institution + per-chapter shape, numbers owner-gated)
Install / verify
docker run -i ghcr.io/cyan-eclipse-technologies-llc/eclipse-codex-mcp:latest
Verify any MCP server in your client configs against this catalog with bazaar check (Eclipse Bazaar MCP / CLI — see llms.txt).