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