SecFeed: SEC EDGAR filings vs parsec-edgar: SEC EDGAR filings
SecFeed: SEC EDGAR filings is an MCP server published by secfeedapi.com. Marketplaces we read that list it: 1 (Official MCP Registry). parsec-edgar: SEC EDGAR filings is an MCP server published by ciscoriordan. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-13. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  parsec-edgar: SEC EDGAR filings | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 No figure published Not marked · First seen |
Listed Version: 0.2.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | SecFeed: SEC EDGAR filings | parsec-edgar: SEC EDGAR filings |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 0 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release (differs) | Not published | 2026-11-12 |
| Where it runs (differs) | Remote server (secfeedapi.com/mcp) | On your machine (parsec-edgar) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 0 |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/ciscoriordan/parsec-edgar |
| Changes in the last 7 days (differs) | 0 | 5 |
| First seen (differs) | 2026-10-17 | 2026-11-09 |
| Endpoint at the last check (differs) | Responded less than an hour ago | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
SecFeed: SEC EDGAR filings
SEC EDGAR data as tools: filing search, full text, XBRL financials, insider trades, 13F, 8-K events.
parsec-edgar: SEC EDGAR filings
Search SEC EDGAR, list company filings, and read 10-K, 10-Q and 8-K filings one Item at a time
How to run each
SecFeed: SEC EDGAR filings As a remote MCP server
claude mcp add --transport http secfeed https://secfeedapi.com/mcp --header "Authorization: Bearer <YOUR_API_KEY>"Requires: Authorization header
parsec-edgar: SEC EDGAR filings As a local MCP server: PyPI package
claude mcp add --env "PARSEC_EDGAR_USER_AGENT=<YOUR_PARSEC_EDGAR_USER_AGENT>" --transport stdio parsec-edgar -- uvx parsec-edgar mcpRequires: PARSEC_EDGAR_USER_AGENT
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only SecFeed: SEC EDGAR filings has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of SecFeed: SEC EDGAR filings publish no settings it asks for, so we do not compare settings.
What it can do: SecFeed: SEC EDGAR filings · What it can do: parsec-edgar: SEC EDGAR filings · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.