Want to use your own AI? Check out our new MCP-only product →
Want to use your own AI? Check out our new MCP-only product →
Why crypto portfolios need an analytical layer more than most
Crypto holdings are where the lack of cross-account intelligence hurts the most. Most retail investors hold their crypto across at least two venues — Coinbase for the convenience, Kraken or another exchange for the assets Coinbase doesn't list, and increasingly self-custody on top. Each venue gives you a portal that shows what you own there. None of them show you what you own across the whole picture.
That's the gap OpenClaw plus Truthifi closes. Your self-hosted OpenClaw becomes a single conversation surface that can see all of your crypto holdings, normalized into one view, alongside your traditional brokerage accounts if you've connected those too. Ask "what percentage of my total net worth is in BTC?" and OpenClaw can answer — pulling Coinbase, Kraken, and any traditional accounts in one query.
Crypto specifically benefits from this kind of analytical layer because volatility makes everything time-sensitive. The position size that was 4% of your portfolio last month is 7% today. The cost basis on the lots you're thinking about selling matters for tax purposes and changes constantly. Manually tracking this across multiple exchanges is exactly the work AI agents are good at — once they know what you own.
There's a second-order benefit specific to OpenClaw: privacy. Many crypto holders prefer not to send portfolio data to a SaaS aggregator dashboard, much less to a hosted LLM provider. Self-hosted OpenClaw with Truthifi keeps the conversational reasoning on infrastructure you own. Your AI agent answers "what's my BTC concentration?" without sending the answer to anyone outside your own host. For privacy-conscious users — which most serious crypto holders are — that's a meaningful design point.
A worked example. A crypto holder on the privacy-conscious end of the spectrum runs OpenClaw on a personal VPS, with Truthifi connected to read Coinbase and Kraken. Their workflow: Sunday-night analysis on the web channel ("review my crypto exposure relative to my non-crypto holdings, identify any tax-loss-harvesting candidates"), Tuesday Discord-based check-ins from their phone with a small group of other holders ("how am I tracking on the BTC concentration target we set?"), Wednesday Telegram quick balance ping while traveling. Same OpenClaw, same Truthifi, three channels, no third-party AI provider in any of those flows. The privacy posture that made them choose self-hosted in the first place is preserved end-to-end for the most-sensitive financial questions.
Multi-channel matters in crypto specifically because crypto news moves fast. You may be at a party when major BTC news breaks. Pull out your phone, ask the OpenClaw Telegram bot what's going on with your positions and what X is saying — get a real answer in seconds rather than having to open multiple apps to triangulate. The architecture optimizes for the way active crypto holders actually live.
The connection, explained
Truthifi connects to Coinbase and Kraken through their respective official APIs (read-only scopes). Truthifi normalizes the data into a consistent schema — the same schema it uses for traditional brokerages — and exposes it to OpenClaw via the Model Context Protocol.
OpenClaw, running on your own infrastructure, registers Truthifi as an MCP server. Once registered, every conversation across every OpenClaw channel can ask questions that draw on your Coinbase and Kraken positions in real time. The crypto data flows through the same pipeline as everything else — there's no special-casing for crypto in OpenClaw.
The OAuth handshake happens between you and Truthifi (and separately between Truthifi and each exchange when you initially link). OpenClaw never sees your exchange credentials. The token issued to OpenClaw is read-only and scoped to the tools OpenClaw needs.
What you need
A self-hosted OpenClaw instance you can configure (web shell, SSH, or local Node environment).
A Truthifi account with Coinbase and/or Kraken already linked. (New to Truthifi Connect?)
Either Node.js 20+ for the
mcporterskill path, or text-editor access to~/.openclaw/openclaw.jsonfor the direct-config path.
That's it. No exchange API keys to copy into OpenClaw. No browser automation. No DIY scraping of exchange portals.
Setup: five steps
Detailed walkthrough is in the full setup guide: How to Connect Your Portfolio to OpenClaw via Truthifi MCP. Condensed here:
Link Coinbase and Kraken to Truthifi. Sign in to truthifi.com → Connections → add each exchange. The OAuth flow happens once per exchange and never again.
Add Truthifi to OpenClaw. Either run
mcporter install --target openclaw truthifi(Path A) or add Truthifi to themcpServersblock of~/.openclaw/openclaw.jsonwithtype: "http"andurl: "https://api.truthifi.com/mcp"(Path B).Restart the OpenClaw gateway. Required after a config edit; not needed if you used
mcporter.Authenticate via OAuth on first call. Ask any crypto question in OpenClaw. The first call triggers an OAuth authorization in your browser. Sign in to Truthifi, grant the read-only scope, return to your OpenClaw session.
Verify. Try a prompt like "Show me my BTC and ETH balances across Coinbase and Kraken with current USD value." Real numbers should come back.
If your OpenClaw runs behind a reverse proxy, set MCP_ISSUER_URL to your public HTTPS URL — otherwise OAuth metadata advertises localhost and the redirect fails. Most reverse-proxy gotchas trace to this single setting.
The security model for crypto accounts specifically
The crypto question gets people more nervous than the traditional brokerage question, with good reason — exchange security is its own discipline. The architecture here is designed around that:
Read-only tokens at the exchange level. When you link Coinbase or Kraken to Truthifi, the OAuth scope you grant is read-only. There is no path through Truthifi's connector to a withdrawal endpoint. Even if Truthifi's connection were compromised at any point, withdrawals from your exchange account would still require the standard exchange-side authentication that OpenClaw and Truthifi don't have access to.
No exchange credentials on the OpenClaw host. Self-hosting is a specific concern here — you're running a Node.js process on a machine you control, and credentials on that machine are credentials at risk. Truthifi's design keeps your Coinbase and Kraken credentials at Coinbase and Kraken. The OpenClaw host only sees a Truthifi-scoped OAuth token.
Truthifi's exchange connections are managed centrally. When an exchange's API changes — and they change often — Truthifi handles the upgrade on its side. You don't need to update your OpenClaw config or rotate keys. The MCP contract OpenClaw sees stays stable while the underlying exchange integrations evolve.
Per-host audit trail. Every Truthifi tool call from OpenClaw is logged with the OpenClaw user identity and channel (web, Discord, Telegram). If something looks anomalous later, you can trace which channel asked what. Especially relevant for shared OpenClaw hosts in family or advisor settings.
Wallet-address tracking, no key exposure. If you also self-custody, Truthifi can read on-chain balances by watching wallet addresses you've registered. The wallet keys never leave your custody — Truthifi only reads what's publicly visible on-chain at the address. OpenClaw sees the same view, with self-custody balances integrated into the same query as your exchange holdings.
Hard limits: what OpenClaw cannot do with your crypto accounts
Spelled out unambiguously:
No trades. OpenClaw cannot place buy or sell orders on Coinbase, Kraken, or any other exchange.
No withdrawals. OpenClaw cannot move crypto off your exchange or to another wallet.
No deposits. OpenClaw cannot move funds in.
No exchange-account modifications. OpenClaw cannot change your security settings, add 2FA devices, change your linked email, or modify any exchange account property.
No Truthifi-account modifications. Adding or removing exchange links is something you do from truthifi.com, not from OpenClaw.
No off-platform sharing. OpenClaw doesn't ship your crypto data to any third party. Truthifi doesn't either.
No wallet-key exposure. Even for self-custody addresses, Truthifi reads addresses, never private keys.
The asymmetry is intentional: read everything, write nothing. It's the right shape for a self-hosted agent that talks to crypto exchanges.
Supported exchanges
Truthifi's MCP supports the major US-accessible exchanges where it's economically reasonable to maintain an integration:
Coinbase (including Coinbase Pro/Advanced)
Kraken
Gemini (via Truthifi's broader exchange roster)
Binance.US (where available)
Plus self-custody read-only via wallet-address tracking for Bitcoin, Ethereum, and major chains
The exchanges OpenClaw will actually see depend on what you've linked in Truthifi. If you have Coinbase and Kraken linked, those are what OpenClaw can query. Add a third exchange in Truthifi later, and OpenClaw picks it up automatically — no config change needed in OpenClaw.
The total-picture argument
The thing that makes the OpenClaw approach especially useful for crypto is that crypto questions almost always benefit from context. "Should I take some BTC profits?" is barely answerable in isolation. It depends on your overall allocation, your tax situation, your retirement-account capacity, your cash position, and any other risk concentrations.
OpenClaw with Truthifi makes the cross-account framing automatic. Ask the question and OpenClaw can pull your traditional brokerage allocation, your retirement accounts, your cash, and your crypto positions in one query. The answer it gives is contextualized against your whole financial life, not just your Coinbase tab.
That's the case for connecting more than just crypto. Each additional account you link in Truthifi makes every question in OpenClaw better. Crypto-only context produces crypto-only answers. Cross-account context produces actually useful answers.
For example: "Should I rebalance my crypto exposure?" In isolation, that's a generic question. With cross-account context, OpenClaw can answer something like "Your crypto holdings (BTC + ETH on Coinbase + Kraken) are now 9.3% of your total portfolio. Your stated target is 5%. To rebalance to target, you'd need to sell about $14,000 of crypto. Highest tax-efficient approach: harvest the $2,140 loss on your BABA position in your taxable brokerage first to offset crypto gains, then sell the BTC lots from Coinbase that have the highest cost basis." That's the kind of answer the trading-app dashboards can't give you because they don't see across accounts.
Multi-channel context adds another dimension. Sunday-night deep analysis on web; weekday balance ping from Telegram; family-coordination conversation in Discord — same OpenClaw, same data, no per-channel re-paste. The use cases compound on themselves once the data layer is in place.
What's next
A few directions OpenClaw plus Truthifi opens up that you might not have considered:
Recurring exposure checks. Set up a Discord channel where your OpenClaw bot reports your top concentration risks every Monday morning.
Tax-lot questions for harvesting. "Show me lots in my Coinbase and Kraken accounts I could sell for a loss without triggering wash-sale issues." Genuinely hard to do manually; trivially easy with structured data and an LLM.
Comparison across venues. "Is the same coin priced differently across my linked exchanges right now? Big enough to matter for my next purchase?" OpenClaw can answer because it sees both venues.
Self-custody integration. Watch a wallet address (not the keys — just the address) and OpenClaw can pull on-chain holdings as part of the same query.
Disconnecting
You can revoke access from either side at any time:
From Truthifi: truthifi.com → Settings → Connected Apps → OpenClaw → Revoke. The next OpenClaw call to Truthifi fails authentication.
From OpenClaw: remove the
truthifientry frommcpServers(Path B) or runmcporter uninstall truthifi(Path A). Restart the gateway.From the exchanges: revoke Truthifi's read access at Coinbase or Kraken in their respective security settings.
Each revocation is independent. Revoking at the exchange level cuts off Truthifi's ability to read that specific exchange. Revoking at OpenClaw cuts off OpenClaw's ability to call Truthifi. Revoking at Truthifi (in your Truthifi account) does both simultaneously for everything OpenClaw can see.
Why crypto portfolios need an analytical layer more than most
Crypto holdings are where the lack of cross-account intelligence hurts the most. Most retail investors hold their crypto across at least two venues — Coinbase for the convenience, Kraken or another exchange for the assets Coinbase doesn't list, and increasingly self-custody on top. Each venue gives you a portal that shows what you own there. None of them show you what you own across the whole picture.
That's the gap OpenClaw plus Truthifi closes. Your self-hosted OpenClaw becomes a single conversation surface that can see all of your crypto holdings, normalized into one view, alongside your traditional brokerage accounts if you've connected those too. Ask "what percentage of my total net worth is in BTC?" and OpenClaw can answer — pulling Coinbase, Kraken, and any traditional accounts in one query.
Crypto specifically benefits from this kind of analytical layer because volatility makes everything time-sensitive. The position size that was 4% of your portfolio last month is 7% today. The cost basis on the lots you're thinking about selling matters for tax purposes and changes constantly. Manually tracking this across multiple exchanges is exactly the work AI agents are good at — once they know what you own.
There's a second-order benefit specific to OpenClaw: privacy. Many crypto holders prefer not to send portfolio data to a SaaS aggregator dashboard, much less to a hosted LLM provider. Self-hosted OpenClaw with Truthifi keeps the conversational reasoning on infrastructure you own. Your AI agent answers "what's my BTC concentration?" without sending the answer to anyone outside your own host. For privacy-conscious users — which most serious crypto holders are — that's a meaningful design point.
A worked example. A crypto holder on the privacy-conscious end of the spectrum runs OpenClaw on a personal VPS, with Truthifi connected to read Coinbase and Kraken. Their workflow: Sunday-night analysis on the web channel ("review my crypto exposure relative to my non-crypto holdings, identify any tax-loss-harvesting candidates"), Tuesday Discord-based check-ins from their phone with a small group of other holders ("how am I tracking on the BTC concentration target we set?"), Wednesday Telegram quick balance ping while traveling. Same OpenClaw, same Truthifi, three channels, no third-party AI provider in any of those flows. The privacy posture that made them choose self-hosted in the first place is preserved end-to-end for the most-sensitive financial questions.
Multi-channel matters in crypto specifically because crypto news moves fast. You may be at a party when major BTC news breaks. Pull out your phone, ask the OpenClaw Telegram bot what's going on with your positions and what X is saying — get a real answer in seconds rather than having to open multiple apps to triangulate. The architecture optimizes for the way active crypto holders actually live.
The connection, explained
Truthifi connects to Coinbase and Kraken through their respective official APIs (read-only scopes). Truthifi normalizes the data into a consistent schema — the same schema it uses for traditional brokerages — and exposes it to OpenClaw via the Model Context Protocol.
OpenClaw, running on your own infrastructure, registers Truthifi as an MCP server. Once registered, every conversation across every OpenClaw channel can ask questions that draw on your Coinbase and Kraken positions in real time. The crypto data flows through the same pipeline as everything else — there's no special-casing for crypto in OpenClaw.
The OAuth handshake happens between you and Truthifi (and separately between Truthifi and each exchange when you initially link). OpenClaw never sees your exchange credentials. The token issued to OpenClaw is read-only and scoped to the tools OpenClaw needs.
What you need
A self-hosted OpenClaw instance you can configure (web shell, SSH, or local Node environment).
A Truthifi account with Coinbase and/or Kraken already linked. (New to Truthifi Connect?)
Either Node.js 20+ for the
mcporterskill path, or text-editor access to~/.openclaw/openclaw.jsonfor the direct-config path.
That's it. No exchange API keys to copy into OpenClaw. No browser automation. No DIY scraping of exchange portals.
Setup: five steps
Detailed walkthrough is in the full setup guide: How to Connect Your Portfolio to OpenClaw via Truthifi MCP. Condensed here:
Link Coinbase and Kraken to Truthifi. Sign in to truthifi.com → Connections → add each exchange. The OAuth flow happens once per exchange and never again.
Add Truthifi to OpenClaw. Either run
mcporter install --target openclaw truthifi(Path A) or add Truthifi to themcpServersblock of~/.openclaw/openclaw.jsonwithtype: "http"andurl: "https://api.truthifi.com/mcp"(Path B).Restart the OpenClaw gateway. Required after a config edit; not needed if you used
mcporter.Authenticate via OAuth on first call. Ask any crypto question in OpenClaw. The first call triggers an OAuth authorization in your browser. Sign in to Truthifi, grant the read-only scope, return to your OpenClaw session.
Verify. Try a prompt like "Show me my BTC and ETH balances across Coinbase and Kraken with current USD value." Real numbers should come back.
If your OpenClaw runs behind a reverse proxy, set MCP_ISSUER_URL to your public HTTPS URL — otherwise OAuth metadata advertises localhost and the redirect fails. Most reverse-proxy gotchas trace to this single setting.
The security model for crypto accounts specifically
The crypto question gets people more nervous than the traditional brokerage question, with good reason — exchange security is its own discipline. The architecture here is designed around that:
Read-only tokens at the exchange level. When you link Coinbase or Kraken to Truthifi, the OAuth scope you grant is read-only. There is no path through Truthifi's connector to a withdrawal endpoint. Even if Truthifi's connection were compromised at any point, withdrawals from your exchange account would still require the standard exchange-side authentication that OpenClaw and Truthifi don't have access to.
No exchange credentials on the OpenClaw host. Self-hosting is a specific concern here — you're running a Node.js process on a machine you control, and credentials on that machine are credentials at risk. Truthifi's design keeps your Coinbase and Kraken credentials at Coinbase and Kraken. The OpenClaw host only sees a Truthifi-scoped OAuth token.
Truthifi's exchange connections are managed centrally. When an exchange's API changes — and they change often — Truthifi handles the upgrade on its side. You don't need to update your OpenClaw config or rotate keys. The MCP contract OpenClaw sees stays stable while the underlying exchange integrations evolve.
Per-host audit trail. Every Truthifi tool call from OpenClaw is logged with the OpenClaw user identity and channel (web, Discord, Telegram). If something looks anomalous later, you can trace which channel asked what. Especially relevant for shared OpenClaw hosts in family or advisor settings.
Wallet-address tracking, no key exposure. If you also self-custody, Truthifi can read on-chain balances by watching wallet addresses you've registered. The wallet keys never leave your custody — Truthifi only reads what's publicly visible on-chain at the address. OpenClaw sees the same view, with self-custody balances integrated into the same query as your exchange holdings.
Hard limits: what OpenClaw cannot do with your crypto accounts
Spelled out unambiguously:
No trades. OpenClaw cannot place buy or sell orders on Coinbase, Kraken, or any other exchange.
No withdrawals. OpenClaw cannot move crypto off your exchange or to another wallet.
No deposits. OpenClaw cannot move funds in.
No exchange-account modifications. OpenClaw cannot change your security settings, add 2FA devices, change your linked email, or modify any exchange account property.
No Truthifi-account modifications. Adding or removing exchange links is something you do from truthifi.com, not from OpenClaw.
No off-platform sharing. OpenClaw doesn't ship your crypto data to any third party. Truthifi doesn't either.
No wallet-key exposure. Even for self-custody addresses, Truthifi reads addresses, never private keys.
The asymmetry is intentional: read everything, write nothing. It's the right shape for a self-hosted agent that talks to crypto exchanges.
Supported exchanges
Truthifi's MCP supports the major US-accessible exchanges where it's economically reasonable to maintain an integration:
Coinbase (including Coinbase Pro/Advanced)
Kraken
Gemini (via Truthifi's broader exchange roster)
Binance.US (where available)
Plus self-custody read-only via wallet-address tracking for Bitcoin, Ethereum, and major chains
The exchanges OpenClaw will actually see depend on what you've linked in Truthifi. If you have Coinbase and Kraken linked, those are what OpenClaw can query. Add a third exchange in Truthifi later, and OpenClaw picks it up automatically — no config change needed in OpenClaw.
The total-picture argument
The thing that makes the OpenClaw approach especially useful for crypto is that crypto questions almost always benefit from context. "Should I take some BTC profits?" is barely answerable in isolation. It depends on your overall allocation, your tax situation, your retirement-account capacity, your cash position, and any other risk concentrations.
OpenClaw with Truthifi makes the cross-account framing automatic. Ask the question and OpenClaw can pull your traditional brokerage allocation, your retirement accounts, your cash, and your crypto positions in one query. The answer it gives is contextualized against your whole financial life, not just your Coinbase tab.
That's the case for connecting more than just crypto. Each additional account you link in Truthifi makes every question in OpenClaw better. Crypto-only context produces crypto-only answers. Cross-account context produces actually useful answers.
For example: "Should I rebalance my crypto exposure?" In isolation, that's a generic question. With cross-account context, OpenClaw can answer something like "Your crypto holdings (BTC + ETH on Coinbase + Kraken) are now 9.3% of your total portfolio. Your stated target is 5%. To rebalance to target, you'd need to sell about $14,000 of crypto. Highest tax-efficient approach: harvest the $2,140 loss on your BABA position in your taxable brokerage first to offset crypto gains, then sell the BTC lots from Coinbase that have the highest cost basis." That's the kind of answer the trading-app dashboards can't give you because they don't see across accounts.
Multi-channel context adds another dimension. Sunday-night deep analysis on web; weekday balance ping from Telegram; family-coordination conversation in Discord — same OpenClaw, same data, no per-channel re-paste. The use cases compound on themselves once the data layer is in place.
What's next
A few directions OpenClaw plus Truthifi opens up that you might not have considered:
Recurring exposure checks. Set up a Discord channel where your OpenClaw bot reports your top concentration risks every Monday morning.
Tax-lot questions for harvesting. "Show me lots in my Coinbase and Kraken accounts I could sell for a loss without triggering wash-sale issues." Genuinely hard to do manually; trivially easy with structured data and an LLM.
Comparison across venues. "Is the same coin priced differently across my linked exchanges right now? Big enough to matter for my next purchase?" OpenClaw can answer because it sees both venues.
Self-custody integration. Watch a wallet address (not the keys — just the address) and OpenClaw can pull on-chain holdings as part of the same query.
Disconnecting
You can revoke access from either side at any time:
From Truthifi: truthifi.com → Settings → Connected Apps → OpenClaw → Revoke. The next OpenClaw call to Truthifi fails authentication.
From OpenClaw: remove the
truthifientry frommcpServers(Path B) or runmcporter uninstall truthifi(Path A). Restart the gateway.From the exchanges: revoke Truthifi's read access at Coinbase or Kraken in their respective security settings.
Each revocation is independent. Revoking at the exchange level cuts off Truthifi's ability to read that specific exchange. Revoking at OpenClaw cuts off OpenClaw's ability to call Truthifi. Revoking at Truthifi (in your Truthifi account) does both simultaneously for everything OpenClaw can see.
The smartest money move you can make? Hook it up to AI.
Truthifi® tests your finances for 100+ risks and opportunities—automatically. Unlock plain-English insights that drive smarter financial decisions today.
The smartest money move you can make? Hook it up to AI.
Truthifi® tests your finances for 100+ risks and opportunities—automatically. Unlock plain-English insights that drive smarter financial decisions today.
The smartest money move you can make? Hook it up to AI.
Truthifi® tests your finances for 100+ risks and opportunities—automatically.
Frequently asked questions
Does Truthifi support staked positions on Coinbase or Kraken? Yes. Staked balances appear in the same query as liquid balances. OpenClaw can distinguish between them when answering "show me my available BTC vs. my staked BTC."
What about NFTs? Truthifi's MCP focuses on fungible holdings (BTC, ETH, ERC-20, exchange-listed alts). NFTs are out of scope for the financial-data layer.
Will OpenClaw see my exchange API keys? No. The keys (or OAuth grants) live at Truthifi. OpenClaw only sees a Truthifi-scoped MCP token. If you uninstall Truthifi from OpenClaw, your exchange connections at Truthifi are unaffected.
Can I have OpenClaw alert me when my crypto allocation crosses a threshold? OpenClaw can answer the question whenever asked — "is BTC over 10% of my portfolio?" — but doesn't have a polling/alerting mode out of the box. If you want scheduled checks, you can wire that up via OpenClaw's task scheduling and a cron-style invocation. The MCP query itself is on-demand.
What if I move my OpenClaw to a different host? The mcpServers config block is portable — copy it. OAuth tokens are tied to host identity for security reasons, so you'll re-authenticate on first call from the new host. That's a deliberate design choice.
How does Truthifi handle the volatility of crypto data freshness? Most exchange connections refresh once per business day; Coinbase and Kraken specifically refresh more often through their APIs. Real-time pricing is a separate question — Truthifi quotes the most recent price the exchange API surfaced at last sync. For day-trading purposes you'd want exchange-native tools; for portfolio-level questions, near-real-time freshness is sufficient.
Can I scope crypto queries to specific OpenClaw channels? Yes — OpenClaw's channel-permission system lets you allow Truthifi-touching queries from web and Telegram only, blocking them from a public Discord channel for example. Useful if you have OpenClaw integrated into a server with mixed-permission users.
What is Truthifi?
Truthifi is a wealth-monitoring platform that connects to your real financial accounts — brokerages, banks, crypto exchanges, retirement accounts — and exposes the data via Model Context Protocol so AI assistants like OpenClaw, Claude, ChatGPT, Perplexity, Grok, and Mistral can read it. The MCP server is read-only by design. Your bank and exchange credentials stay at your bank and exchange. The whole thing is built around the principle that your AI should know what you actually own without becoming a credential store.
For OpenClaw users specifically: Truthifi is the data layer that makes self-hosted AI actually useful for personal finance. Every other piece of the stack (the agent, the host, the channels) you already control. Truthifi closes the gap on the data side.
Frequently asked questions
Does Truthifi support staked positions on Coinbase or Kraken? Yes. Staked balances appear in the same query as liquid balances. OpenClaw can distinguish between them when answering "show me my available BTC vs. my staked BTC."
What about NFTs? Truthifi's MCP focuses on fungible holdings (BTC, ETH, ERC-20, exchange-listed alts). NFTs are out of scope for the financial-data layer.
Will OpenClaw see my exchange API keys? No. The keys (or OAuth grants) live at Truthifi. OpenClaw only sees a Truthifi-scoped MCP token. If you uninstall Truthifi from OpenClaw, your exchange connections at Truthifi are unaffected.
Can I have OpenClaw alert me when my crypto allocation crosses a threshold? OpenClaw can answer the question whenever asked — "is BTC over 10% of my portfolio?" — but doesn't have a polling/alerting mode out of the box. If you want scheduled checks, you can wire that up via OpenClaw's task scheduling and a cron-style invocation. The MCP query itself is on-demand.
What if I move my OpenClaw to a different host? The mcpServers config block is portable — copy it. OAuth tokens are tied to host identity for security reasons, so you'll re-authenticate on first call from the new host. That's a deliberate design choice.
How does Truthifi handle the volatility of crypto data freshness? Most exchange connections refresh once per business day; Coinbase and Kraken specifically refresh more often through their APIs. Real-time pricing is a separate question — Truthifi quotes the most recent price the exchange API surfaced at last sync. For day-trading purposes you'd want exchange-native tools; for portfolio-level questions, near-real-time freshness is sufficient.
Can I scope crypto queries to specific OpenClaw channels? Yes — OpenClaw's channel-permission system lets you allow Truthifi-touching queries from web and Telegram only, blocking them from a public Discord channel for example. Useful if you have OpenClaw integrated into a server with mixed-permission users.
What is Truthifi?
Truthifi is a wealth-monitoring platform that connects to your real financial accounts — brokerages, banks, crypto exchanges, retirement accounts — and exposes the data via Model Context Protocol so AI assistants like OpenClaw, Claude, ChatGPT, Perplexity, Grok, and Mistral can read it. The MCP server is read-only by design. Your bank and exchange credentials stay at your bank and exchange. The whole thing is built around the principle that your AI should know what you actually own without becoming a credential store.
For OpenClaw users specifically: Truthifi is the data layer that makes self-hosted AI actually useful for personal finance. Every other piece of the stack (the agent, the host, the channels) you already control. Truthifi closes the gap on the data side.
Disclaimer: This article is for educational purposes only and does not constitute financial, tax, or legal advice. It should not be construed as a personalized recommendation regarding any investment, financial advisor, or financial product. All calculations use hypothetical scenarios and historical return assumptions; actual results will vary. Past performance does not guarantee future results. Consult a qualified financial professional for guidance specific to your situation. Truthifi is an investment monitoring platform — not a financial advisor, broker-dealer, or tax professional. Truthifi does not manage assets, recommend investments, sell financial products, or provide personalized financial advice. Truthifi earns no revenue from advisor referrals, product commissions, or AUM fees. Statistics and data cited reflect publicly available sources current as of the article's publication date. Sources are linked throughout.
Disclaimer: This article is for educational purposes only and does not constitute financial, tax, or legal advice. It should not be construed as a personalized recommendation regarding any investment, financial advisor, or financial product. All calculations use hypothetical scenarios and historical return assumptions; actual results will vary. Past performance does not guarantee future results. Consult a qualified financial professional for guidance specific to your situation. Truthifi is an investment monitoring platform — not a financial advisor, broker-dealer, or tax professional. Truthifi does not manage assets, recommend investments, sell financial products, or provide personalized financial advice. Truthifi earns no revenue from advisor referrals, product commissions, or AUM fees. Statistics and data cited reflect publicly available sources current as of the article's publication date. Sources are linked throughout.
Disclaimer: This article is for educational purposes only and does not constitute financial, tax, or legal advice. It should not be construed as a personalized recommendation regarding any investment, financial advisor, or financial product. All calculations use hypothetical scenarios and historical return assumptions; actual results will vary. Past performance does not guarantee future results. Consult a qualified financial professional for guidance specific to your situation. Truthifi is an investment monitoring platform — not a financial advisor, broker-dealer, or tax professional. Truthifi does not manage assets, recommend investments, sell financial products, or provide personalized financial advice. Truthifi earns no revenue from advisor referrals, product commissions, or AUM fees. Statistics and data cited reflect publicly available sources current as of the article's publication date. Sources are linked throughout.
Ready to get started?