check_env_exposure — VibeScale MCP Tool Read-only
check_env_exposure
(check env exposure) is one of 3 tools on the
VibeScale
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call check_env_exposure from your client
- Claude Code VibeScale check_env_exposure run in your project directory
- Claude Desktop VibeScale check_env_exposure ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor VibeScale check_env_exposure ~/.cursor/mcp.json
- VS Code VibeScale check_env_exposure .vscode/mcp.json
- Zed VibeScale check_env_exposure ~/.config/zed/settings.json
- Windsurf VibeScale check_env_exposure ~/.codeium/windsurf/mcp_config.json
- Cline VibeScale check_env_exposure ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI VibeScale check_env_exposure ~/.gemini/settings.json
- Grok VibeScale check_env_exposure .mcp.json (in your project root)
- ChatGPT VibeScale check_env_exposure Settings → Connectors → Advanced → Developer mode
- Claude.ai VibeScale check_env_exposure Settings → Connectors → Add custom connector
- LangChain VibeScale check_env_exposure pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http vibescale https://vibe.elya-studio.com/mcpOther tools on this server
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.