About this integration
SEC 10-K/10-Q/8-K search, RAG Q&A, comparison, and anomaly detection with citations.
- Transport
- stdio
- Authentication
- api-key
- Initial setup
- credentials
- Runtime
- unattended
- Evidence
- documented
- Version
- 0.1.1
- Package
- sec-intelligence-mcp
- Last compatibility test
- Not independently tested
Connect your agent
sec-intelligence-mcpThe publisher documents persistent services that restart without manual intervention. The stdio package still requires several third-party credentials and local or hosted Qdrant, and networked demo deployment lacks production TLS until the operator adds a proxy. Documentation was reviewed; no filing, model, vector store or API was contacted.
Capabilities: Ingest and search SEC filing text, Generate cited filing analysis and summaries, Compare companies and detect disclosure anomalies
Connected profiles
Additional details
io.github.jahanv01/sec-intelligence-mcp
Source ↗ · Checked 2026-09-170.1.1
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17pypi
Source ↗ · Checked 2026-09-17GEMINI_API_KEY, QDRANT_URL, LANGFUSE_SECRET_KEY, LANGFUSE_PUBLIC_KEY
Source ↗ · Checked 2026-09-17sec-intelligence-mcp
Source ↗ · Checked 2026-09-190.1.1
Source ↗ · Checked 2026-09-19The documented persistent deployment uses restart policies so the server and Qdrant return after VM reboot without manual intervention.
Source ↗ · Checked 2026-09-19Gemini and LangFuse API keys are required, Qdrant needs a URL and may need its own API key, while SEC EDGAR itself uses no API key.
Source ↗ · Checked 2026-09-19Launch uvx sec-intelligence-mcp over stdio with the documented Gemini, Qdrant and LangFuse environment configuration.
Source ↗ · Checked 2026-09-19Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-19