Skip to main content
mcpSource-backed

edgartools SEC MCP Server

Local MCP server for the edgartools Python library, letting Claude search, parse, read, compare, and analyze SEC EDGAR filings, companies, ownership, funds, proxy statements, notes, trends, and live filing feeds.

by Dwight Gunning · submitted by oktofeesh1·added 2026-06-06·
Review first review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Source URLs
https://github.com/dgunning/edgartools/blob/main/docs/ai/mcp-setup.md, https://github.com/dgunning/edgartools
Brand
edgartools
Brand domain
github.com
Safety notes
edgartools MCP can query live SEC filings, parse structured filing data, search filing text, monitor recent filings, compare companies, inspect ownership, and extract proxy or fund information., SEC EDGAR access requires an identity string and can be rate-limited if automated requests are too frequent or unidentified., Filing analysis can produce plausible financial, legal, governance, compensation, or risk conclusions that still require expert review., The local server is stateless, but remote HTTP transport deployments still need normal network access controls if shared with a team., Do not treat model-generated summaries as investment advice, legal advice, accounting advice, or a substitute for reading the filing source.
Privacy notes
Tool inputs can reveal watchlists, portfolio interests, deal research, diligence targets, litigation topics, trading hypotheses, or compliance questions., Tool outputs can expose filing excerpts, insider transactions, institutional holdings, compensation data, financial metrics, and query strategy in the MCP client transcript., EDGAR_IDENTITY includes a name and email address; keep it scoped to approved automation and avoid committing it to source control., If using hosted edgar.tools services instead of the local server, review the hosted service's tier, retention, processing, and data-use terms separately.
Author
Dwight Gunning
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-06

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

63

Baseline

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Needs review

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done
  • Source provenance statusRequired

    Marked as source-backed.

    Done
  • Metadata reviewed

    No reviewed flag detected in metadata.

    Pending

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done
  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done
  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done
  • Package verification flag

    No package verification flag provided.

    Pending
  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending
  • Baseline comparison available

    No baseline peer selected yet.

    Pending
  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

CLI install

Copy-ready — paste the snippet to get started.

10 minutes

Adoption plan

Balanced adoption plan

Current risk score 24/100. Use staged verification before broader rollout.

Risk 24

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done
  • Confirm metadata review state

    No review metadata found; increase manual validation.

    Pending
  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done
  • Review privacy notesRequired

    Privacy notes are present.

    Done
  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending
  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending
  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Missing required evidence: Metadata review. Risk score 31.

Risk 31

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Missing

Review metadata is missing.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required gaps: Metadata review

Decision timeline

Decision timeline · balanced

Blocking gaps: Check metadata review status. Risk 28.

Risk 28

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is missing.

Pending

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

Blockers: Check metadata review status

Prerequisite readiness

Prerequisite readiness

5 prerequisites to line up before setup. Have accounts and credentials ready first.

0/5 ready
Account & credentials1Install & runtime1Network & hosting1General210 minutes

Safety & privacy surface

Safety & privacy surface

5 safety and 4 privacy notes across 4 risk areas. Review closely: permissions & scopes, network access.

4 areas
  • SafetyGeneraledgartools MCP can query live SEC filings, parse structured filing data, search filing text, monitor recent filings, compare companies, inspect ownership, and extract proxy or fund information.
  • SafetyNetwork accessSEC EDGAR access requires an identity string and can be rate-limited if automated requests are too frequent or unidentified.
  • SafetyGeneralFiling analysis can produce plausible financial, legal, governance, compensation, or risk conclusions that still require expert review.
  • SafetyPermissions & scopesThe local server is stateless, but remote HTTP transport deployments still need normal network access controls if shared with a team.
  • SafetyGeneralDo not treat model-generated summaries as investment advice, legal advice, accounting advice, or a substitute for reading the filing source.
  • PrivacyGeneralTool inputs can reveal watchlists, portfolio interests, deal research, diligence targets, litigation topics, trading hypotheses, or compliance questions.
  • PrivacyExecution & processesTool outputs can expose filing excerpts, insider transactions, institutional holdings, compensation data, financial metrics, and query strategy in the MCP client transcript.
  • PrivacyPermissions & scopesEDGAR_IDENTITY includes a name and email address; keep it scoped to approved automation and avoid committing it to source control.
  • PrivacyExecution & processesIf using hosted edgar.tools services instead of the local server, review the hosted service's tier, retention, processing, and data-use terms separately.

Safety notes

  • edgartools MCP can query live SEC filings, parse structured filing data, search filing text, monitor recent filings, compare companies, inspect ownership, and extract proxy or fund information.
  • SEC EDGAR access requires an identity string and can be rate-limited if automated requests are too frequent or unidentified.
  • Filing analysis can produce plausible financial, legal, governance, compensation, or risk conclusions that still require expert review.
  • The local server is stateless, but remote HTTP transport deployments still need normal network access controls if shared with a team.
  • Do not treat model-generated summaries as investment advice, legal advice, accounting advice, or a substitute for reading the filing source.

Privacy notes

  • Tool inputs can reveal watchlists, portfolio interests, deal research, diligence targets, litigation topics, trading hypotheses, or compliance questions.
  • Tool outputs can expose filing excerpts, insider transactions, institutional holdings, compensation data, financial metrics, and query strategy in the MCP client transcript.
  • EDGAR_IDENTITY includes a name and email address; keep it scoped to approved automation and avoid committing it to source control.
  • If using hosted edgar.tools services instead of the local server, review the hosted service's tier, retention, processing, and data-use terms separately.

Prerequisites

  • Python 3.10 or newer and `uvx` available, or the `edgartools[ai]` package installed.
  • EDGAR_IDENTITY set to the name and email required for automated SEC EDGAR access.
  • Network access to SEC EDGAR endpoints and patience for rate limits or transient filing fetch failures.
  • Understanding of the filing forms, companies, sections, and time periods being analyzed.
  • Human review before using SEC filing analysis for investment, legal, accounting, compliance, or disclosure decisions.

Schema details

Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
10 minutes
Difficulty
intermediate
Full copyable content
{
  "mcpServers": {
    "edgartools": {
      "command": "uvx",
      "args": ["--from", "edgartools[ai]", "edgartools-mcp"],
      "env": {
        "EDGAR_IDENTITY": "Your Name your.email@example.com"
      }
    }
  }
}

About this resource

Content

edgartools SEC MCP Server connects Claude to the edgartools Python library for local SEC EDGAR research. It can retrieve company profiles, search filing metadata and full text, monitor recent filings, parse specific filings, read sections, inspect notes, analyze financial trends, compare companies, review ownership, look at fund holdings, and examine proxy compensation or governance data.

The local MCP server is installed through the edgartools[ai] extra and runs with stdio by default. The setup docs also describe Streamable HTTP transport for shared deployments and distinguish the local open-source server from the hosted edgar.tools MCP service.

Source Review

These sources were reviewed on 2026-06-06. Prefer the live repository, MCP setup guide, PyPI page, MCP tools reference, package metadata, and license for current install commands, tool names, SEC identity requirements, and transport options.

Features

  • Local stdio MCP server through uvx --from "edgartools[ai]" edgartools-mcp.
  • EDGAR_IDENTITY configuration for SEC automated access identification.
  • 13 documented tools organized around SEC research intent.
  • Company profile, financial, filing, and ownership lookup through edgar_company.
  • Company and filing search through edgar_search.
  • Company screening by industry, exchange, state, or SIC through edgar_screen.
  • Full-text filing search through edgar_text_search.
  • Recent filing monitoring through edgar_monitor.
  • Structured filing parsing and section extraction through edgar_filing and edgar_read.
  • Notes, trends, company comparison, ownership, fund, and proxy tools.
  • Optional Streamable HTTP transport for shared deployments.

Installation

For Claude Code:

claude mcp add edgartools -- uvx --from "edgartools[ai]" edgartools-mcp

Set the SEC identity required for automated EDGAR access:

export EDGAR_IDENTITY="Your Name your.email@example.com"

For MCP clients that use JSON configuration:

{
  "mcpServers": {
    "edgartools": {
      "command": "uvx",
      "args": ["--from", "edgartools[ai]", "edgartools-mcp"],
      "env": {
        "EDGAR_IDENTITY": "Your Name your.email@example.com"
      }
    }
  }
}

Restart the MCP client after adding the server.

Use Cases

  • Ask Claude to summarize a company's latest 10-K, 10-Q, or 8-K with filing identifiers.
  • Search recent filings for cybersecurity, AI, restructuring, revenue recognition, or risk-factor language.
  • Pull a specific filing section such as MD&A, risk factors, financials, controls, legal proceedings, or proxy compensation.
  • Compare financial trends across companies or periods using XBRL-sourced data.
  • Monitor recent SEC filings for a form type, company, or event-driven research workflow.
  • Inspect insider transactions, institutional holdings, fund data, or proxy governance details.

Safety and Privacy

SEC filings are public, but research intent is not. Treat prompts and tool calls as sensitive if they reveal portfolio targets, diligence questions, legal theories, competitive monitoring, or trading hypotheses. Keep EDGAR_IDENTITY out of committed files and use an approved automation identity.

Do not let a model's filing summary become the final decision. Verify citations, accession numbers, section text, filing dates, and financial figures against the source filing before using results for investment, legal, accounting, compliance, governance, or public reporting work.

Duplicate Check

Existing financial MCP entries cover hosted financial datasets, standardized market data, or curated provider databases such as Financial Datasets, Drillr, and Daloopa. This entry covers the separate local MIT-licensed edgartools Python library and MCP server for SEC EDGAR filings. No dgunning/edgartools, edgartools-mcp, or dedicated edgartools SEC MCP entry was found in content/mcp, content/tools, content/guides, content/agents, or content/skills.

Source citations

Add this badge to your README

Show that edgartools SEC MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/edgartools-sec-mcp-server.svg)](https://heyclau.de/entry/mcp/edgartools-sec-mcp-server)

How it compares

edgartools SEC MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

3 trust signals differ across this comparison (Package trust, Source provenance, Submitter).

Field

Local MCP server for the edgartools Python library, letting Claude search, parse, read, compare, and analyze SEC EDGAR filings, companies, ownership, funds, proxy statements, notes, trends, and live filing feeds.

Open dossier

Access high-quality fundamental financial data from SEC filings and investor presentations

Open dossier

Streamable HTTP MCP server for financial research workflows, including standardized financial data, SEC filing search, company discovery, market signals, ticker resolution, and alternative-data table exploration.

Open dossier

Remote MCP server over US SEC EDGAR filings — parsed 8-K (with body-text detection of suspected misclassifications under Item 8.01), Schedule 13D/G with activist filer tagging, and S-3 / 424B5 ATM-offering detection.

Open dossier
Next steps
Trust
Review statusNot reviewedNot reviewedNot reviewedNot reviewed
Package trustDiffersPackage not verifiedPackage verifiedPackage not verifiedPackage not verified
Source provenanceDiffersSource-backedNo submission linkSource-backedSource-backed
SubmitterDiffersoktofeesh1oktofeesh1jaablon
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
BrandDaloopa logoDaloopaDrillr logoDrillrFilingFirehose logoFilingFirehose
Categorymcpmcpmcpmcp
SourceSource-backedFirst-partySource-backedSource-backed
AuthorDwight GunningDaloopaDrillrFilingFirehose
Added2026-06-062025-09-182026-06-052026-06-27
Platforms
Harness
Source repo
Safety notesedgartools MCP can query live SEC filings, parse structured filing data, search filing text, monitor recent filings, compare companies, inspect ownership, and extract proxy or fund information. SEC EDGAR access requires an identity string and can be rate-limited if automated requests are too frequent or unidentified. Filing analysis can produce plausible financial, legal, governance, compensation, or risk conclusions that still require expert review. The local server is stateless, but remote HTTP transport deployments still need normal network access controls if shared with a team. Do not treat model-generated summaries as investment advice, legal advice, accounting advice, or a substitute for reading the filing source.Treat financial data as informational research and verify figures before using them for investment, accounting, or reporting decisions.Drillr's MCP endpoint is a remote Streamable HTTP server at `https://gateway.drillr.ai/mcp/data` and requires a bearer API key. Tool calls can consume Drillr credits or billable API usage. Check plan limits and remaining credit balance before high-volume research loops. run_sql is documented as read-only SELECT access, but broad queries across 90-plus tables can still be expensive, slow, or noisy. Treat outputs as research inputs, not investment, legal, accounting, tax, or trading advice. Drillr documents that it does not place trades, manage brokerage positions, expose options chains, or provide its own price forecasts. Review cited SEC filing paragraphs, table schemas, ticker resolution, and source coverage before relying on results in reports or decisions.Read-only — the server exposes no write tools.
Privacy notesTool inputs can reveal watchlists, portfolio interests, deal research, diligence targets, litigation topics, trading hypotheses, or compliance questions. Tool outputs can expose filing excerpts, insider transactions, institutional holdings, compensation data, financial metrics, and query strategy in the MCP client transcript. EDGAR_IDENTITY includes a name and email address; keep it scoped to approved automation and avoid committing it to source control. If using hosted edgar.tools services instead of the local server, review the hosted service's tier, retention, processing, and data-use terms separately.Company queries, filing references, financial models, and research topics may be sent through the MCP client and model.Prompts, ticker lists, research themes, SQL queries, and retrieved financial context are sent to Drillr's hosted gateway and the connected MCP client. Drillr API keys are sensitive credentials. Keep them out of prompts, shared configs, issue comments, logs, screenshots, and repository files. Research prompts may reveal portfolio interests, watchlists, investment theses, client names, diligence topics, or confidential strategy. SEC filing excerpts, analyst consensus, alt-data, market signals, and generated summaries may be retained by MCP clients, AI providers, logs, or downstream tools. Use synthetic prompts or public tickers for demos, screenshots, and examples when client, portfolio, or internal research strategy is sensitive.Queries and responses pass through the FilingFirehose backend; standard request logs apply.
Prerequisites
  • Python 3.10 or newer and `uvx` available, or the `edgartools[ai]` package installed.
  • EDGAR_IDENTITY set to the name and email required for automated SEC EDGAR access.
  • Network access to SEC EDGAR endpoints and patience for rate limits or transient filing fetch failures.
  • Understanding of the filing forms, companies, sections, and time periods being analyzed.
  • Daloopa account with active subscription
  • Daloopa API key (obtained from Daloopa sales team - contact sales@daloopa.com)
  • Internet connection for accessing Daloopa MCP server (https://mcp.daloopa.com/server/mcp)
  • Claude Desktop 0.7.0+ or Claude Code with MCP support
  • Drillr account at `https://drillr.ai`.
  • External-scope Drillr API key from `https://drillr.ai/developer/keys`.
  • MCP client that supports Streamable HTTP servers with bearer headers.
  • Secure secret storage for `DRILLR_API_KEY` outside prompts, repository files, screenshots, and shell history.
  • MCP client with streamable HTTP transport support (Claude Desktop, Claude Code, Cursor, etc.)
  • No account required for the free public tier (last 72 hours of filings).
  • Optional API key for full archive access — set via Authorization header.
Install
claude mcp add edgartools -- uvx --from "edgartools[ai]" edgartools-mcp
claude mcp list && claude mcp status daloopa
claude mcp add drillr https://gateway.drillr.ai/mcp/data --transport http --header "Authorization: Bearer $DRILLR_API_KEY"
claude mcp add --transport http filingfirehose https://filingfirehose.com/mcp
Config
{
  "mcpServers": {
    "edgartools": {
      "command": "uvx",
      "args": ["--from", "edgartools[ai]", "edgartools-mcp"],
      "env": {
        "EDGAR_IDENTITY": "Your Name your.email@example.com"
      }
    }
  }
}
{
  "mcpServers": {
    "daloopa": {
      "url": "https://mcp.daloopa.com/server/mcp",
      "type": "http"
    }
  }
}
{
  "mcpServers": {
    "drillr": {
      "type": "http",
      "url": "https://gateway.drillr.ai/mcp/data",
      "headers": {
        "Authorization": "Bearer ${DRILLR_API_KEY}"
      }
    }
  }
}
{
  "mcpServers": {
    "filingfirehose": {
      "url": "https://filingfirehose.com/mcp",
      "type": "http"
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.