MCP Server
SukukFi runs a public Model Context Protocol server, so AI assistants can query live protocol data and this documentation directly rather than working from a stale training snapshot.
Connect
In Claude Code:
claude mcp add --transport http sukukfi https://mcp.sukuk.fi/mcp --scope user
Any MCP-compatible client works. The endpoint is https://mcp.sukuk.fi/mcp, streamable
HTTP transport, no API key and no account required.
What it exposes
| Tool | Returns |
|---|---|
get_vault_stats | Live per-vault capital held, pending deposits and redemptions, participant counts, straight from Berachain |
search_docs | Ranked search across this documentation and the SukukFi blog |
get_doc | A full documentation page as markdown |
get_contracts | Verified contract addresses with explorer links |
get_vault_terms | Current vault terms: target yield, capacity, minimum, lockup, accepted assets |
Once connected you can ask things like “what is the current capital held in the SukukFi vaults?”, “how does SukukFi assess obligor credit risk?” or “what are the contract addresses on Berachain?” and get answers grounded in live data.
Scope and limits
Public data only. The server reads the same on-chain snapshot that powers the site and the same documentation you are reading now. Confidential investor materials are not reachable through it.
Read-only. There are no tools that move funds, sign transactions or change state. It cannot deposit, redeem or approve anything.
Not advice. Yields reported are illustrative targets, not guarantees, and figures are a point-in-time snapshot. Nothing returned by the server is investment advice.
A note on the TVL figure
get_vault_stats reports each vault’s raw asset balance, not totalAssets(). Per the
vault source, totalAssets() deliberately excludes pending deposits, claimable redemptions,
cancellations and capital already invested, so reading it as a TVL figure undercounts the
real position, sometimes to zero while deposits are sitting in the vault. See
Smart Contracts for the full explanation.