Skip to content
MCPSTAMP
MCP server report

ChainFolioAI MCP server

com.chainfolioai/chainfolioai

We checked this server on 2 November 2026 with McpStamp Check engine 1.2.0. It scored 68 of 100 (grade C), higher than 9.3% of the 33,003 registry servers that responded over HTTPS that day. Ready for MCP Registry. Not ready for Claude, ChatGPT and Gemini.

Measured facts

Score
68C
Sign-in
OAuth
Tools listed
23
Protocol version
2025-11-25
Stores

Store readiness

StoreStatusReason
Claude Connectors Directory Not ready Blocked by Protected resource metadata (RFC 9728), Authorization server metadata (RFC 8414 / OIDC), readOnlyHint or destructiveHint on every tool and Human-readable title on every tool.
ChatGPT app directory Not ready Blocked by Protected resource metadata (RFC 9728), Authorization server metadata (RFC 8414 / OIDC), readOnlyHint or destructiveHint on every tool, Explicit readOnlyHint, destructiveHint and openWorldHint (ChatGPT) and Human-readable title on every tool.
Gemini Connected Apps Not ready Blocked by Authorization server metadata (RFC 8414 / OIDC) and First metadata URL Gemini tries answers 200 with the required fields.
Official MCP Registry Ready No blocking check failed.

MCP Registry ready means a valid public remote for the registry, not that the server is listed in a store.

Fixes

8 checks to fix

  1. Fails

    readOnlyHint or destructiveHint on every tool

    tool_annotations

    Blocks Claude and ChatGPT.

    Measured 23/23 tools set neither readOnlyHint nor destructiveHint: get_portfolio, get_wallets, get_pnl, get_realized_gains, get_metrics and 18 more

    Set annotations.readOnlyHint: true on read-only tools and destructiveHint: true on tools that modify or delete data (Claude needs one of them on every tool; ChatGPT needs all three hints, see tool_open_world).

  2. Fails

    Protected resource metadata (RFC 9728)

    auth_prm

    Blocks Claude and ChatGPT.

    Measured https://chainfolioai.com/.well-known/oauth-protected-resource has no authorization_servers

    List your issuer URL in "authorization_servers" in the protected resource metadata.

  3. Fails

    Authorization server metadata (RFC 8414 / OIDC)

    auth_as_metadata

    Blocks Claude, ChatGPT and Gemini.

    Measured Not found: https://chainfolioai.com/.well-known/oauth-authorization-server -> 404; https://chainfolioai.com/.well-known/openid-configuration -> 404

    Serve RFC 8414 metadata at <issuer>/.well-known/oauth-authorization-server with authorization_endpoint, token_endpoint and response_types_supported ["code"].

  4. Fails

    Explicit readOnlyHint, destructiveHint and openWorldHint (ChatGPT)

    tool_open_world

    Blocks ChatGPT.

    Measured 23/23 tools miss an explicit hint: get_portfolio, get_wallets, get_pnl, get_realized_gains, get_metrics and 18 more

    Set readOnlyHint, destructiveHint and openWorldHint to explicit true/false on every tool (OpenAI app review requires all three).

  5. Fails

    Human-readable title on every tool

    tool_titles

    Blocks Claude and ChatGPT.

    Measured 23/23 without title: get_portfolio, get_wallets, get_pnl, get_realized_gains, get_metrics and 18 more

    Add a short human-readable "title" to every tool (shown in store UIs and consent screens).

  6. Fails

    First metadata URL Gemini tries answers 200 with the required fields

    auth_gemini_discovery

    Blocks Gemini.

    Measured Gemini tries https://chainfolioai.com/.well-known/oauth-authorization-server first and gets HTTP 404; it uses that answer and does not try other locations

    Make https://chainfolioai.com/.well-known/oauth-authorization-server answer HTTP 200 with the authorization server metadata (authorization_endpoint, token_endpoint, response_types_supported ["code"], registration_endpoint). Gemini tries htt

  7. Fails

    Server instructions

    instructions

    Measured No instructions in the initialize result

    Add an "instructions" string to the initialize result: what the server covers, for whom, and its limits.

  8. Warning

    JSON-RPC error for unknown method

    jsonrpc_errors

    Measured HTTP 401 instead of a JSON-RPC error

    Route the method first and answer unknown methods with JSON-RPC error -32601 before the auth check, or return a JSON-RPC error body with the 401.

15 checks passed, 4 did not run

Passed. Served over HTTPS, initialize over Streamable HTTP, Supported protocol version negotiated, JSON or SSE response Content-Type, GET answers SSE or 405, initialize latency, serverInfo name and version, tools capability declared, Sign-in method the store supports (OAuth or none), 401 carries WWW-Authenticate resource_metadata, Resource metadata "resource" equals the server URL, tools/list returns tools, inputSchema is an object schema, Tool names are valid and portable, Tool descriptions.

Not run. issuer equals the authorization_servers entry; token_endpoint_auth_methods_supported (ChatGPT), PKCE S256 advertised, Client registration (DCR or Client ID Metadata Documents), refresh_token grant advertised. These need an OAuth sign-in flow the check could not reach.

Run a fresh check

This page is the 2 November 2026 snapshot. If you maintain this server and have shipped fixes since then, re-check it. The live check and the badge show the current result, and the next snapshot will pick up the change.

Re-check now

Badge

README badge

The badge shows the latest score for this URL and links to this report.

McpStamp score for ChainFolioAI

Markdown

[![McpStamp score](https://www.mcpstamp.com/badge?url=https%3A%2F%2Fchainfolioai.com%2Fapi%2Fmcp)](https://www.mcpstamp.com/r/com-chainfolioai-chainfolioai/)

HTML

<a href="https://www.mcpstamp.com/r/com-chainfolioai-chainfolioai/"><img src="https://www.mcpstamp.com/badge?url=https%3A%2F%2Fchainfolioai.com%2Fapi%2Fmcp" alt="McpStamp score" height="20"></a>
Registry entry

About this server

Read-only crypto and traditional portfolio: holdings, PNL, FIFO tax figures and market data.
Registry name
com.chainfolioai/chainfolioai
Remote URL
https://chainfolioai.com/api/mcp
Version
1.0.0
Website
chainfolioai.com/developers
Checked
2 November 2026, engine 1.2.0, no credentials

The description above is the server's own text from the official MCP Registry. If a result looks wrong, run a fresh check and email support@zovo.one with the report link.

More grade C servers

All grade C servers · All server reports · State of MCP readiness, November 2026