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.

io.github.toolstem/toolstem-sec-mcp-server

NPM · TOOLSTEM-SEC-MCP-SERVER

SEC filing MCP for AI agents — insider signals, 13F flow, material events. Pre-computed.

0 this week 79 Trust /100

Last scanned (22 hours ago)

Scores higher than 63% 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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 74 of 259 dependencies flagged as unhealthy (2 deprecated). View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability75
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 774 tokens (~154/item across 5 items; 5 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 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
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.

  • 18 Nov 26 +1
    • Stability: 0.97 → pass security
  • 16 Nov 26 −1
    • Stability: pass → 0.93 functional
  • 13 Nov 26 0
    • CVE-2026-126345 affects this package: high ▼ security
    • CVE-2026-126346 affects this package: high ▼ security
  • 10 Nov 26 +1
    • Stability: 0.97 → pass security
  • 8 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 6 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

  • 4 Nov 26 −3
    • Stability: pass → 0.80 functional
  • 31 Oct 26 0
    • CVE-2026-118764 affects this package: high ▼ security
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 21 Nov 2026 · Analysed npm/toolstem-sec-mcp-server@0.1.9

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 5 findings
ID CVE Severity Vector Fix available
GHSA-5pm8-86m8-9m6r CVE-2026-126345 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes
GHSA-c475-qrg2-pj4r CVE-2026-102990 high yes
GHSA-r4jh-29pc-gfqr CVE-2026-126346 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-g3hv-75wg-m249 CVE-2026-118764 medium yes
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 259 packages
Packages resolved 259
Deprecated 2
Stale 73
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~774 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
compare_disclosure_signals ~144

Side-by-side comparison of 2-5 companies across key SEC disclosure signals: filing velocity, material event count (90d), red-flag count (365d), activist risk flag, and most recent filing date. Returns derived "winners" for each dimension — quietest disclosure, most active filer, most red flags, and companies with active activist investors. All lookups run in parallel. Use for competitive intelligence or risk triage across a watchlist.

NameTypeReqDescription
tickers_or_ciksarrayyes2-5 ticker symbols or CIKs to compare (e.g. ["AAPL", "MSFT", "GOOGL"]).
NameTypeReqDescription
companiesarrayyes–
metaobjectyes–
winnersobjectyes–

No examples provided.

get_company_filings_summary ~150

Retrieve a structured overview of a company's SEC filing activity. Returns the most recent 20 filings and pre-computed signals: filing velocity (ACCELERATING / NORMAL / SLOWING vs. trailing 365-day average), material event count in the last 90 days, 10-K disclosure volume trend (RISING / STABLE / FALLING), and the unique form types filed in the last 90 days. Use this as a first-pass signal before digging into insider or material-event detail.

NameTypeReqDescription
ticker_or_cikstringyesTicker symbol (e.g. "AAPL") or numeric CIK (e.g. "320193" or "0000320193").
NameTypeReqDescription
cikstringyes–
company_namestring|nullyes–
metaobjectyes–
recent_filingsarrayyes–
signalsobjectyes–
tickerstring|nullyes–

No examples provided.

get_insider_signal ~144

Probe insider filing activity (Form 3, 4, 4/A) for a company over a configurable lookback window. Answers: "Are insiders filing recently?" Returns recent Form 4 filing references and counts. NOTE: Direction-aware buy/sell signals (insider_signal, buy_count, sell_count) are null/0 in v0.1 — Form 4 XML parsing ships in v0.2.

NameTypeReqDescription
lookback_daysinteger–Number of calendar days to look back (default 90, max 730).
ticker_or_cikstringyesTicker symbol (e.g. "MSFT") or numeric CIK.
NameTypeReqDescription
buy_countnumberyes–
cikstringyes–
company_namestring|nullyes–
insider_signal–yes–
lookback_daysnumberyes–
metaobjectyes–
net_transaction_countnumberyes–
recent_insider_filingsarrayyes–
sell_countnumberyes–
tickerstring|nullyes–

No examples provided.

get_institutional_signal ~167

Probe institutional and activist investor signals for a company. Returns a live activist_risk_flag (true if any SC 13D or 13D/A was filed in the last 365 days — an activist investor has disclosed a large stake). Also lists the 13D filings and their SEC URLs. NOTE: Institutional accumulation/distribution signal (institutional_signal) and recent_13f_count are null/0 in v0.1 — quarterly 13F XBRL parsing ships in v0.2.

NameTypeReqDescription
quarters_backinteger–Number of calendar quarters to look back (default 4 ≈ 1 year, max 20).
ticker_or_cikstringyesTicker symbol (e.g. "NVDA") or numeric CIK.
NameTypeReqDescription
activist_risk_flagbooleanyes–
cikstringyes–
company_namestring|nullyes–
institutional_signal–yes–
metaobjectyes–
quarters_backnumberyes–
recent_13d_filingsarrayyes–
recent_13f_countnumberyes–
tickerstring|nullyes–

No examples provided.

get_material_events_digest ~169

Retrieve a severity-ranked digest of all 8-K and 8-K/A filings for a company within a configurable lookback window. Each event is tagged with item codes mapped to plain-English labels, categories, and severity (RED / YELLOW / GREEN). Returns redflag_count (events with any RED item) and category_counts for quick categorical analysis. Answers: "Has this company disclosed a cybersecurity incident, restatement, or going-concern risk recently?" Premium-tier tool. See the actor pricing page for current per-call cost.

NameTypeReqDescription
lookback_daysinteger–Number of calendar days to include (default 365, max 1825 / 5 years).
ticker_or_cikstringyesTicker symbol (e.g. "TSLA") or numeric CIK.
NameTypeReqDescription
category_countsobjectyes–
cikstringyes–
company_namestring|nullyes–
eventsarrayyes–
lookback_daysnumberyes–
metaobjectyes–
redflag_countnumberyes–
tickerstring|nullyes–

No examples provided.

Install

How do I install the io.github.toolstem/toolstem-sec-mcp-server server?

io.github.toolstem/toolstem-sec-mcp-server runs locally as an npm package, launched with npx -y toolstem-sec-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · toolstem-sec-mcp-server

# add to Claude Code
claude mcp add toolstem-toolstem-sec-mcp-server -- npx -y toolstem-sec-mcp-server
Common questions

What is the io.github.toolstem/toolstem-sec-mcp-server server?

io.github.toolstem/toolstem-sec-mcp-server is listed in the public MCP registry as io.github.toolstem/toolstem-sec-mcp-server. SEC filing MCP for AI agents, insider signals, 13F flow, material events. Pre-computed. This page covers its npm package (toolstem-sec-mcp-server).

Is the io.github.toolstem/toolstem-sec-mcp-server server safe to use?

io.github.toolstem/toolstem-sec-mcp-server scores 79 out of 100 on VerifyMCP. We recorded 5 known advisories against it as of 21 November 2026. It declares no install or post-install scripts. 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 io.github.toolstem/toolstem-sec-mcp-server server expose?

io.github.toolstem/toolstem-sec-mcp-server exposes 5 tools: get_company_filings_summary, get_insider_signal, get_institutional_signal, get_material_events_digest, compare_disclosure_signals. Their descriptions and schemas cost roughly 774 tokens of context every time the server is loaded.

Is the io.github.toolstem/toolstem-sec-mcp-server server still maintained?

io.github.toolstem/toolstem-sec-mcp-server is still listed as active in the MCP registry. We last reached this channel on 21 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 io.github.toolstem/toolstem-sec-mcp-server server under?

io.github.toolstem/toolstem-sec-mcp-server 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 io.github.toolstem/toolstem-sec-mcp-server server?

VerifyMCP ran 16 checks on io.github.toolstem/toolstem-sec-mcp-server, 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.