Ext Ops Panel
Open dashboard
Comparison

Needle vs parsec-edgar: SEC EDGAR filings

Needle is an MCP server published by needle-ai. Marketplaces we read that list it: 2 (Docker MCP Catalog, 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

Where each is published
MarketplaceNeedleparsec-edgar: SEC EDGAR filings
Docker MCP Catalog Listed
Version: sha256:d3fd314f40c3
Forks (GitHub): 24
Pulls (Docker Hub): 12 202
Stars (Docker Hub): 1
Stars (GitHub): 105
Not marked · First seen
Not listed
Official MCP Registry Listed
Version: 1.0.1
Forks (GitHub): 24
Stars (GitHub): 105
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

Needle vs parsec-edgar: SEC EDGAR filings
FactNeedleparsec-edgar: SEC EDGAR filings
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)105 (better)0 (worse)
Pulls (Docker Hub) (differs)12 202No figure on Docker Hub
Forks (GitHub) (differs)24 (better)0 (worse)
Last release (differs)2026-11-06 (worse)2026-11-12 (better)
Where it runs (differs)Remote server or your machineOn your machine (parsec-edgar)
Transport (differs)stdio, Streamable HTTPstdio
Tools it declares (differs)7Not published
Environment variables it asks for (differs)1, secrets among them: 11, secrets among them: 0
LicenceNot statedNot stated
Repository (differs)github.com/needle-ai/needle-mcpgithub.com/ciscoriordan/parsec-edgar
Changes in the last 7 days (differs)05
First seen (differs)2026-10-112026-11-09
Endpoint at the last check (differs)Responded 5 h ago, requires authenticationno 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

Needle

In its own words, on Docker MCP Catalog:

Production-ready RAG service to search and retrieve data from your documents.

parsec-edgar: SEC EDGAR filings

In its own words, on Official MCP Registry:

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

Needle As a local MCP server: Docker image

Claude Code
claude mcp add --env "NEEDLE_API_KEY=<YOUR_NEEDLE_API_KEY>" --transport stdio needle-mcp -- docker run -i --rm -e NEEDLE_API_KEY mcp/needle-mcp

Requires: NEEDLE_API_KEY (secret)

parsec-edgar: SEC EDGAR filings As a local MCP server: PyPI package

Claude Code
claude mcp add --env "PARSEC_EDGAR_USER_AGENT=<YOUR_PARSEC_EDGAR_USER_AGENT>" --transport stdio parsec-edgar -- uvx parsec-edgar mcp

Requires: PARSEC_EDGAR_USER_AGENT

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Needle has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of parsec-edgar: SEC EDGAR filings publish no list of tools, so we do not compare tools.

Settings each asks for

Only Needle asks for

  • NEEDLE_API_KEY (secret)

Only parsec-edgar: SEC EDGAR filings asks for

  • PARSEC_EDGAR_USER_AGENT

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Needle · What it can do: parsec-edgar: SEC EDGAR filings · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.

Where the data comes from: how the catalog is built