check_state_availability — CoHostBnB MCP Tool Read-only
check_state_availability
(check state availability) is one of 2 tools on the
CoHostBnB
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call check_state_availability from your client
- Claude Code CoHostBnB check_state_availability run in your project directory
- Claude Desktop CoHostBnB check_state_availability ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor CoHostBnB check_state_availability ~/.cursor/mcp.json
- VS Code CoHostBnB check_state_availability .vscode/mcp.json
- Zed CoHostBnB check_state_availability ~/.config/zed/settings.json
- Windsurf CoHostBnB check_state_availability ~/.codeium/windsurf/mcp_config.json
- Cline CoHostBnB check_state_availability ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI CoHostBnB check_state_availability ~/.gemini/settings.json
- Grok CoHostBnB check_state_availability .mcp.json (in your project root)
- ChatGPT CoHostBnB check_state_availability Settings → Connectors → Advanced → Developer mode
- Claude.ai CoHostBnB check_state_availability Settings → Connectors → Add custom connector
- LangChain CoHostBnB check_state_availability pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http cohostbnb https://cohostbnb.xyz/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 10 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.