audit_status — 72hours security check MCP Tool
audit_status
(audit status) is one of 15 tools on the
72hours security check
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call audit_status from your client
- Claude Code 72hours security check audit_status run in your project directory
- Claude Desktop 72hours security check audit_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor 72hours security check audit_status ~/.cursor/mcp.json
- VS Code 72hours security check audit_status .vscode/mcp.json
- Zed 72hours security check audit_status ~/.config/zed/settings.json
- Windsurf 72hours security check audit_status ~/.codeium/windsurf/mcp_config.json
- Cline 72hours security check audit_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI 72hours security check audit_status ~/.gemini/settings.json
- Grok 72hours security check audit_status .mcp.json (in your project root)
- ChatGPT 72hours security check audit_status Settings → Connectors → Advanced → Developer mode
- Claude.ai 72hours security check audit_status Settings → Connectors → Add custom connector
- LangChain 72hours security check audit_status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http 72hours https://oboe-handiness-enroll.ngrok-free.dev/mcp/service/rpcOther 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.