io.github.toolstem/toolstem-sec-mcp-server
NPM · TOOLSTEM-SEC-MCP-SERVER · SCANNED SEP 24
SEC filing MCP for AI agents — insider signals, 13F flow, material events. Pre-computed.
Available components
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 Security93
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known medium-severity CVE affects stream-json 1.9.1, reached via apify > @crawlee/core > stream-json. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 76 of 263 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 107 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
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 Management97
- Stability observed for 29 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
- 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
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
claude mcp add toolstem-toolstem-sec-mcp-server -- npx -y toolstem-sec-mcp-server
{
"mcpServers": {
"toolstem-toolstem-sec-mcp-server": {
"command": "npx",
"args": [
"-y",
"toolstem-sec-mcp-server"
]
}
}
} {
"servers": {
"toolstem-toolstem-sec-mcp-server": {
"command": "npx",
"args": [
"-y",
"toolstem-sec-mcp-server"
]
}
}
} codex mcp add toolstem-toolstem-sec-mcp-server -- npx -y toolstem-sec-mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"toolstem-toolstem-sec-mcp-server": {
"type": "local",
"command": [
"npx",
"-y",
"toolstem-sec-mcp-server"
],
"enabled": true
}
}
} openclaw mcp add toolstem-toolstem-sec-mcp-server --command npx --arg -y --arg toolstem-sec-mcp-server
mcp_servers:
toolstem-toolstem-sec-mcp-server:
command: "npx"
args: ["-y", "toolstem-sec-mcp-server"] {
"McpServers": {
"toolstem-toolstem-sec-mcp-server": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"toolstem-sec-mcp-server"
]
}
}
} assistant mcp add toolstem-toolstem-sec-mcp-server -t stdio -c npx -a -y toolstem-sec-mcp-server
{
"mcpServers": {
"toolstem-toolstem-sec-mcp-server": {
"command": "npx",
"args": [
"-y",
"toolstem-sec-mcp-server"
]
}
}
} 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.
- 24 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 −3
- Stability: pass → 0.77 functional
- 17 Sept 26 0
- Stability: 0.97 → pass security
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 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.
- 11 Sept 26 −2
- Stability: pass → 0.80 functional
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 24 Sept 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 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-528h-pc64-c93x | CVE-2026-71429 | medium | CVSS:3.1/AV:L/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 263 packages
| Packages resolved | 263 |
|---|---|
| Deprecated | 1 |
| Stale | 76 |
| 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 →
compare_disclosure_signals 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.
| Name | Type | Req | Description |
|---|---|---|---|
| tickers_or_ciks | array | yes | 2-5 ticker symbols or CIKs to compare (e.g. ["AAPL", "MSFT", "GOOGL"]). |
| Name | Type | Req | Description |
|---|---|---|---|
| companies | array | yes | – |
| meta | object | yes | – |
| winners | object | yes | – |
No examples provided.
get_company_filings_summary 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.
| Name | Type | Req | Description |
|---|---|---|---|
| ticker_or_cik | string | yes | Ticker symbol (e.g. "AAPL") or numeric CIK (e.g. "320193" or "0000320193"). |
| Name | Type | Req | Description |
|---|---|---|---|
| cik | string | yes | – |
| company_name | string|null | yes | – |
| meta | object | yes | – |
| recent_filings | array | yes | – |
| signals | object | yes | – |
| ticker | string|null | yes | – |
No examples provided.
get_insider_signal 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.
| Name | Type | Req | Description |
|---|---|---|---|
| lookback_days | integer | – | Number of calendar days to look back (default 90, max 730). |
| ticker_or_cik | string | yes | Ticker symbol (e.g. "MSFT") or numeric CIK. |
| Name | Type | Req | Description |
|---|---|---|---|
| buy_count | number | yes | – |
| cik | string | yes | – |
| company_name | string|null | yes | – |
| insider_signal | – | yes | – |
| lookback_days | number | yes | – |
| meta | object | yes | – |
| net_transaction_count | number | yes | – |
| recent_insider_filings | array | yes | – |
| sell_count | number | yes | – |
| ticker | string|null | yes | – |
No examples provided.
get_institutional_signal 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.
| Name | Type | Req | Description |
|---|---|---|---|
| quarters_back | integer | – | Number of calendar quarters to look back (default 4 ≈ 1 year, max 20). |
| ticker_or_cik | string | yes | Ticker symbol (e.g. "NVDA") or numeric CIK. |
| Name | Type | Req | Description |
|---|---|---|---|
| activist_risk_flag | boolean | yes | – |
| cik | string | yes | – |
| company_name | string|null | yes | – |
| institutional_signal | – | yes | – |
| meta | object | yes | – |
| quarters_back | number | yes | – |
| recent_13d_filings | array | yes | – |
| recent_13f_count | number | yes | – |
| ticker | string|null | yes | – |
No examples provided.
get_material_events_digest 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.
| Name | Type | Req | Description |
|---|---|---|---|
| lookback_days | integer | – | Number of calendar days to include (default 365, max 1825 / 5 years). |
| ticker_or_cik | string | yes | Ticker symbol (e.g. "TSLA") or numeric CIK. |
| Name | Type | Req | Description |
|---|---|---|---|
| category_counts | object | yes | – |
| cik | string | yes | – |
| company_name | string|null | yes | – |
| events | array | yes | – |
| lookback_days | number | yes | – |
| meta | object | yes | – |
| redflag_count | number | yes | – |
| ticker | string|null | yes | – |
No examples provided.
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 82 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 24 September 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 24 September 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.