Ext Ops Panel
Open dashboard
Comparison

EdgarParser MCP vs SEC Intelligence

EdgarParser MCP is an MCP server published by henrysouchien. Marketplaces we read that list it: 1 (Official MCP Registry). SEC Intelligence is an MCP server published by jahanv01. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-07. 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
MarketplaceEdgarParser MCPSEC Intelligence
Official MCP Registry Listed
Version: 1.0.2
Downloads/month (PyPI): 1 094
Downloads/week (PyPI): 47
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.1.1
Downloads/month (PyPI): 377
Downloads/week (PyPI): 21
Forks (GitHub): 0
Stars (GitHub): 1
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

EdgarParser MCP vs SEC Intelligence
FactEdgarParser MCPSEC Intelligence
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)1 (better)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)On your machine (edgar-mcp)On your machine (sec-intelligence-mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)3, secrets among them: 18, secrets among them: 3
LicenceNot statedNot stated
Repository (differs)github.com/henrysouchien/edgar-mcpgithub.com/jahanv01/sec-intelligence-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11

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

EdgarParser MCP

In its own words, on Official MCP Registry:

MCP stdio server for source-backed SEC EDGAR financial data from the hosted EdgarParser API.

SEC Intelligence

In its own words, on Official MCP Registry:

SEC 10-K/10-Q/8-K search, RAG Q&A, comparison, and anomaly detection with citations.

How to run each

EdgarParser MCP As a local MCP server: PyPI package

Claude Code
claude mcp add --env "EDGAR_API_KEY=<YOUR_EDGAR_API_KEY>" --transport stdio edgar-mcp -- uvx edgar-mcp

Requires: EDGAR_API_KEY (secret)

SEC Intelligence As a local MCP server: PyPI package

Claude Code
claude mcp add --env "GEMINI_API_KEY=<YOUR_GEMINI_API_KEY>" --env "LANGFUSE_PUBLIC_KEY=<YOUR_LANGFUSE_PUBLIC_KEY>" --env "LANGFUSE_SECRET_KEY=<YOUR_LANGFUSE_SECRET_KEY>" --env "QDRANT_API_KEY=<YOUR_QDRANT_API_KEY>" --env "QDRANT_URL=<YOUR_QDRANT_URL>" --transport stdio sec-intelligence-mcp -- uvx sec-intelligence-mcp

Requires: GEMINI_API_KEY (secret), LANGFUSE_PUBLIC_KEY, LANGFUSE_SECRET_KEY (secret), QDRANT_API_KEY (secret), QDRANT_URL

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

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Only EdgarParser MCP asks for

  • EDGAR_API_KEY (secret)
  • EDGAR_API_URL
  • EDGAR_MCP_OUTPUT_DIR

Only SEC Intelligence asks for

  • EMBEDDING_MODEL
  • GEMINI_API_KEY (secret)
  • GEMINI_MODEL
  • LANGFUSE_PUBLIC_KEY
  • LANGFUSE_SECRET_KEY (secret)
  • QDRANT_API_KEY (secret)
  • QDRANT_URL
  • SEC_EDGAR_USER_AGENT

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

What it can do: EdgarParser MCP · What it can do: SEC Intelligence · 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.

Where the data comes from: how the catalog is built