SEC EDGAR data vs FinzData market data
SEC EDGAR data is an MCP server published by Bosco-Labs. Marketplaces we read that list it: 1 (Official MCP Registry). FinzData market data is an MCP server published by FinzData. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-11-10. 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 |  SEC EDGAR data |  FinzData market data |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 1.0.0 Downloads/month (PyPI): 0 Downloads/week (PyPI): 125 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| PyPI (MCP servers) | Not listed | Listed Version: 0.1.5 Downloads/month (PyPI): 0 Downloads/week (PyPI): 258 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 | SEC EDGAR data | FinzData market data |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | 2026-11-09 (better) | 2026-11-06 (worse) |
| Where it runs (differs) | Remote server (api.boscolabs.dev/mcp) | Remote server or your machine |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/bosco-labs/bosco-labs-data | github.com/finzdata/finzdata-mcp |
| Changes in the last 7 days (differs) | 4 | 3 |
| First seen (differs) | 2026-11-08 | 2026-10-12 |
| Endpoint at the last check (differs) | not checked yet | Status out of date: last check 31 h ago returned HTTP 401 |
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
SEC EDGAR data
SEC EDGAR filings, Form 4 insider trades, 13F holdings and XBRL financials, with filing links
FinzData market data
US stocks incl. delisted, futures, CPI/macro vintages, point-in-time GEX, 13F, COT, backtests.
How to run each
SEC EDGAR data
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Requires: Authorization header
FinzData market data As a remote MCP server
claude mcp add --transport http finzdata-mcp https://api.finzdata.com/mcp --header "X-API-Key: <YOUR_X_API_KEY>"Requires: X-API-Key header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only FinzData market data 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
Neither one's marketplaces publish the settings it asks for.
What it can do: SEC EDGAR data · What it can do: FinzData market data · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.