chain_status — keyfo MCP Tool

chain_status (chain status) is one of 23 tools on the keyfo MCP server. Connect the server and your client discovers it on the handshake.

by client

How to call chain_status from your client

Claude Code keyfo chain_status run in your project directory
Claude Desktop keyfo chain_status ~/Library/Application Support/Claude/claude_desktop_config.json
Cursor keyfo chain_status ~/.cursor/mcp.json
VS Code keyfo chain_status .vscode/mcp.json
Zed keyfo chain_status ~/.config/zed/settings.json
Windsurf keyfo chain_status ~/.codeium/windsurf/mcp_config.json
Cline keyfo chain_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
Gemini CLI keyfo chain_status ~/.gemini/settings.json
Grok keyfo chain_status .mcp.json (in your project root)
ChatGPT keyfo chain_status Settings → Connectors → Advanced → Developer mode
Claude.ai keyfo chain_status Settings → Connectors → Add custom connector
LangChain keyfo chain_status pip install langchain-mcp-adapters

Fastest route

claude mcp add --transport http keyfo https://keyfo.xyz/mcp

Other tools on this server

stock_quote
stock_movers
stock_portfolio
build_trade
fund_agent
my_key
morpho_rates
morpho_loop
build_morpho_deposit
list_models
model_detail
ask_model
stock_approvals
build_revoke
explain_tx
schedule_buy
list_schedules
cancel_schedule
pending_signs
buy_at_price
portfolio_pnl
portfolio_brief

This list was read from the server itself, by connecting to it and calling tools/list on 11 November 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.

keyfo MCP server