SEC EDGAR Financial Data

io.github.Taru0208Published by GitHub account Taru0208v1.1.0Updated Oct 24, 2026

Search SEC EDGAR filings, financial statements, and company data.

The publisher's own server: edgar.tools SEC Intelligence

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

Remote MCP server that lets an assistant search SEC EDGAR filings, financial statements and company data.

What you can do
  • Search SEC EDGAR filings and company data
  • Look up financial statements reported in filings
  • No tool list is published, so exact operations are not documented; the server is described only as covering filings, financial statements and company data.
When to use it
Useful when you need US public-company regulatory filings or reported financial figures inside an assistant session, for example to look up a company's filings or statements without leaving the chat.
Requirements
A remote streamable HTTP endpoint hosted on Apify; no local package or environment variables. OAuth authentication is required, so an account and authorization flow are needed, plus network access.
Before you install
Access requires OAuth sign-in, so the server receives your account authorization. It is a third-party hosted endpoint that queries SEC data on your behalf; review the provider's terms and data handling before connecting. No tool list is published, so what it can do beyond searching filings and company data is unverified.

Installation

In SourceWeft

  1. Open SEC EDGAR Financial Data in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.Taru0208%2Fsec-edgar-mcp-server/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "sec-edgar-financial-data": {
      "type": "http",
      "url": "https://aligned-kettledrum--sec-edgar-mcp-server.apify.actor/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.1.0LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Edgar integrations