check_health — kr crypto intelligence MCP Tool Read-only
check_health
(check health) is one of 18 tools on the
kr crypto intelligence
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call check_health from your client
- Claude Code kr crypto intelligence check_health run in your project directory
- Claude Desktop kr crypto intelligence check_health ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor kr crypto intelligence check_health ~/.cursor/mcp.json
- VS Code kr crypto intelligence check_health .vscode/mcp.json
- Zed kr crypto intelligence check_health ~/.config/zed/settings.json
- Windsurf kr crypto intelligence check_health ~/.codeium/windsurf/mcp_config.json
- Cline kr crypto intelligence check_health ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI kr crypto intelligence check_health ~/.gemini/settings.json
- Grok kr crypto intelligence check_health .mcp.json (in your project root)
- ChatGPT kr crypto intelligence check_health Settings → Connectors → Advanced → Developer mode
- Claude.ai kr crypto intelligence check_health Settings → Connectors → Add custom connector
- LangChain kr crypto intelligence check_health pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http kr-crypto-intelligence https://mcp.printmoneylab.com/mcpOther tools on this server
- get_kimchi_premium
- get_kr_prices
- get_fx_rate
- get_available_symbols
- get_stablecoin_premium
- get_arbitrage_scanner
- get_exchange_alerts
- get_market_movers
- get_market_read
- get_kr_sentiment
- get_krw_macro_stress
- get_global_vs_korea_divergence
- get_global_vs_korea_divergence_deep
- get_kr_news_kpop
- get_kr_news_kpop_summary
- get_kr_news_semiconductor
- get_kr_news_semiconductor_summary
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.