# Sec 13f (npm · @pipeworx/mcp-sec-13f)

SEC 13F — institutional ownership, asked security-first.

- Trust score: 84/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 70/100, [markdown](https://verifymcp.io/servers/pipeworx-io-sec-13f/sec-13f-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-sec-13f/sec-13f-mcp)
- npm · `@pipeworx/mcp-sec-13f`: 84/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-sec-13f/pipeworx-mcp-sec-13f.md), [page](https://verifymcp.io/servers/pipeworx-io-sec-13f/pipeworx-mcp-sec-13f)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-sec-13f`
- 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-13f).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 922 tokens (~153/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 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.

## Install

### How do I install the Sec 13f MCP server?

Sec 13f runs locally as an npm package, launched with npx -y @pipeworx/mcp-sec-13f. 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-13f -- npx -y @pipeworx/mcp-sec-13f
```

### Cursor

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

### VS Code

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

### Codex

```bash
codex mcp add pipeworx-io-sec-13f -- npx -y @pipeworx/mcp-sec-13f
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add pipeworx-io-sec-13f --command npx --arg -y --arg @pipeworx/mcp-sec-13f
```

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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 84, +4)

- [functional regression] Security disclosure: fail → unverified
- [functional improvement] Stability: unverified → 0.23
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-30 (score 80, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-29 (score 80)

First indexed and scored.

## MCP tools (6)

### `who_owns` (~214 tokens)

Which institutional managers hold a given US-listed security, ranked by position size — the reverse of every 13F API, which requires you to name the manager first. Give a company name, ticker (e.g. "NVDA") or 9-character CUSIP. Ticker input is resolved through OpenFIGI, not a bulk symbol table. Returns each manager, the value of their position in USD, share count, and the reporting quarter. Answers "who owns NVDA", "which funds hold the most Apple", "institutional ownership of Tesla". Sourced from SEC Form 13F. Where a manager amended a quarter (13F-HR/A), each position is counted once, from the latest filing that reports it.

Input parameters:

- `limit` (number): How many managers to return, 1-100 (default 25).
- `security` (string, required): Company name, ticker or 9-character CUSIP — e.g. "NVIDIA", "NVDA", "67066G104".

### `manager_portfolio` (~114 tokens)

Every 13F position reported by one institutional manager, largest first — the classic manager-first view, over the same indexed data. Give the manager name ("Berkshire Hathaway", "Pershing Square"). Returns each holding with value and share count, plus the reported quarter. For what CHANGED since the prior quarter use manager_changes instead.

Input parameters:

- `limit` (number): How many positions to return, 1-200 (default 50).
- `manager` (string, required): Filing manager name or a distinctive fragment of it.

### `manager_changes` (~223 tokens)

What one institutional manager NEW-ed, EXITED, INCREASED or DECREASED between two 13F quarters — the newsletter primitive: a portfolio snapshot is not news, a change is. Give the manager name; optionally the two report quarters to compare (YYYY-MM-DD, e.g. "2026-03-31"), defaulting to the two most recent quarters loaded for that manager. Returns four ranked lists (new positions, exits, adds, trims) each with issuer, CUSIP, value in both quarters and the dollar delta.

Input parameters:

- `compare_to` (string): The earlier ("from") quarter. Defaults to the manager's next-most-recent loaded quarter.
- `limit` (number): Max rows per bucket (new/exited/increased/decreased), 1-100 (default 25).
- `manager` (string, required): Filing manager name or a distinctive fragment of it.
- `quarter` (string): The later ("to") quarter, e.g. "2026-03-31". Defaults to the manager's most recent loaded quarter.

### `security_flows` (~129 tokens)

Net institutional buying or selling of one security across the loaded 13F quarters — total position value and holder count per quarter, plus which managers newly bought, sold out, added to or trimmed that security between the two most recent quarters. Give a company name, ticker or CUSIP. Use for "is institutional ownership of NVDA growing", "who has been buying/selling Tesla".

Input parameters:

- `limit` (number): Max managers per bucket in the mover lists, 1-100 (default 25).
- `security` (string, required): Company name, ticker or 9-character CUSIP.

### `manager_profile` (~120 tokens)

A profile of one institutional manager's 13F book: portfolio concentration (share of value in the top 5 / top 10 positions), turnover between the two most recent loaded quarters, and top positions. Use to characterize a manager's style before targeting them (e.g. for a newsletter) — concentrated vs. diversified, high vs. low turnover. Does NOT include sector/industry exposure: 13F carries no such field, and this pack does not fabricate one.

Input parameters:

- `manager` (string, required): Filing manager name or a distinctive fragment of it.

### `holdings_coverage` (~66 tokens)

What this 13F dataset currently covers: which SEC release windows and reporting quarters are loaded, how many filings and holdings rows are in each, and total size. Use to check freshness and to know which quarters manager_changes/security_flows can actually compare before relying on an ownership answer.

## Diagnostics

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

## Score history

- 2026-11-05: 84
- 2026-11-04: 80
- 2026-11-03: 80
- 2026-11-02: 80
- 2026-11-01: 80
- 2026-10-31: 80
- 2026-10-30: 80
- 2026-10-29: 80

## Common questions

### What is the Sec 13f MCP server?

Sec 13f is an MCP server listed in the public MCP registry as io.github.pipeworx-io/sec-13f. SEC 13F, institutional ownership, asked security-first. This page covers its npm package (@pipeworx/mcp-sec-13f).

### Is the Sec 13f MCP server safe to use?

Sec 13f scores 84 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 13f MCP server expose?

Sec 13f exposes 6 tools: who_owns, manager_portfolio, manager_changes, security_flows, manager_profile, holdings_coverage. Their descriptions and schemas cost roughly 866 tokens of context every time the server is loaded.

### Is the Sec 13f MCP server still maintained?

Sec 13f 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 13f MCP server under?

Sec 13f 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 13f MCP server?

VerifyMCP ran 15 checks on Sec 13f, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Sec 13f: Security disclosure. 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.

## Links

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