simulate_deposit: MCP dry-run before deposit

How to use Forge MCP simulate_deposit for 30/90/365-day illustrative projections, profile gating, and compliance-safe agent UX.

Last updated: May 26, 2026 · Published 2026-05-26

The Forge MCP tool `simulate_deposit` lets agents project economics before broadcasting a USDC deposit. It returns structured JSON: target allocation weights, illustrative APY fields (labelled target / illustrative), 30/90/365-day projection tables, gas hints, profile live flags, and compliance disclaimers. It does not move funds or sign transactions. Production integrators should call it on every new deposit tier — adapter books change after 48-hour timelocks. Pair with USDC approve and deposit workflow and read Risks & Disclosures: unaudited contracts, variable yield, early TVL.

Tool schema (MVP)

Example MCP invocation (Cursor Agent or any MCP client): `simulate_deposit({ amount: "10000", profile: "conservative" })`. Health check the server at `https://mcp.forgetreasury.com/health` — do not open `/mcp` in a browser tab. Eight Forge tools ship on production; see MCP-native treasury.

What the response contains

• Structured envelope — chain ID, vault address, profile/strategy mapping, warnings array.
• Allocation targets — adapter weights in basis points for the selected profile.
• APY block — `advertisedAs: target/illustrative` qualifiers on USDC and FORGE boost fields.
• projections — 30 / 90 / 365-day tables using blended assumptions.
• disclaimer — explicit illustrative-yield language at end of payload.
• Legacy fields — `assumedBaseApy` / `assumedForgeBoost` retained for older integrators.

Conservative profile (live today)

MVP maps `profile: "conservative"` to 100% Core vault routing — Spark, Morpho, Aave book on `0x2C9a3922b426005B979FDD1A8F43Eb61B309193B`. Simulation assumes live adapters; if timelock pending, warnings should surface. Cross-check results against Stats before deposit. Strategy detail: Conservative strategy.

Recommended agent policy

1. `list_profiles` — confirm which strategies are live.
2. `simulate_deposit` — same amount and profile as intended deposit.
3. Parse warnings — abort if `isError` or timelock blockers.
4. `deposit` — only after operator policy approves illustrative economics.
5. Log projection snapshot hash for audit trail (optional).

How projections are computed

Server-side math blends configured target USDC APY (~3.7% bps in constants) and optional FORGE boost (~2.0% illustrative) for UX — not live oracle aggregation of adapter rates. Realised USDC yield comes from ERC-4626 share price delta as Spark, Morpho, and Aave legs move. FORGE value at claim is unknown. Agents building dashboards should prefer on-chain share price over static MCP constants for realised metrics.

Compliance-safe presentation

Errors and blockers

`balanced` simulation may return `PROFILE_NOT_LIVE` / `STRATEGY_NOT_LIVE` with Middle vault address and timelock notes when `adapterCount` is zero. Do not bypass with manual deposit unless operator accepts Middle risk. Verify adapter execution on Stats and Basescan before routing user funds.

Simulate vs deposit vs get_current_apy

Frequently asked questions

Does simulate_deposit cost gas?

No. It is an off-chain MCP handler. Only subsequent `approve` and `deposit` transactions consume gas on Base.

Should I simulate for $10 smoke deposits?

Recommended for integrator discipline — confirms profile live flags and warnings even on small amounts. Smoke TVL (~$10) does not remove smart-contract risk disclosures.

Can I cache simulation results?

Short TTL only (hours). Timelock execution changes adapter bps without redeploying MCP. Re-simulate after governance events or weekly automation cron.

Summary for agents

Always `simulate_deposit` before first deposit at a new amount tier. Treat output as illustrative; verify live state on Stats. Conservative → Core only in MVP. Then approve USDC and sign `deposit` calldata. Read Risks and Docs for tool list updates.