get_flare_prices — flarewatch MCP Tool Read-only
get_flare_prices
(get flare prices) is one of 27 tools on the
flarewatch
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_flare_prices from your client
- Claude Code flarewatch get_flare_prices run in your project directory
- Claude Desktop flarewatch get_flare_prices ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor flarewatch get_flare_prices ~/.cursor/mcp.json
- VS Code flarewatch get_flare_prices .vscode/mcp.json
- Zed flarewatch get_flare_prices ~/.config/zed/settings.json
- Windsurf flarewatch get_flare_prices ~/.codeium/windsurf/mcp_config.json
- Cline flarewatch get_flare_prices ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI flarewatch get_flare_prices ~/.gemini/settings.json
- Grok flarewatch get_flare_prices .mcp.json (in your project root)
- ChatGPT flarewatch get_flare_prices Settings → Connectors → Advanced → Developer mode
- Claude.ai flarewatch get_flare_prices Settings → Connectors → Add custom connector
- LangChain flarewatch get_flare_prices pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http flarewatch https://mcp.flarewatch.io/api/mcp
Other tools on this server
- get_flare_validators
- get_validator_score
- get_ftso_providers
- get_ftso_provider_metrics
- get_network_status
- get_flarewatch_validator
- get_flarewatch_sgb_entity
- get_recent_agent_actions
- get_agent_capabilities
- get_agent_status
- get_network_economics
- get_fassets_status
- get_defi_tvl
- get_chain_activity
- get_ftso_provider_history
- list_ftso_feeds
- get_payment_options
- simulate_delegation_rewards
- compare_validators
- compare_ftso_providers
- verify_response
- get_my_delegations
- get_my_claimable
- get_my_portfolio_summary
- get_my_tax_records
- get_my_rewards_history
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.