ChainFolioAI
REMOTE · CHAINFOLIOAI.COM
Read-only crypto and traditional portfolio: holdings, PNL, FIFO tax figures and market data.
Available components
Last scanned (20 hours ago)
Scores higher than 98% of remote servers
Reachable. Last reached 22 Nov 2026.
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security91
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1456 tokens (~63/item across 23 items; 23 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 23 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 23 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 13 Nov 26 +1
- Stability: 0.97 → pass security
- 11 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +60
- Authorization: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.63 ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Nov 2026 · Probed https://chainfolioai.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=chainfolioai.com | CN=YR2,O=Let's Encrypt,C=US | 29 Sept 2026 | 28 Dec 2026 | RSA 2048 | SHA256-RSA | 5b18b1da2b24f4596a9b4c73c3b327db2fa |
| SANs: chainfolioai.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of chainfolioai.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| chainfolioai.com. | DS published | 2371 | 13 | Verified |
| chainfolioai.com. | Verified address RRset verified with the apex keys |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer error="invalid_token", error_description="No authorization provided", resource_metadata="https://chainfolioai.com/.well-known/oauth-protected-resource"
Bearer error="invalid_token", error_description="No authorization provided", resource_metadata="https://chainfolioai.com/.well-known/oauth-protected-resource" | Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'wasm-unsafe-eval' https://js.stripe.com https://s3.tradingview.com https://accounts.google.com https://challenges.cloudflare.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https:; font-src 'self' data:; connect-src 'self' https://accounts.google.com https://*.supabase.co https://*.supabase.io wss://*.supabase.co https://api.coingecko.com https://deep-index.moralis.io https://programs.shyft.to https://dlmm-api.meteora.ag https://blockfrost.io https://cardano-mainnet.blockfrost.io https://api.alternative.me https://api.blockchair.com https://mempool.space https://blockchain.info https://api.bitaps.com https://xchain.io https://api.ordinals.com https://open-api.unisat.io https://api.mainnet-beta.solana.com https://solana.publicnode.com https://solana-rpc.publicnode.com https://blockstream.info https://rpc.ankr.com https://cloudflare-eth.com https://ethereum.publicnode.com https://walletconnect.org https://*.walletconnect.org wss://*.wallet |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(self), usb=() |
Protected resource metadata
| Document | https://chainfolioai.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Problem | Metadata incomplete |
| Resource | https://chainfolioai.com/api/mcp |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://chainfolioai.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://chainfolioai.com/api/mcp | HTTPS enforced | 308 | https://chainfolioai.com/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
ask_ai ~63
Ask the AI assistant, in natural language, about your real portfolio (analysis, context, risks). It never gives buy or sell orders. Daily limit per account.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | The question about the portfolio or the market (max. 1000 characters). |
No output schema declared.
No examples provided.
get_asset ~53
Price, market cap, volume and change (24h/7d) of a crypto asset by symbol (e.g. btc, eth, sol).
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | yes | Asset symbol, e.g. btc |
No output schema declared.
No examples provided.
get_btc_blocks ~31
Recent Bitcoin blocks (height, number of transactions, median fee, pool) and recommended mempool fees.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_defi_positions ~72
The user's lending positions read from the contracts (Aave V3, Spark, Compound V3, Morpho, EigenLayer) on Ethereum, Arbitrum, Base, Optimism and Polygon: supplied, borrowed and net, with health factor. It queries the blockchain, so it takes a few seconds.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_derivatives ~72
Derivatives data for a symbol on OKX: open interest, long/short ratio, funding, CVD, taker volume, 1 h candles, put/call and a composite sentiment score (0–100).
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | – | Symbol, e.g. BTC (default) or ETH. |
No output schema declared.
No examples provided.
get_fear_greed ~31
Crypto market Fear & Greed index (current value 0–100, classification and recent history).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_fire ~112
Calculates the years to financial independence (4% rule) from expenses, savings, return and age.
| Name | Type | Req | Description |
|---|---|---|---|
| annualReturn | number | – | Expected annual return in % (default 7) |
| currentAge | integer | – | Current age (default 30) |
| currentPortfolio | number | – | Current net worth (default 0) |
| inflation | number | – | Annual inflation in % (default 3) |
| monthlyExpenses | number | yes | Monthly expenses |
| monthlyInvestment | number | yes | Monthly savings/investment |
No output schema declared.
No examples provided.
get_global_market ~28
Global crypto market state: total market cap, 24 h change and Bitcoin and Ethereum dominance.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_market ~53
Returns the top crypto assets by market cap (price, market cap, volume, 24h and 7d change).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many assets to return (1–250, default 50). |
No output schema declared.
No examples provided.
get_metrics ~46
Advanced portfolio metrics from the saved history: ROI, CAGR, Sharpe, Sortino, Calmar, volatility, maximum and current drawdown, win rate and 95% VaR.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_news ~42
Latest crypto news (CoinDesk, CoinTelegraph): title, source, link and date.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many news items (default 15) |
No output schema declared.
No examples provided.
get_nfts ~44
NFTs in the user's EVM wallets on one network. They are not included in the portfolio total (no reliable price).
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | Network (default eth). |
No output schema declared.
No examples provided.
get_pnl ~42
The user's portfolio performance in euros: current total and change over 24 h, 7 days, 30 days and since the start, from the saved snapshots.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_portfolio ~39
Returns the user's latest portfolio snapshot: balances per network (ETH, SOL, BTC, ADA), exchanges (CEX), DeFi and manual assets.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_portfolio_score ~53
The user's portfolio score (0–100), as shown in the app: diversification, crypto/traditional mix, stablecoin reserve, performance and risk management. A reading aid, not a recommendation to buy or sell.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_price_on ~67
Closing price in US dollars of a crypto asset on a date (UTC), from OKX daily candles. Useful to value a past buy or sale.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Data em AAAA-MM-DD (UTC). |
| symbol | string | yes | Symbol, e.g. BTC. |
No output schema declared.
No examples provided.
get_realized_gains ~61
The user's realised capital gains using FIFO, in euros, with fees and gas deducted: total, per asset and per year. Not a tax return.
| Name | Type | Req | Description |
|---|---|---|---|
| year | integer | – | Calendar year of the sales (optional; without it everything is returned). |
No output schema declared.
No examples provided.
get_tax_estimate ~308
ESTIMATE of capital-gains tax in a country, in that country's currency: the country's cost method (FIFO, average cost, LIFO, UK pooling, annual sum), each trade converted at the ECB rate of its date, the rules of the year of sale, holding period, annual allowance and, where the law allows, losses carried from previous years. Not a tax return. Each country's options are in list_tax_countries (options field).
| Name | Type | Req | Description |
|---|---|---|---|
| alternative | boolean | – | BR, PT, AR and AT only: the alternative option for where the coins are held (BR foreign exchange; PT broker outside the EU/EEA with no tax treaty; AR sale in pesos; AT Austrian platform). |
| country | string | yes | Two-letter country code (e.g. PT, ES, US). See list_tax_countries. |
| marginalRate | number | – | Only where the rate depends on income (DE, GB, US, CA, AU, LU, MX): the person's marginal rate as a fraction (0.35 = 35%). Without it the top rate is used. |
| marginalRateLong | number | – | US only: the person's long-term rate as a fraction (0, 0.15 or 0.20, plus 0.038 NIIT if applicable). |
| year | integer | – | Tax year of the sales (optional). In the UK and Australia it is the year the tax year starts (2025 = 2025/26). |
No output schema declared.
No examples provided.
get_trades ~78
Transactions recorded by the user (buys, sells and fees), in euros, newest first. Optional filters by asset and year.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | – | Asset symbol (e.g. BTC). |
| limit | integer | – | Maximum number of transactions to return (default 100). |
| year | integer | – | Calendar year of the transaction. |
No output schema declared.
No examples provided.
get_wallets ~29
Returns the wallets of each portfolio, with addresses as pseudonyms (wallet_…), never in clear.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_whale_activity ~50
Scans the given addresses and returns recent on-chain movements (large transfers, accumulation). Supports ETH, BTC and SOL.
| Name | Type | Req | Description |
|---|---|---|---|
| watchlist | array | yes | Addresses to watch (max. 10). |
No output schema declared.
No examples provided.
list_known_whales ~43
Lists the preloaded known whales (exchanges, funds, public figures, governments) with address and chain. Use the addresses as input to get_whale_activity.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_tax_countries ~39
Crypto tax regimes published by ChainFolioAI: short- and long-term rate, holding period, annual allowance and legal reference, per country.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the ChainFolioAI MCP server?
ChainFolioAI is a hosted endpoint at https://chainfolioai.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · chainfolioai.com
claude mcp add --transport http com-chainfolioai-chainfolioai 'https://chainfolioai.com/api/mcp'
What is the ChainFolioAI MCP server?
ChainFolioAI is an MCP server listed in the public MCP registry as com.chainfolioai/chainfolioai. Read-only crypto and traditional portfolio: holdings, PNL, FIFO tax figures and market data. This page covers its hosted endpoint (https://chainfolioai.com/api/mcp).
Is the ChainFolioAI MCP server safe to use?
ChainFolioAI scores 92 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the ChainFolioAI MCP server expose?
ChainFolioAI exposes 23 tools: get_portfolio, get_wallets, get_pnl, get_realized_gains, get_metrics, and 18 more. Their descriptions and schemas cost roughly 1,456 tokens of context every time the server is loaded.
Does the ChainFolioAI MCP server require authentication?
Yes. ChainFolioAI asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the ChainFolioAI MCP server still maintained?
ChainFolioAI is still listed as active in the MCP registry. We last reached this channel on 22 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the ChainFolioAI MCP server?
VerifyMCP ran 13 checks on ChainFolioAI, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.