market_state — Agentic Finance Graph MCP Tool
market_state
(market state) is one of 29 tools on the
Agentic Finance Graph
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call market_state from your client
- Claude Code Agentic Finance Graph market_state run in your project directory
- Claude Desktop Agentic Finance Graph market_state ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Agentic Finance Graph market_state ~/.cursor/mcp.json
- VS Code Agentic Finance Graph market_state .vscode/mcp.json
- Zed Agentic Finance Graph market_state ~/.config/zed/settings.json
- Windsurf Agentic Finance Graph market_state ~/.codeium/windsurf/mcp_config.json
- Cline Agentic Finance Graph market_state ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Agentic Finance Graph market_state ~/.gemini/settings.json
- Grok Agentic Finance Graph market_state .mcp.json (in your project root)
- ChatGPT Agentic Finance Graph market_state Settings → Connectors → Advanced → Developer mode
- Claude.ai Agentic Finance Graph market_state Settings → Connectors → Add custom connector
- LangChain Agentic Finance Graph market_state pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http agentic-finance-graph https://agenticfinancegraph.com/mcpOther tools on this server
- find_agent
- agent_record
- ranked_agents
- detections
- definition
- metric_history
- since_last
- counterparty_preview
- agent_statement
- evidence_pack_quote
- pay_check
- payer_set
- agent_stability
- agent_independence
- ladder_dynamics
- verify_sum_log
- self_check
- agent_pattern
- payee_facts
- gate_check
- agent_pass
- fleet_check
- payer_check
- agent_books
- blast_radius
- canary_register
- canary_status
- list_metrics
This list was read from the server itself, by connecting to it and calling tools/list on 14 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.