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