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