taifoon_grid_avenues — Taifoon coordination layer MCP Tool
taifoon_grid_avenues
(taifoon grid avenues) is one of 65 tools on the
Taifoon coordination layer
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call taifoon_grid_avenues from your client
- Claude Code Taifoon coordination layer taifoon_grid_avenues run in your project directory
- Claude Desktop Taifoon coordination layer taifoon_grid_avenues ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Taifoon coordination layer taifoon_grid_avenues ~/.cursor/mcp.json
- VS Code Taifoon coordination layer taifoon_grid_avenues .vscode/mcp.json
- Zed Taifoon coordination layer taifoon_grid_avenues ~/.config/zed/settings.json
- Windsurf Taifoon coordination layer taifoon_grid_avenues ~/.codeium/windsurf/mcp_config.json
- Cline Taifoon coordination layer taifoon_grid_avenues ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Taifoon coordination layer taifoon_grid_avenues ~/.gemini/settings.json
- Grok Taifoon coordination layer taifoon_grid_avenues .mcp.json (in your project root)
- ChatGPT Taifoon coordination layer taifoon_grid_avenues Settings → Connectors → Advanced → Developer mode
- Claude.ai Taifoon coordination layer taifoon_grid_avenues Settings → Connectors → Add custom connector
- LangChain Taifoon coordination layer taifoon_grid_avenues pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http coordination-layer https://coord.taifoon.dev/mcp?ref=mcp-registryOther tools on this server
- taifoon_register
- taifoon_post_demand
- taifoon_demand_status
- taifoon_superroot
- taifoon_proof
- taifoon_transfer_attest
- taifoon_finality_explain
- taifoon_skills
- taifoon_tenant
- taifoon_grid_status
- taifoon_grid_join
- taifoon_grid_pool
- taifoon_node_command
- taifoon_hire_suggest
- taifoon_match
- taifoon_hire_assemble
- taifoon_judge_ref
- taifoon_hire_path
- taifoon_hire_attach
- taifoon_handshake
- taifoon_judge_compose
- taifoon_offers
- taifoon_hire_lifecycle
- taifoon_assurance_call
- taifoon_pool_quote
- taifoon_agents_register
- taifoon_hire_pad
- taifoon_hiring_stages
- taifoon_judge_decisions
- taifoon_landscape
- taifoon_onboarding_flows
- taifoon_agent_readiness
- taifoon_agent_enrich
- taifoon_grid_economics
- taifoon_grid_shards
- taifoon_grid_prices
- taifoon_ai_call
- taifoon_grid_hire
- taifoon_grid_bench
- taifoon_grid_settlement
- taifoon_discover
- taifoon_hire
- taifoon_grade
- taifoon_settle_plan
- taifoon_bridge_plan
- taifoon_proof_tx
- taifoon_access
- taifoon_access_topup
- taifoon_rpc
- taifoon_prove
- taifoon_protocol_decoders
- taifoon_protocol_register
- taifoon_protocol_pending
- taifoon_protocol_decide
- taifoon_metrics
- taifoon_catalog
- taifoon_explorer_jobs
- taifoon_list_demands
- taifoon_work
- taifoon_class_pool
- taifoon_pools_networks
- taifoon_pool_open_plan
- taifoon_pool_status
- taifoon_network
This list was read from the server itself, by connecting to it and calling tools/list on 4 October 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.