Sec Edgar MCP

🚀 SEC EDGAR MCP Project Documentation

The SEC EDGAR MCP project offers an interface that enables AI models to access the U.S. Securities and Exchange Commission (SEC)'s EDGAR database via the Model Context Protocol (MCP). EDGAR is the SEC's electronic system for corporate filings, containing regulatory filings of public companies, such as 10-K, 8-K, and other important financial reports.

Through the MCP protocol, AI models can invoke a series of tools to query and analyze the SEC's public data, thereby automating the acquisition and processing of information about public companies' financial status, governance structure, etc.

🚀 Quick Start

The SEC EDGAR MCP project provides an interface for AI models to access the SEC's EDGAR database through the MCP protocol. This allows for automated retrieval and analysis of public companies' regulatory filings.

✨ Features

• Access to EDGAR Database: Enables AI models to access the SEC's EDGAR database via MCP.
• Automated Data Retrieval: Facilitates the automated acquisition and processing of company financial information.
• Multiple Query Tools: Offers a set of tools for querying and analyzing SEC public data.

🔧 Technical Details

Available Tools

1. Get Submissions (get_submissions)

• Function: Retrieves all SEC submissions of a specified company (by CIK or Ticker).
• Parameters:
  • cik: The company's Central Index Key (optional; if not provided, ticker is required).
  • ticker: The company's stock ticker (optional; if not provided, cik is required).
• Returns: A list of metadata for all filings submitted by the company, including the following fields:
  • accessionNumber: The unique identifier of the submission.
  • formType: The type of the submitted form (e.g., 10-K, 8-K).
  • actionDate: The submission date.
  • filedAt: The actual filing time of the document.
  • description: A brief description of the form.
• Example Request:

{
  "jsonrpc": "2.0",
  "method": "get_submissions",
  "params": {
    "cik": "0001369748"
  },
  "id": 1
}

• Example Response:

{
  "result": [
    {
      "accessionNumber": "0001369748-23-00001",
      "formType": "10-K",
      "actionDate": "2023-12-31",
      "filedAt": "2024-01-01T12:00:00Z",
      "description": "Annual report for the year ended December 31, 2023"
    },
    // More records...
  ]
}

2. Get Filing (get_filing)

• Function: Returns the full content of a specified submission.
• Parameters:
  • accessionNumber: The unique identifier of the submission.
• Returns: The JSON-formatted content of the submission, including the following fields:
  • infoTable: The basic information table.
  • formData: The form data.
  • XBRLData: The eXtensible Business Reporting Language (XBRL) data (if applicable).
• Example Request:

{
  "jsonrpc": "2.0",
  "method": "get_filing",
  "params": {
    "accessionNumber": "0001369748-23-00001"
  },
  "id": 1
}

• Example Response:

{
  "result": {
    "infoTable": {
      "Company Name": "Example Corp",
      "CIK": "0001369748",
      "Form Type": "10-K"
    },
    "formData": {
      // Form data content...
    }
  }
}

3. Get XBRL (get_xbrl)

• Function: Returns the XBRL (eXtensible Business Reporting Language) data in a specified submission.
• Parameters:
  • accessionNumber: The unique identifier of the submission.
• Returns: The financial data in XBRL format, including key indicators such as revenue, profit, and liabilities.
• Example Request:

{
  "jsonrpc": "2.0",
  "method": "get_xbrl",
  "params": {
    "accessionNumber": "0001369748-23-00001"
  },
  "id": 1
}

• Example Response:

{
  "result": {
    "FinancialStatements": {
      "Revenue": 1000000,
      "NetIncome": 500000,
      "TotalLiabilities": 2000000
    }
  }
}

🚧 Important Notes

⚠️ Important Note

• All tool invocations require a valid CIK or Ticker.
• Please carefully read the SEC's official documentation and the requirements of the MCP protocol before making any invocations.
• Due to limitations of the SEC database, some historical data may not be accessible.

🗺️ Architecture

The project architecture is as follows:

1. MCP Client: Responsible for receiving and processing requests from AI models and forwarding them to the server.
2. MCP Server: Responsible for parsing requests, invoking the corresponding EDGAR API, and returning the results to the client.
3. EDGAR REST API: A public interface provided by the SEC for querying and obtaining filings data.

The entire process is as follows:

AI model -> MCP Client -> MCP Server -> EDGAR REST API -> Return results

📚 References

1. SEC Official Website (Official Website, 2024)
2. MCP Protocol Documentation
3. EDGAR API Documentation

📄 License

This project is open-source under the MIT License, allowing users to freely use, modify, and distribute it. Please refer to the LICENSE file for the full license content.