Sec Nport
NPM · @PIPEWORX/MCP-SEC-NPORT · 2 COMPONENTS
SEC Form N-PORT — fund and ETF holdings, asked security-first.
Available components
Last scanned (12 hours ago)
Scores higher than 76% 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-nport). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 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.
- 5 Nov 26 +4
- 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. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Stability: unverified → 0.23 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.0 → 0.2.1 functional
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 79
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-sec-nport@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-nport |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-sec-nport/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3692342281 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:24eed806dff6711071b2d33e55136860cfa0d20d71d801eeb418b6302b2fa9e40fa4b38131eba073169782e684625b0d17f93ba05ec5b8a29a7d6b724 |
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 →
nport_fund_owners ~209
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".
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Ticker, company name, or CUSIP. A ticker resolves through OpenFIGI to the underlying company. |
No output schema declared.
No examples provided.
nport_fund_portfolio ~165
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".
| Name | Type | Req | Description |
|---|---|---|---|
| fund | string | yes | 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. |
No output schema declared.
No examples provided.
nport_fund_profile ~268
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.
| Name | Type | Req | Description |
|---|---|---|---|
| fund | string | yes | Fund or ETF name, or a fragment of it. |
No output schema declared.
No examples provided.
nport_holdings_coverage ~74
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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.
npm · @pipeworx/mcp-sec-nport
claude mcp add pipeworx-io-sec-nport -- npx -y @pipeworx/mcp-sec-nport
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.