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