# com.data-apis.api/sec-event-intelligence

Data APIs SEC Event Intelligence API for SEC API/EDGAR filings, OpenAPI, MCP, A2A at data-apis.com.

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the content rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 0.1.10
- **Author:** com.data-apis.api
- **License:** Unknown
- **Endpoints:** streamable-http https://api.data-apis.com/mcp
- **Source:** https://api.data-apis.com/mcp
- **Endpoint health:** degraded (last checked 2026-09-29T01:54:14.057Z, 5 samples) — uptime is not a security property and is not part of the trust score
- **Compatible clients:** claude-code, cursor, copilot, chatgpt, gemini (basis: transport)

## Trust

60/100 (B), scored on the content rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: clean
- Obfuscation scan: clean
- Evidence age: 27 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-09T05:17:43.887Z
- **Version scanned:** live
- **CVEs:** no coverage — this entry has no package coordinates to query OSV against, so "no known CVEs" is NOT asserted for it.

## Tools

11 declared. Observed from a live `tools/list` probe.
- `sec_demo_latest_filings` — Preview the SEC filing response shape without an API key. Returns a small public sample only, then call sec_subscription_info for RapidAPI checkout, pricing, MC
- `sec_subscription_info` — Return public pricing, checkout, documentation, and access links for SEC Event Intelligence without an API key. Use this after sec_demo_latest_filings to choose
- `sec_latest_filings` — Fetch a newest-first snapshot of public SEC filings. Use for initial dashboards or latest-form lookups when no polling cursor is needed; use sec_filing_changes 
- `sec_filing_changes` — Fetch filings observed on or after a since date for polling jobs that persist a cursor. Supports ticker/CIK, form, and event-type filters; use sec_latest_filing
- `sec_watchlist_changes` — Fetch incremental filing changes for multiple tickers or CIKs, grouped into per-company buckets. Use for batch watchlist polling, alert fan-out, and dashboards 
- `sec_company_search` — Search the SEC company index by ticker, CIK, or legal name and return identifiers to pass into profile, filings, events, and insider-trade tools. Authentication
- `sec_company_profile` — Fetch one issuer profile with ticker/CIK identity, filing coverage, form counts, and latest known filing. Use after company search to verify the target issuer b
- `sec_company_filings` — Return newest-first filing rows for one company, optionally narrowed by SEC form type. Use when you need accession numbers and filing metadata history, not norm
- `sec_company_events` — Return normalized event records derived from one company's filings. Use when you need event labels and monitoring-friendly changes instead of the full company f
- `sec_insider_trades` — Return public insider ownership filing metadata from Forms 3, 4, and 5, optionally scoped to one ticker or CIK. Use for insider activity monitoring, not trade r
- `sec_filing_summary` — Retrieve one normalized filing summary by SEC accession number, including issuer, form, filed date, source links, and concise summary fields. Use after another 

## Install

**Verdict: review** — Installable, but 2 things to check first: No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
**Cautions** (coverage gaps and advisories — never blocking)
- No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"sec-event-intelligence\": {\n      \"type\": \"http\",\n      \"url\": \"https://api.data-apis.com/mcp\"\n    }\n  }\n}"
```

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on someone else's infrastructure; read-only tool surface.
- Floor 9, ceiling 27 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/com.data-apis.api%2Fsec-event-intelligence
- Install plan: https://forgeregistry.com/api/v1/packages/com.data-apis.api%2Fsec-event-intelligence/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/com.data-apis.api%2Fsec-event-intelligence
- HTML page: https://forgeregistry.com/registry/com.data-apis.api%2Fsec-event-intelligence
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.