Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Sec Insider

NPM · @PIPEWORX/MCP-SEC-INSIDER · 2 COMPONENTS

SEC Forms 3/4/5 — insider transactions, indexed so the question can be inverted.

+4 this week 81 Trust /100

Last scanned (20 hours ago)

Scores higher than 68% of npm servers

Category Finance and Payments

Trust breakdown (7 categories)

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-insider). 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 Usability55
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1514 tokens (~504/item across 3 items; 3 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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
What we tested

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 →

Changelog

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
    • Security disclosure: unverified → fail ▼ functional
    • 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
  • 4 Nov 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 29 Oct 26 77

    First indexed and scored.

Diagnostics

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-insider@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-insider
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-sec-insider/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3692341859
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:f204296d3d936b2f479230e0490a1b0de5cfe7a9701cfbcaf8dfcf9f7ba6b63565e2a48cb7844a9807c029629fb6f4d9755ee7558b29cad2c25dc456b

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~1,460 tokens

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 →

Tool Tokens
insider_coverage ~56

Which SEC insider data is currently available: which quarterly releases are covered, how many filings, owners and transactions, and the date range of the transactions themselves. Call this to check how current the insider data is before relying on a ranking.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

insider_top_buyers ~718

Stock purchases by a company's insiders and major holders, from SEC Form 4 — one buyer at one company, every buyer at one company, or the biggest buyers market-wide: "how much Occidental stock did Berkshire Hathaway buy in March", "insider buying at Pfizer this quarter", "which insiders bought the most stock recently", "largest insider purchase last month". Pass issuer (ticker or company name) and owner (a person or a firm, e.g. "Berkshire") to narrow it, since/until for the period, and group_by "owner" for one buyer's total across several filings. Officers, directors and 10% owners — including large investors and funds holding over 10% of a company — file a Form 4 within two business days of every trade, so this gives the exact trade dates, shares, price per share and dollar value inside any month or week. Returns the insider name and role, the issuer and ticker, shares, price and value. Counts only transaction code P, a purchase at market; option exercises, grants and tax withholding are excluded because none of them is a decision to buy. Ranks over every row in the window — never a capped slice — and reports rows_considered so a cut is never silent. A price the filer states in another currency (e.g. Brazilian reais, in a footnote) is left out and counted in non_usd_rows_excluded, never ranked as dollars. A price that looks like a filer data-entry error is left out unless include_suspect is set, and a report filed as several parts counts as one filing. Sourced from SEC Forms 3/4/5.

NameTypeReqDescription
exclude_fundsboolean–Drop issuers that are funds reporting unitholders, not operating companies with real insiders (e.g. a BDC or interval fund). Best-effort name/security-type heuristic. Default false.
group_bystring–How to roll transactions up before ranking. "filing" (default): sum every row on the same Form 4 into one total — a filing often reports one decision as several price-band lines, and a price-band row…
include_suspectboolean–Include transactions whose price looks like a filer data-entry error (see the caveat). Default false — suspect rows are excluded from rankings.
issuerstring–Limit to one issuer — ticker (e.g. "LEN") or SEC CIK. Substring match on issuer name also works.
limitnumber–How many to return (default 20, max 100).
min_value_usdnumber–Ignore transactions below this dollar value.
ownerstring–Limit to one insider — name substring (e.g. "Berkshire") or SEC CIK.
sincestring–Earliest transaction date, ISO (YYYY-MM-DD). Defaults to the last 90 days of the loaded window.
untilstring–Latest transaction date, ISO (YYYY-MM-DD).

No output schema declared.

No examples provided.

insider_top_sellers ~686

Stock sales by a company's insiders and major holders, from SEC Form 4 — one seller at one company, every seller at one company, or the biggest sellers market-wide: "how many Amazon shares did Jeff Bezos sell in July", "insider selling at Apple this year", "which insiders sold the most stock recently", "largest insider sale last month". Pass issuer (ticker or company name) and owner (a person or a firm) to narrow it, since/until for the period, and group_by "owner" for one seller's total across several filings. Officers, directors and 10% owners file a Form 4 within two business days of every trade, so this gives the exact trade dates, shares, price per share and dollar value inside any month or week. Returns insider name and role, issuer and ticker, shares, price and dollar value. Counts only transaction code S, a sale at market; shares withheld for tax (F) are excluded, since those are a payroll mechanism rather than a decision to sell. Ranks over every row in the window — never a capped slice — and reports rows_considered so a cut is never silent. A price the filer states in another currency (e.g. Brazilian reais, in a footnote) is left out and counted in non_usd_rows_excluded, never ranked as dollars. A price that looks like a filer data-entry error is left out unless include_suspect is set, and a report filed as several parts counts as one filing. Sourced from SEC Forms 3/4/5.

NameTypeReqDescription
exclude_fundsboolean–Drop issuers that are funds reporting unitholders, not operating companies with real insiders (e.g. a BDC or interval fund). Best-effort name/security-type heuristic. Default false.
group_bystring–How to roll transactions up before ranking. "filing" (default): sum every row on the same Form 4 into one total — a filing often reports one decision as several price-band lines, and a price-band row…
include_suspectboolean–Include transactions whose price looks like a filer data-entry error (see the caveat). Default false — suspect rows are excluded from rankings.
issuerstring–Limit to one issuer — ticker (e.g. "LEN") or SEC CIK. Substring match on issuer name also works.
limitnumber–How many to return (default 20, max 100).
min_value_usdnumber–Ignore transactions below this dollar value.
ownerstring–Limit to one insider — name substring (e.g. "Berkshire") or SEC CIK.
sincestring–Earliest transaction date, ISO (YYYY-MM-DD).
untilstring–Latest transaction date, ISO (YYYY-MM-DD).

No output schema declared.

No examples provided.

Install

How do I install the Sec Insider MCP server?

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

# add to Claude Code
claude mcp add pipeworx-io-sec-insider -- npx -y @pipeworx/mcp-sec-insider
Common questions

What is the Sec Insider MCP server?

Sec Insider is an MCP server listed in the public MCP registry as io.github.pipeworx-io/sec-insider. SEC Forms 3/4/5, insider transactions, indexed so the question can be inverted. This page covers its npm package (@pipeworx/mcp-sec-insider).

Is the Sec Insider MCP server safe to use?

Sec Insider scores 81 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 Insider MCP server expose?

Sec Insider exposes 3 tools: insider_top_buyers, insider_top_sellers, insider_coverage. Their descriptions and schemas cost roughly 1,460 tokens of context every time the server is loaded.

Is the Sec Insider MCP server still maintained?

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

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

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