Sec 13f
NPM · @PIPEWORX/MCP-SEC-13F · 2 COMPONENTS
SEC 13F — institutional ownership, asked security-first.
Available components
Last scanned (21 hours ago)
Scores higher than 81% 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-13f). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- 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. 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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 (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
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
- Security disclosure: fail → unverified ▼ functional
- Stability: unverified → 0.23 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 80
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-13f@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-13f |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-sec-13f/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3692340581 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:a9297d1981f97e8d87b969405abe4205d216785cf21dc415b57be372c17e55282391aed884b391316d700ad39abdec8a68b9ae8c3710b0c192eb26f3d |
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 →
holdings_coverage ~66
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
manager_changes ~223
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
manager_portfolio ~114
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | How many positions to return, 1-200 (default 50). |
| manager | string | yes | Filing manager name or a distinctive fragment of it. |
No output schema declared.
No examples provided.
manager_profile ~120
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.
| Name | Type | Req | Description |
|---|---|---|---|
| manager | string | yes | Filing manager name or a distinctive fragment of it. |
No output schema declared.
No examples provided.
security_flows ~129
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".
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max managers per bucket in the mover lists, 1-100 (default 25). |
| security | string | yes | Company name, ticker or 9-character CUSIP. |
No output schema declared.
No examples provided.
who_owns ~214
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | How many managers to return, 1-100 (default 25). |
| security | string | yes | Company name, ticker or 9-character CUSIP — e.g. "NVIDIA", "NVDA", "67066G104". |
No output schema declared.
No examples provided.
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.
npm · @pipeworx/mcp-sec-13f
claude mcp add pipeworx-io-sec-13f -- npx -y @pipeworx/mcp-sec-13f
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.