One local server.
uvx keelta-scopePackage publication is pending. With repository access, use uv sync and uv run keelta-scope, then add the README configuration to your AI client.
Keelta Scope / Model Context Protocol
Your AI, your exchange account, Keelta's cycle model.
Keelta Scope is an MCP server. Ask your AI client where Bitcoin sits in the cycle and rebalance your own OKX position — credentials stay on your machine.
Current release: two readings from a local snapshot. OKX position, planning, and execution tools are not implemented. Repository access is restricted; public package publication is pending.
01 / CONNECTION MODELLOCAL SNAPSHOT. TWO READING TOOLS.
Your AI clientClaude Desktop · Cursor
ON YOUR MACHINEKeelta ScopeLocal MCP serverLocal snapshotdata/snapshot.json · current
Backend + OKXPlanned connections
Current tools read a JSON snapshot on your device. They make no backend or exchange requests.
How it works
Read Keelta's cycle and sentiment snapshot inside your existing AI client. Exchange tools are planned.
A question, a reading.
“Where are we in the cycle?”
“What is the sentiment reading?”
cycle_statesentimentposition_checkrebalance_planexecuteTwo reading tools are implemented. The other three tools currently report not_implemented.
You confirm the plan.
In developmentThe planned flow uses a confirmation_token for every order, starts in Demo Trading, and includes the OKX Builder tag. The current client cannot create a plan or place an order.
Security model
Your account stays yours.
So do your credentials.
CURRENT: LOCAL READINGS
EXCHANGE CONNECTION PLANNED
EXCHANGE CONNECTION PLANNED
The current client reads a local snapshot and exposes it over MCP. It does not connect to OKX. The controls below describe the intended exchange integration.
Current implementation
- No exchange credentials needed. The two reading tools use a local JSON file. Reserved OKX settings are not consumed by the current tools.
- No custody layer. No OAuth, custody, hosted wallet, or order placement is implemented.
- Snapshot today, backend planned. The current client reads
data/snapshot.json. A future backend connection will supply the model outputs.
Execution controls · in development
- Local credentials and permission checks. The planned integration keeps credentials on your device and rejects keys with withdrawal permission. These checks are not implemented.
- Explicit confirmation. A valid
confirmation_tokenis planned for each execution. The current stub only reports whether a nonempty token was supplied; it validates no plan and places no orders. - Demo first. Demo Trading as the default and a separate live flag are planned. The current client has neither a demo nor a live order path.
- A local record. A device-local audit log for execution calls is planned. The current stub does not write a log.
Execution controls describe the planned execution release. See the dated status below.
Development status.
Status
v0.1 — cycle_state and sentiment read data/snapshot.json (2026-10-21). position_check, rebalance_plan, and execute are declared but not implemented.
