# io.github.CloudCorpRecords/filingpulse (npm · @reneturcios/filingpulse)

Fresh SEC filing intel: 8-K events, Form 4 insider activity, filing search and digests.

- Trust score: 70/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- npm · `@reneturcios/filingpulse`: 70/100 (this document), [markdown](https://verifymcp.io/servers/cloudcorprecords-filingpulse/reneturcios-filingpulse.md), [page](https://verifymcp.io/servers/cloudcorprecords-filingpulse/reneturcios-filingpulse)
- oci · `ghcr.io/cloudcorprecords/filingpulse`: 42/100, [markdown](https://verifymcp.io/servers/cloudcorprecords-filingpulse/ghcr-io-cloudcorprecords-filingpulse.md), [page](https://verifymcp.io/servers/cloudcorprecords-filingpulse/ghcr-io-cloudcorprecords-filingpulse)

## Channel facts

- Registry: `npm`
- Package: `@reneturcios/filingpulse`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 636 tokens (~127/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the io.github.CloudCorpRecords/filingpulse MCP server?

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

### Claude

```bash
claude mcp add cloudcorprecords-filingpulse -- npx -y @reneturcios/filingpulse mcp
```

### Cursor

```json
{
  "mcpServers": {
    "cloudcorprecords-filingpulse": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/filingpulse",
        "mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cloudcorprecords-filingpulse": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/filingpulse",
        "mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cloudcorprecords-filingpulse -- npx -y @reneturcios/filingpulse mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cloudcorprecords-filingpulse": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@reneturcios/filingpulse",
        "mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cloudcorprecords-filingpulse --command npx --arg -y --arg @reneturcios/filingpulse --arg mcp
```

### Hermes

```yaml
mcp_servers:
  cloudcorprecords-filingpulse:
    command: "npx"
    args: ["-y", "@reneturcios/filingpulse", "mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "cloudcorprecords-filingpulse": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@reneturcios/filingpulse",
        "mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add cloudcorprecords-filingpulse -t stdio -c npx -a -y @reneturcios/filingpulse mcp
```

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-filingpulse": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/filingpulse",
        "mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-18 (score 70, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-17 (score 55)

First indexed and scored.

## MCP tools (5)

### `whats_new_since` (~209 tokens)

Return SEC filings that are NEW since a cursor token (your bookmark). Pass the cursor from a prior call to get only filings since then. Filter by form type, ticker, CIK, 8-K item code, and minimum event severity. This is the fresh-filing delta feed's core lock-in primitive. Monitoring/research over public EDGAR data — not investment advice.

Input parameters:

- `cik` (string): CIK number of the company in the SEC EDGAR system
- `cursor` (string): Opaque cursor from a previous response; omit for first call.
- `form` (array): Form types, e.g. ['8-K','4'].
- `item` (string): 8-K item code, e.g. '5.02'.
- `limit` (number): Max filings to return (default 100).
- `minEventScore` (number): Severity floor 1-10 (material events only).
- `ticker` (string): Stock ticker symbol of the company

### `filing_digest` (~161 tokens)

Digest for a filter over the last N days: material 8-K events, insider (Form 4) activity, new registrations, and periodic reports. Best summary signal for a desk.

Input parameters:

- `cik` (string): CIK number of the company in the SEC EDGAR system
- `company` (string): Company name to match filings against
- `days` (number): Lookback days (default 7).
- `form` (array): SEC form types to include, such as 10-K or 8-K
- `item` (string): Filing item or section to focus the digest on
- `minEventScore` (number): Minimum event score for a filing to be included
- `ticker` (string): Stock ticker symbol of the company

### `company_watch` (~68 tokens)

Given a company CIK, return recent filings, insider activity, and a filing-velocity stat (last-90 vs prior-90 days). Live-backfilled from EDGAR so it works day one.

Input parameters:

- `cik` (string, required): CIK number of the company in the SEC EDGAR system

### `insider_activity` (~90 tokens)

Recent Form 4/3/5 insider transactions with insider-cluster detection (multiple insiders filing on the same issuer). Optionally filter by ticker/CIK.

Input parameters:

- `cik` (string): CIK number of the company in the SEC EDGAR system
- `days` (number): Number of days of insider activity to look back over
- `ticker` (string): Stock ticker symbol of the company

### `search_filings` (~108 tokens)

Direct live search of SEC EDGAR full-text for the latest filings of a form type in a date range. Use for ad-hoc lookups.

Input parameters:

- `end` (string): End date of the filing search range
- `form` (string): Form type, e.g. '8-K'.
- `limit` (number): Default 50, max 100.
- `q` (string): Optional full-text query.
- `start` (string): Start date of the filing search range

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/cloudcorprecords-filingpulse/reneturcios-filingpulse#diagnostics

## Score history

- 2026-11-21: 70
- 2026-11-20: 70
- 2026-11-19: 70
- 2026-11-18: 70
- 2026-11-17: 55

## Common questions

### What is the io.github.CloudCorpRecords/filingpulse MCP server?

io.github.CloudCorpRecords/filingpulse is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/filingpulse. Fresh SEC filing intel: 8-K events, Form 4 insider activity, filing search and digests. This page covers its npm package (@reneturcios/filingpulse).

### Is the io.github.CloudCorpRecords/filingpulse MCP server safe to use?

io.github.CloudCorpRecords/filingpulse scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting 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.CloudCorpRecords/filingpulse MCP server expose?

io.github.CloudCorpRecords/filingpulse exposes 5 tools: whats_new_since, filing_digest, company_watch, insider_activity, search_filings. Their descriptions and schemas cost roughly 636 tokens of context every time the server is loaded.

### Is the io.github.CloudCorpRecords/filingpulse MCP server still maintained?

io.github.CloudCorpRecords/filingpulse 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.CloudCorpRecords/filingpulse MCP server under?

io.github.CloudCorpRecords/filingpulse 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.CloudCorpRecords/filingpulse MCP server?

VerifyMCP ran 15 checks on io.github.CloudCorpRecords/filingpulse, 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 io.github.CloudCorpRecords/filingpulse: Stability. One category scores 0 for that reason, because we only credit what we can confirm. 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.

## Links

- npm package: https://www.npmjs.com/package/@reneturcios/filingpulse
- Socket report: https://socket.dev/npm/package/@reneturcios/filingpulse
- Repository: https://github.com/CloudCorpRecords/filingpulse
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-filingpulse/reneturcios-filingpulse.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-filingpulse/reneturcios-filingpulse/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/cloudcorprecords-filingpulse/reneturcios-filingpulse.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-filingpulse/reneturcios-filingpulse
