Platform · Model context protocol
kýklos MCP normalizes consented financial data — pensions, tax rules, cash flow, market assumptions, and equity compensation — into a single versioned planning schema that every downstream model reads from.
5
Connector extensions
25+
API & data sources
4
Jurisdictions covered
1
Normalized planning schema
Live topology
Israeli and international sources flow through their connector extension, into the normalized context store, and out to every consumer — including agents on the MCP tool surface.
Layered view
Raw upstream payloads never reach the planning engine. Each layer narrows the contract until only canonical, lineage-tagged entities remain.
L1 · Connector adapters
Per-source clients handling auth, pagination, rate limits, retries, and raw payload capture. Adapters are the only code that knows an upstream format.
L2 · Normalization & validation
Schema mapping, unit and currency coercion, deduplication, referential checks, and confidence assignment into canonical entities.
L3 · MCP context store
Versioned, effective-dated store of the canonical schema plus lineage and consent metadata. The single read surface for everything downstream.
L4 · MCP tool surface
Typed, read-scoped tools exposed over the Model Context Protocol so planning agents and assistants query context without touching raw connectors.
L5 · Planning & scenario engine
Forecasting, inheritance-tax modelling, probate-vs-trust comparison, and beneficiary review queues — all reading the same normalized context.
Extensions
Each extension owns its own adapters, refresh cadence, and failure modes — and writes into the shared schema through the same validation gate.
Balances, contributions, fees, tracks, policies, and benefit projections across every Israeli retirement vehicle and linked brokerage.
Sources
Writes entities
Account · Holding · PensionPolicy · Liability
Refresh
Daily balances · monthly statements
Versions the tax and social-benefit layer so every scenario output can reference the exact rule set in force at run time.
Sources
Writes entities
TaxRule · ScenarioOverride
Refresh
Event-driven · effective-dated
Turns payroll, transaction, lending, and milestone data into structured planning objects and review triggers.
Sources
Writes entities
CashFlowItem · Milestone · Liability
Refresh
Daily transactions · real-time events
Returns, rates, inflation, macro series, benchmarks, and pension-track performance used for simulation and backtesting.
Sources
Writes entities
MarketSeries
Refresh
Daily close · monthly macro
Grant to vesting to trustee release to tax event to sale proceeds — including Section 102 windows and concentration risk.
Sources
Writes entities
EquityGrant · Holding · TaxRule
Refresh
Daily FMV · event-driven vesting
Core
Ten entities describe an entire household balance sheet across jurisdictions. Connectors map into them; the planning engine reads only them.
Every record carries validation state, refresh cadence, effective dates, confidence score, consent reference, and source lineage as first-class fields — not as metadata bolted on later.
Every connector holds a scoped, revocable grant per data source. No fetch runs without an active consent record, and revocation cascades to derived context within one cycle.
Each normalized field carries the connector, upstream document, retrieval timestamp, and transform version. Any number on screen traces back to its origin.
Rules and market series are stored as effective-dated versions rather than overwritten. Re-running a 2024 scenario reproduces the 2024 answer exactly.
Scraped or inferred values are scored lower than authoritative API responses. The planning engine surfaces low-confidence inputs instead of silently modelling them.
Read surface
The tool surface is read-scoped by default. Writes are limited to explicit, user-confirmed actions such as a beneficiary review dispatch.
list_accountsreadAll aggregated accounts with institution, type, balance, refresh time, and confidence score.
get_pension_policyreadTrack, fees, contribution history, and benefit projection for a single pension or provident policy.
list_beneficiariesreadDesignations per account with status (ok / stale / missing / risk) and last review date.
get_tax_rulesreadEffective-dated rule set for a jurisdiction and date — used so scenarios are reproducible.
get_market_seriesreadIndex levels, yields, and CPI series backing forecast and backtest assumptions.
list_equity_grantsreadGrants, vesting schedules, Section 102 trustee windows, and unrealized position value.
run_scenarioreadExecutes a planning scenario against a pinned rule-set version and returns the assumption trace.
dispatch_reviewwriteSubmits confirmed beneficiary updates to institutions. Requires explicit per-item user confirmation.
Architecture draft, June 2026 revision. Illustrative connector set — integration availability varies by institution and consent regime.