edgar-sec-mcp

Created By
flothjla year ago
An MCP Server to get data from EDGAR
Overview

what is edgar-sec-mcp?

edgar-sec-mcp is an MCP (Modular Computing Platform) server designed to facilitate AI agents in accessing and interacting with EDGAR Data from the SEC. It provides tools and endpoints for retrieving and analyzing SEC filings.

how to use edgar-sec-mcp?

To use edgar-sec-mcp, configure it with the provided settings and utilize the available tools to access specific SEC data, such as proxy statements and Form 4 filings.

key features of edgar-sec-mcp?

  • Access to SEC filings through a modular computing platform.
  • Tools for retrieving proxy statements and Form 4 data by ticker.
  • Streamlined data processing utilities for analysis.

use cases of edgar-sec-mcp?

  1. Analyzing executive compensation through proxy statements.
  2. Understanding insider trading activities via Form 4 filings.
  3. Facilitating AI-driven analysis of SEC data for research purposes.

FAQ from edgar-sec-mcp?

  • What types of SEC data can I access with edgar-sec-mcp?

You can access various SEC filings, including proxy statements and Form 4 filings.

  • Is edgar-sec-mcp easy to set up?

Yes! The configuration is straightforward, and detailed instructions are provided in the documentation.

  • Can I use edgar-sec-mcp for real-time data retrieval?

Yes, it is designed to facilitate real-time access to SEC data.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
flothjl
Star
0
Language
Python
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago