Skip to content
Clark

One agent. Every financial action.

Clark is being built to plan payroll, investments and cross-border payments, asking for your approval before money moves. It is designed to connect Krypton’s financial tools and give external AI agents access through MCP.

The interface

Two products. One interface.

Clark is designed to bring Krypton Pay and the Yield Engine behind one interface: a single MCP endpoint for agents. The example shows the initialization request and an abridged response.

POSThttps://clark.kryptonfund.com/mcp
curl -sN https://clark.kryptonfund.com/mcp \  -H 'Content-Type: application/json' \  -H 'Accept: application/json, text/event-stream' \  -d '{"jsonrpc":"2.0","id":1,"method":"initialize",       "params":{"protocolVersion":"2024-11-05","capabilities":{},                 "clientInfo":{"name":"you","version":"1.0"}}}'
Example response · abridged200 · text/event-stream
event: messagedata: {"jsonrpc":"2.0","id":1,"result":{  "protocolVersion":"2024-11-05",  "serverInfo":{"name":"Krypton Strands HTTP MCP","version":"3.4.5"}}}

Krypton Pay and the Yield Engine: the capabilities Clark is built to reach. Their money movement is planned, not live.

Clark is the orchestration layer between them: one runtime across both products.

One MCP interface for agents. The example request initializes a session; the response shown is abridged.

Read the docs (opens in a new tab)
Your money, understood

Clark sits across your whole financial life.

Payments, portfolio, yield and tax are one surface to Clark, and it acts on natural language in real time, which is only safe because every action it takes is bounded by a mandate you wrote and, where it moves money, gated by an approval you give.

Understands

Payment patterns, portfolio composition, risk tolerance, tax constraints and jurisdictional limits.

9:41
You

Run payroll for the full team — same as last month.

Clark

Twelve people, four currencies, each settling as a direct pair.

INR6 people
AED2 people
EUR2 people
GBP2 people
All-in cost$230

Illustrative example · planned capabilities

Capabilities

What Clark does once it is connected.

Four behaviours the runtime brings to every request it is handed, whether that request came from you, from a schedule, or from another agent over MCP.

Watch the demo (opens in a new tab)

Illustrative product preview

Understands full financial context

Payment patterns, portfolio composition, risk tolerance, tax constraints, jurisdictional limits. Clark supports the complete picture.

How it works

Six moments. One thread.

The app, drawn rather than filmed: a request chosen out of what Clark can actually run, answered with its working attached, and then a payment made in the same thread. Pick a moment and it jumps there.

01 / 06 · Understands

One control from the balance

9:41

Hello @Rhea

Active
Your Balance$14,263.3110.2%All Currencies12,000.00USD2,220.00AED10,200.00INR400.00USDC850.00GBP
PayGrowAsk
Clark
You

Backtest Gold from 01/01/2025 to 09/09/2025 with 1000 USD

Clark

Processing…

The backtest for Gold from January 1 to September 9, 2025, using $1,000 of initial capital, shows a total return of 39.47%, a Sharpe ratio of 2.55, and a maximum drawdown of 6.95%. The historical price data for this period was retrieved successfully.

Final Value$1,394.72
Total Return39.47%
Sharpe Ratio2.55
Max Drawdown6.95%
Trade History1 trade executed during backtestShow Details

GOLD/USDT Price Chart

OHLC Candlestick Chart

Portfolio Performance

Portfolio value over time from 01/01/2025 to 09/09/2025

Portfolio Allocation

Final allocation percentages by asset

Asset Performance

Individual asset returns during backtest period

You

Send 100 AED to @Arjun

Clark
Transfer completeDelivered 100.00 AED to @Arjun5s
Send 100.00 AED to @ArjunStep 3/3
  1. Queued
  2. Submitted
  3. Confirmed
0x9c41ab07…5e2d8f14
Ask ClarkBacktest Gold from 01/01/2025 to 09/09/2025 with 1000 USDSend 100 AED to @Arjun
Run payrollSend moneyPay invoicesGrow idle cashFX savings
Strategy & BacktestingTest portfolio strategies
Backtest a 100-day SMA filter on Gold; stay in cash when below SMA; from 2024-01-01 to 2024-09-30 with $12,000Copied
Backtest Gold from 01/01/2025 to 09/09/2025 with 1000 USDCopied
Backtest Bitcoin & Ethereum with 50% each from 01/01/2025 to 09/09/2025 with 1000 USDCopied
Backtest a 50/200 EMA crossover on BTC from 2024-01-01 to 2024-06-30 with $5,000Copied
Backtest RSI strategy on Bitcoin from 2024-01-01 to 2024-06-30 with $10,000Copied
Backtest portfolio with 60% Bitcoin, 30% Ethereum, 10% Solana using 10000 USD from 2024-01-01 to 2024-12-31Copied
Backtest monthly momentum on BTC, ETH, SOL (hold top 2 each rebalance) from 2023-01-01 to 2024-01-01 with $15,000Copied

Clark opens from the wallet, not from a second app. And it opens on what it can actually run: the stack's jobs, one tap away in the bar you ask in, and behind them requests that execute rather than prompts to adapt.

The wallet, with Clark opened from it. The Ask Clark bar with its row of shortcuts, and a Strategy & Backtesting panel opening from the bar's more button onto example requests, one of which is copied.

01: One control from the balance

< 15 seconds

Typical response time for most requests.

MCP

AI agent protocol.

Multilingual

Multiple languages supported.

Tool surface

An agent asks. A human approves.

Clark exposes a query tool and an approval tool. The preview below shows the approval flow planned for a payment request: the agent asks, the run stops at an interrupt, and a person decides.

tools/list
  • 2 tools
  • streamable HTTP
  • responses as SSE

Interactive preview · approval behaviour planned

01Agent request

krypton_query

Routes a natural-language query through the remote Krypton orchestrator, across Pay and the Yield Engine.

Example: prepare a supplier payment

02Human approval

krypton_approve_interrupt

Approves or rejects a pending interrupt before the run continues.

stops atkrypton-pay-approval

03Continuation

After approval, the proposed run can continue.

Illustration only · no payment submitted

krypton_query routes a natural-language request through Clark, across Pay and the Yield Engine.

Before the three calls, one file

The endpoint is registered the way any MCP server is. Nothing here is Krypton-specific except the URL and who you say you are.

jsonclaude_desktop_config.json
1{2  "mcpServers": {3    "clark": {4      "type": "http",5      "url": "https://clark.kryptonfund.com/mcp",6      "headers": {7        "X-Username": "krypton",8        "X-User-Id": "7895abe0-d992-488a-a848-e6b5bd0e300f"9      }10    }11  }12}

Connecting takes three calls, not one

The endpoint is a streamable HTTP transport, so the handshake has a shape worth stating plainly rather than hiding behind a one-liner that would fail.

  1. initialize

    Returns the server's capabilities and an Mcp-Session-Id response header.

  2. notifications/initialized

    Echo the session id back as a request header. Every later call needs it.

  3. tools/list

    Now the tool surface resolves. Responses stream as SSE, not plain JSON.

And what it resolves to is the two tools above. That is the whole surface.

Built-in financial agents

A registry with attribution built in.

Every agent call is tracked, metered and attributed. The registry is designed around four agents, covering the operations Krypton is being built to run.

  • Payments

    Krypton Pay

    Cross-border settlement and payroll. Called for anything that moves money between currencies.

  • Allocation

    Yield Agent

    Strategy routing across vaults. Called when idle capital has to be placed against a mandate.

  • Quant

    Backtesting

    QuantConnect Lean. Called to run a strategy over historical data before any capital is committed.

  • Compliance

    Tax Agent

    Jurisdiction-aware. Called to check what a proposed action means where the money actually lands.

On the roadmap

Planned, and labelled as planned.

Neither of these has shipped. They are on this page because a roadmap stated openly is worth more than a roadmap implied by silence.

  1. Planned

    Developer Platform

    Developers deploy custom financial agents onto Clark's runtime, earning per call, per unit of AUM, or per unit of yield generated.

  2. Planned

    Agent Marketplace

    A registry where third-party agents are discovered, metered and monetised alongside the built-in set.

Generally availableNeither item has reached this stage.

Be told when each of these lands, rather than finding out from the changelog.

Join the waitlist
Build on Clark

Give your agent
a balance sheet.

Explore Clark’s integration guide, or join the waitlist for the Developer Platform.