auditflag

Search SEC EDGAR for going-concern auditor opinions in real 10-K/10-Q filings.

Should I use this

Quality & Safety

A
Description quality
100%
Schema completeness
90%
Naming quality
100%
Poisoning risk
100%
Permission match
100%
Protocol compliance
100%

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~161Tokens (tool definitions)
~762 BTypical response size
Minimal attention impact (0.13% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "auditflag": {
      "url": "https://auditflag-lac.vercel.app/api/mcp"
    }
  }
}

Remote endpoints

https://auditflag-lac.vercel.app/api/mcpstreamable-http

What it can do

Tool inventory

Tools (1)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢check_going_concern_filings(days, company)

Search SEC EDGAR's real full-text search index for 10-K/10-Q/NT filings where a company's auditor included 'going concern' language -- the standard opinion auditors file when they have substantial doubt a company can survive the next 12 months. Returns real, dated filings straight from EDGAR, not a guess. Optionally filter to filings mentioning a specific company name.

Input Schema

{
  "type": "object",
  "properties": {
    "days": {
      "type": "integer",
      "description": "How many days back to search, 1-90 (default 30)."
    },
    "company": {
      "type": "string",
      "description": "Optional company name substring to filter results to (case-insensitive)."
    }
  },
  "required": []
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded1 tools
verifiedversion not recorded1 tools