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