SEC EDGAR MCP

Created By
stefanoamorellia year ago
A SEC EDGAR Model Context Protocol (MCP) Server
Overview

What is SEC EDGAR MCP?

SEC EDGAR MCP is an open-source Model Context Protocol (MCP) server that connects AI models to the SEC EDGAR filings dataset, providing access to corporate financial information submitted to the U.S. SEC.

How to use SEC EDGAR MCP?

To use SEC EDGAR MCP, run the server and connect it with any MCP-compatible client (like an AI assistant). The client can then invoke tools to retrieve real-time data from SEC filings.

Key features of SEC EDGAR MCP?

  • Access to millions of SEC filings for financial research.
  • Integration with AI models for real-time data retrieval.
  • Tools for fetching company submissions, financial concepts, and facts.

Use cases of SEC EDGAR MCP?

  1. AI assistants retrieving the latest filings for companies.
  2. Financial analysts querying specific financial metrics.
  3. Researchers accessing historical corporate data for analysis.

FAQ from SEC EDGAR MCP?

  • Can SEC EDGAR MCP be used for all companies?

Yes! It provides access to filings for all companies registered with the SEC.

  • Is SEC EDGAR MCP free to use?

Yes! It is an open-source project and free for everyone.

  • What programming language is used?

The server is implemented in Python.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
stefanoamorelli
Star
32
Language
Python
License
MIT license

Recommend Servers

View All
Payai X402 Tools

6 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago