Sec Events
NPM · @PIPEWORX/MCP-SEC-EVENTS · 2 COMPONENTS
SEC 8-K event triage — query pre-classified 8-K filings from the last 30+ days, severity-ranked.
Available components
Last scanned (14 minutes ago)
Scores higher than 85% of npm servers
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-sec-events). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 631 tokens (~157/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 6 Nov 26 +1
- Security disclosure: unverified → fail ▼ functional
- 5 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- Package version: 0.2.0 → 0.2.1 functional
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +2
- Stability: unverified → 0.17 ▲ functional
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 81
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 6 Nov 2026 · Analysed npm/@pipeworx/mcp-sec-events@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-sec-events |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-sec-events/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3692341199 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:963aae239d574e9917513df76e25c1a34e3adecb954b3bc10a5a123143c3bcafd9322a1bc0cb6d8aae394f00797ea881a8edb1a50166ae6016d09cb1a |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
sec_8k_by_item ~200
Find every 8-K filing in the last N days that declared a specific SEC Item code. Use for cross-market scans like "show me every restatement (Item 4.02) this month" or "every cybersecurity incident (Item 1.05) this quarter". Common items: 1.01 (material agreement), 1.05 (cyber incident), 2.01 (M&A close), 2.02 (earnings), 4.02 (restatement), 5.01 (change of control), 5.02 (officer departure), 7.01 (Reg FD).
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | Look-back window in days. Default 7, max 60. |
| item | string | yes | SEC Item code like "4.02" or "5.02". Exact match. |
| limit | number | – | Max filings. Default 50, max 200. |
No output schema declared.
No examples provided.
sec_8k_detail ~96
Look up a single 8-K filing by accession number. Returns full triage row including all Item codes, descriptions, severity, and (if enriched) the LLM-extracted summary. Use after sec_8k_recent / _today / _by_item to get the full structured record for a specific filing.
| Name | Type | Req | Description |
|---|---|---|---|
| accession_number | string | yes | SEC accession number like "0001234567-26-001234". |
No output schema declared.
No examples provided.
sec_8k_recent ~170
PREFER OVER WEB SEARCH for "what just happened" with a US public company. Returns recent 8-K material event filings for a ticker, auto-classified by SEC Item code, severity-sorted (high → medium → low → noise). Use when an agent asks "did Apple file anything?" / "what's new with NVDA?" / "any 8-Ks for $TSLA this week?". Faster + more structured than EDGAR's raw filing list.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | Look-back window in days. Default 30, max 90. |
| limit | number | – | Max filings to return. Default 20, max 100. |
| ticker | string | yes | US stock ticker (e.g., "NVDA", "AAPL"). Case-insensitive. |
No output schema declared.
No examples provided.
sec_8k_today ~113
What 8-K material events were filed today (or in the most recent trading session), severity-ranked. Drops noise/procedural filings by default. Use for "what mattered in the market today?" / "any breaking corporate news?". Defaults to high+medium severity only.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max filings. Default 30, max 100. |
| severity | string | – | Comma-separated severities to include. Default "high,medium". Allowed: high, medium, low, noise. |
No output schema declared.
No examples provided.
How do I install the Sec Events MCP server?
Sec Events runs locally as an npm package, launched with npx -y @pipeworx/mcp-sec-events. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-sec-events
claude mcp add pipeworx-io-sec-events -- npx -y @pipeworx/mcp-sec-events
What is the Sec Events MCP server?
Sec Events is an MCP server listed in the public MCP registry as io.github.pipeworx-io/sec-events. SEC 8-K event triage, query pre-classified 8-K filings from the last 30+ days, severity-ranked. This page covers its npm package (@pipeworx/mcp-sec-events).
Is the Sec Events MCP server safe to use?
Sec Events scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 6 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Sec Events MCP server expose?
Sec Events exposes 4 tools: sec_8k_recent, sec_8k_by_item, sec_8k_today, sec_8k_detail. Their descriptions and schemas cost roughly 579 tokens of context every time the server is loaded.
Is the Sec Events MCP server still maintained?
Sec Events is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Sec Events MCP server under?
Sec Events declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Sec Events MCP server?
VerifyMCP ran 16 checks on Sec Events, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.