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