# Sec Nport (npm · @pipeworx/mcp-sec-nport)

SEC Form N-PORT — fund and ETF holdings, asked security-first.

- Trust score: 83/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`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-sec-nport/sec-nport-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-sec-nport/sec-nport-mcp)
- npm · `@pipeworx/mcp-sec-nport`: 83/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-sec-nport/pipeworx-mcp-sec-nport.md), [page](https://verifymcp.io/servers/pipeworx-io-sec-nport/pipeworx-mcp-sec-nport)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-sec-nport`
- 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-nport).
  - 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**: 67/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 770 tokens (~192/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**: 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 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.

## Install

### How do I install the Sec Nport MCP server?

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

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

- [security regression] Tool safety: pass → unverified
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Stability: unverified → 0.23
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.2.0 → 0.2.1

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

- [functional regression] Security disclosure: unverified → fail

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

First indexed and scored.

## MCP tools (4)

### `nport_fund_owners` (~209 tokens)

Which mutual funds and ETFs hold a given stock or bond, ranked by position size, from SEC Form N-PORT portfolio filings — the reverse of a fund fact sheet, which makes you name the fund first. Give a ticker ("NVDA"), a company name ("NVIDIA"), or a CUSIP. Returns each fund, its sponsor, the position value, share or principal count, and what percent of that fund's net assets it is. Answers "which ETFs hold the largest positions in NVDA", "what funds own this corporate bond", "who are the biggest fund holders of this stock".

Input parameters:

- `limit` (number): How many holders to return, 1-200 (default 25).
- `quarter` (string): Release to search, e.g. "2026q2". Omit to search everything loaded.
- `security` (string, required): Ticker, company name, or CUSIP. A ticker resolves through OpenFIGI to the underlying company.

### `nport_fund_portfolio` (~165 tokens)

The portfolio a mutual fund or ETF reported to the SEC on Form N-PORT: its largest positions with issuer, value, share or principal count, and percent of net assets. Give the fund or ETF series name ("Vanguard Total Stock Market Index Fund", "SPDR S&P 500 ETF"). Answers "what does this ETF hold", "what are this fund's biggest positions", "how much of this fund is in one stock".

Input parameters:

- `fund` (string, required): Fund or ETF series name, or a fragment of it.
- `limit` (number): How many positions to return, 1-500 (default 50).
- `quarter` (string): Release to read, e.g. "2026q2". Omit for everything loaded.

### `nport_holdings_coverage` (~74 tokens)

Which SEC Form N-PORT releases are loaded, how many funds each carries, the newest reporting period, and what the data does and does not cover. Also reports N-CEN fund-profile coverage (nport_fund_profile). Use this to check how current fund holdings and profile answers are before quoting them.

### `nport_fund_profile` (~268 tokens)

A mutual fund or ETF's profile from SEC Form N-CEN, the annual fund census: ETF/index/money-market status (an explicit flag, which N-PORT holdings filings do not carry), AUM, expense ratio, advisory fee, NAV and market price per share, and its investment adviser(s). Also covers ETFs organized as unit investment trusts (SPY, QQQ, DIA) via N-CEN's separate UIT section — fund_type "unit investment trust", total assets, and administrator(s), but no expense ratio/advisory fee/NAV (Part F does not report those). Give the fund or ETF name ("Vanguard Total Stock Market Index Fund", "SPDR S&P 500 ETF Trust"). Answers "is this fund an ETF", "what's this fund's expense ratio", "who manages this fund", "how big is this fund's AUM". Does NOT cover inception date — N-CEN carries no such field — or portfolio holdings (use nport_fund_portfolio for that). Response discloses a name_match grade (exact/starts_with/contains) and other candidates, since a substring match is never presented as the fund without saying so.

Input parameters:

- `fund` (string, required): Fund or ETF name, or a fragment of it.

## Diagnostics

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

## Score history

- 2026-11-05: 83
- 2026-11-04: 79
- 2026-11-03: 79
- 2026-11-02: 79
- 2026-11-01: 79
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 79

## Common questions

### What is the Sec Nport MCP server?

Sec Nport is an MCP server listed in the public MCP registry as io.github.pipeworx-io/sec-nport. SEC Form N-PORT, fund and ETF holdings, asked security-first. This page covers its npm package (@pipeworx/mcp-sec-nport).

### Is the Sec Nport MCP server safe to use?

Sec Nport scores 83 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 Nport MCP server expose?

Sec Nport exposes 4 tools: nport_fund_owners, nport_fund_portfolio, nport_holdings_coverage, nport_fund_profile. Their descriptions and schemas cost roughly 716 tokens of context every time the server is loaded.

### Is the Sec Nport MCP server still maintained?

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

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

VerifyMCP ran 16 checks on Sec Nport, 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.

## Links

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