SEC EDGAR MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sec-edgarC | Unified tool for SEC EDGAR (Electronic Data Gathering, Analysis, and Retrieval) operations: access company filings, financial statements, and XBRL data from the U.S. Securities and Exchange Commission. Provides comprehensive access to public company disclosures, financial metrics, and regulatory filings using the official SEC EDGAR API. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools, as there are no other tools to compare it to. The single tool's purpose is clearly defined and distinct by default.
Since there is only one tool, naming consistency is inherently perfect; there are no other tool names to compare it against, so no inconsistencies can exist. The tool name 'sec-edgar' is clear and follows a straightforward pattern.
A single tool for SEC EDGAR operations feels thin and under-scoped, as the domain involves complex tasks like accessing filings, financial statements, and XBRL data. This likely forces multiple functionalities into one tool, which could be confusing and limit agent effectiveness, making it borderline too few for the apparent scope.
The tool description suggests a broad range of operations (e.g., access filings, financial statements, XBRL data), but with only one tool, there are significant gaps in the surface. It lacks distinct operations for different tasks like searching, retrieving specific filings, or handling XBRL data separately, which will likely cause agent failures due to incomplete coverage.