# Sec Beneficial Ownership (npm · @pipeworx/mcp-sec-beneficial-ownership)

SEC Schedule 13D / 13G — structured beneficial-ownership filings.

- Trust score: 78/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 71/100, [markdown](https://verifymcp.io/servers/pipeworx-io-sec-beneficial-ownership/sec-beneficial-ownership-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-sec-beneficial-ownership/sec-beneficial-ownership-mcp)
- npm · `@pipeworx/mcp-sec-beneficial-ownership`: 78/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-sec-beneficial-ownership/pipeworx-mcp-sec-beneficial-ownership.md), [page](https://verifymcp.io/servers/pipeworx-io-sec-beneficial-ownership/pipeworx-mcp-sec-beneficial-ownership)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-sec-beneficial-ownership`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-sec-beneficial-ownership).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1373 tokens (~343/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability observed for 0 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the Sec Beneficial Ownership MCP server?

Sec Beneficial Ownership runs locally as an npm package, launched with npx -y @pipeworx/mcp-sec-beneficial-ownership. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-sec-beneficial-ownership -- npx -y @pipeworx/mcp-sec-beneficial-ownership
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-sec-beneficial-ownership": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-sec-beneficial-ownership"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-sec-beneficial-ownership": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-sec-beneficial-ownership"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-sec-beneficial-ownership -- npx -y @pipeworx/mcp-sec-beneficial-ownership
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-sec-beneficial-ownership": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-sec-beneficial-ownership"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-sec-beneficial-ownership --command npx --arg -y --arg @pipeworx/mcp-sec-beneficial-ownership
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-sec-beneficial-ownership:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-sec-beneficial-ownership"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-sec-beneficial-ownership": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-sec-beneficial-ownership"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-sec-beneficial-ownership -t stdio -c npx -a -y @pipeworx/mcp-sec-beneficial-ownership
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-sec-beneficial-ownership": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-sec-beneficial-ownership"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 78)

First indexed and scored.

## MCP tools (4)

### `sec_13d_filings` (~296 tokens)

List Schedule 13D / 13G beneficial-ownership filings (and their amendments, 13D/A and 13G/A) for one issuer — AUTHORITATIVE source for "who owns 5%+ of $TICKER" and "has an activist filed a 13D on this company". Takes a ticker or company name (auto-resolved to CIK) or a CIK directly. Each row flags `structured: true/false` — filings from SEC's 2024 XML rule onward are structured and feed straight into sec_13d_filing; older ones are plain text/HTML only. Use sec_13d_filing on any accession_number returned here to get the actual reporting-owner data (percent of class, voting power, purpose).

Input parameters:

- `cik` (string): Alias for ticker_or_cik.
- `form_type` (string): Filter to one form family. "13D" / "13G" exclude amendments; "13D/A" / "13G/A" are amendments only. Default "all".
- `limit` (number): Max rows to return (1-40, default 20).
- `ticker` (string): Alias for ticker_or_cik.
- `ticker_or_cik` (string): Stock ticker ("GME"), company name ("GameStop"), or SEC CIK, of the ISSUER whose beneficial-ownership filings to list.

Output parameters:

- `cik` (string)
- `data_as_of` (string)
- `filings` (array)
- `filter_form_type` (string)
- `issuer_name` (string)
- `returned` (number)
- `tickers` (array)

### `sec_13d_filing` (~260 tokens)

Parse ONE Schedule 13D or 13G filing by issuer + accession_number (get the accession_number from sec_13d_filings). Returns every reporting owner (the "group members") with percent of class, sole/shared voting power, sole/shared dispositive power, and aggregate shares owned; for Schedule 13D, also Item 4 — the free-text "Purpose of Transaction", which is where an activist states its intent (board seats, a merger, liquidation, or "no plans"). Filings from before SEC's 2024 structured-XML rule have no machine-readable fields — this returns `structured: false` plus the bounded plain text of the filing instead of silently returning empty data.

Input parameters:

- `accession_number` (string, required): The filing's SEC accession number, e.g. "0001104659-25-086308" (dashes optional). From sec_13d_filings.
- `cik` (string): Alias for ticker_or_cik.
- `ticker` (string): Alias for ticker_or_cik.
- `ticker_or_cik` (string): Ticker, company name, or CIK of the ISSUER the filing is about (same value you passed to sec_13d_filings).

Output parameters:

- `accession_number` (string)
- `cik` (string)
- `data_as_of` (string)
- `event_date` (string|null)
- `filing_index_url` (string)
- `form` (string)
- `form_family` (string)
- `is_amendment` (boolean)
- `issuer_name` (string)
- `item4_purpose` (string|null)
- `items` (object)
- `note` (string|null)
- `primary_document_url` (string)
- `raw_text` (string|null)
- `raw_text_truncated` (boolean|null)
- `reporting_owners` (array)
- `securities_class_title` (string|null)
- `structured` (boolean)

### `sec_13d_search` (~484 tokens)

MARKET-WIDE search of Schedule 13D / 13G beneficial-ownership filings by FILING DATE — no ticker needed. AUTHORITATIVE for "which activist investors filed new 13Ds this month and which companies did they target", "who disclosed a 5%+ stake in anything last week", "new 13G filings since Monday". Returns, per filing: the SUBJECT company (the issuer targeted, with ticker and CIK), the FILERS (investors / reporting persons, with CIK), form, filing date, and whether it is an amendment. By default only NEW filings (amendments excluded; set include_amendments true to add 13D/A and 13G/A). For the first `enrich` structured filings (post-2024 XML rule, default 5, max 10) it also reads the filing itself and adds the reporting owners' percent of class and shares owned, the event date, and — for 13D — the Item 4 "Purpose of Transaction" text (the activist signal). Rows beyond `enrich` carry the index fields only; pass their accession to sec_13d_filing for the full parse. `total_matches` is the true count for the window, `scanned` how many were read (at most 300), and `truncated` says honestly when the window held more than was scanned — narrow the date range rather than assuming completeness. Default window: the last 30 days.

Input parameters:

- `end_date` (string): Last filing date, YYYY-MM-DD. Default: today.
- `enrich` (number): How many of the returned structured filings to read in full for percent of class and Item 4 purpose (0-10, default 5). Each is one SEC document fetch.
- `form_family` (string): "13D" (default; active / activist stakes), "13G" (passive 5%+ holders) or "all".
- `include_amendments` (boolean): Include 13D/A and 13G/A amendments. Default false (new filings only).
- `limit` (number): Max filings to return (1-100, default 25), newest first.
- `start_date` (string): First filing date, YYYY-MM-DD. Default: 30 days before end_date.

Output parameters:

- `data_as_of` (string)
- `date_range` (object)
- `form_family` (string)
- `include_amendments` (boolean)
- `matched_after_filter` (number)
- `note` (string|null)
- `results` (array)
- `returned` (number)
- `scanned` (number)
- `source` (string)
- `total_matches` (number)
- `truncated` (boolean)

### `sec_13d_amendment_diff` (~275 tokens)

Given one 13D/A or 13G/A amendment (issuer + accession_number), find the SAME reporting group's prior filing in the chain and diff what changed: percent of class, aggregate shares owned, sole/shared voting & dispositive power (per reporting owner, matched by CIK or name), and — for 13D — whether the Item 4 purpose text changed. Walks back through the issuer's filing history (bounded, never a bulk crawl) matching on reporting-owner identity, since EDGAR does not carry an explicit "previous accession" link for this form family. Reports `prior_filing_found: false` honestly if no matching prior filing turns up within the scan bound, or if the chain predates the structured-XML rule (diffing free text is not meaningful).

Input parameters:

- `accession_number` (string, required): Accession number of the AMENDMENT (13D/A or 13G/A) to diff against its predecessor. Also accepts an original 13D/13G, in which case there is by definition no prior filing.
- `cik` (string): Alias for ticker_or_cik.
- `ticker` (string): Alias for ticker_or_cik.
- `ticker_or_cik` (string): Ticker, company name, or CIK of the ISSUER.

Output parameters:

- `changes` (object|null)
- `cik` (string)
- `current` (object)
- `data_as_of` (string)
- `issuer_name` (string)
- `note` (string|null)
- `prior` (object|null)
- `prior_filing_found` (boolean)
- `scan_limit` (number)
- `scanned` (number)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-sec-beneficial-ownership/pipeworx-mcp-sec-beneficial-ownership#diagnostics

## Score history

- 2026-11-05: 78

## Common questions

### What is the Sec Beneficial Ownership MCP server?

Sec Beneficial Ownership is an MCP server listed in the public MCP registry as io.github.pipeworx-io/sec-beneficial-ownership. SEC Schedule 13D / 13G, structured beneficial-ownership filings. This page covers its npm package (@pipeworx/mcp-sec-beneficial-ownership).

### Is the Sec Beneficial Ownership MCP server safe to use?

Sec Beneficial Ownership scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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 Beneficial Ownership MCP server expose?

Sec Beneficial Ownership exposes 4 tools: sec_13d_filings, sec_13d_filing, sec_13d_search, sec_13d_amendment_diff. Their descriptions and schemas cost roughly 1,315 tokens of context every time the server is loaded.

### Is the Sec Beneficial Ownership MCP server still maintained?

Sec Beneficial Ownership is still listed as active in the MCP registry. We last reached this channel on 5 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 Beneficial Ownership MCP server under?

Sec Beneficial Ownership declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-sec-beneficial-ownership
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-sec-beneficial-ownership
- Repository: https://github.com/pipeworx-io/mcp-sec-beneficial-ownership
- Website: https://pipeworx.io/packs/sec-beneficial-ownership
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-sec-beneficial-ownership/pipeworx-mcp-sec-beneficial-ownership.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-sec-beneficial-ownership/pipeworx-mcp-sec-beneficial-ownership.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-sec-beneficial-ownership/pipeworx-mcp-sec-beneficial-ownership