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