filingexplorer-mcp

A Model Context Protocol server for the FilingExplorer API. It gives an MCP client (Claude Desktop, Claude Code, or any other MCP host) direct tools for public SEC filing data: company profiles and filing lists, reported financials, verbatim filing text, Form 13-F institutional holdings, Form 4 insider trades, ETF holdings, and your own watchlists.

0.x: tool names, parameters and outputs may change between minor versions.

The server runs locally on your machine and calls the FilingExplorer API with your own API token. There is no hosted endpoint.

Requirements

• Python 3.10 or newer, or uv
• A FilingExplorer API token. API keys are free: sign up, then create a key at filingexplorer.com/api-keys. See filingexplorer.com/developers for plan limits.

Free and paid plans

A free account can create an API key and use every tool in this server. The free plan has a small monthly request allowance (currently 100 requests a month, with short burst limits), which is enough to try the server over a few conversations. One MCP conversation usually makes several API calls, so heavier use needs a paid plan. A few options also need a paid plan: see the notes under Tools.

When the allowance runs out, tools return a rate-limit error that says when you can retry.

Install and run

uvx filingexplorer-mcp

or install it into an environment and run the script:

pip install filingexplorer-mcp
filingexplorer-mcp

The server speaks MCP over stdio, so it is normally started by your MCP client rather than by hand.

Configuration

All data, including filing documents, is fetched through the FilingExplorer API. The server makes no direct requests to sec.gov.

Claude Desktop

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "filingexplorer": {
      "command": "uvx",
      "args": ["filingexplorer-mcp"],
      "env": { "FILING_EXPLORER_API_TOKEN": "your-token" }
    }
  }
}

Claude Code

claude mcp add filingexplorer --env FILING_EXPLORER_API_TOKEN=your-token -- uvx filingexplorer-mcp

Tools

Notes:

• Verbatim text only. The document and section tools return text exactly as filed.
• ETF coverage is incomplete. Some ETFs have no holdings data. The tool says so when that happens; an empty result means the data is not available, not that the fund holds nothing.
• Watchlist tools act only on your own account. The API scopes every list request to the owner of the token.
• Some requests (same-day or full-history filing lists, older 13-F history, longer insider-cluster windows) need a paid FilingExplorer plan. These return a clear error on other plans.

Output format

Tools return compact, YAML-like text: empty fields are omitted, and lists include a hint such as call again with offset=50 for more when more results exist. Long texts come in windows of max_chars characters with the next offset stated in a header line.

Errors come back as tool errors with the HTTP status and the API's message, for example Not found (404): Company not found or Rate limited by the FilingExplorer API (429). Retry after 30 seconds.

Development

uv sync
uv run ruff check .
uv run pytest

See CONTRIBUTING.md for the commit hooks and the publication check.

The contract tests use hand-written fixtures and no network. A live smoke test runs only when FILING_EXPLORER_API_TOKEN is set:

FILING_EXPLORER_API_TOKEN=your-token uv run pytest -m live

License

Apache License 2.0. See LICENSE and NOTICE.