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