# com.datasignalslab/datasignals-lab-events-mcp (pypi · datasignals-lab-events-mcp)

Twelve US filing and career-site streams in one schema: SEC, FDA, NIH, contracts, Congress, hiring

- Trust score: 42/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-20

## Components

- remote · `datasignalslab--datasignals-lab-events-mcp.apify.actor`: 34/100, [markdown](https://verifymcp.io/servers/com-datasignalslab-datasignals-lab-events-mcp/datasignalslab-datasignals-lab-events-mcp.md), [page](https://verifymcp.io/servers/com-datasignalslab-datasignals-lab-events-mcp/datasignalslab-datasignals-lab-events-mcp)
- remote · `mcp.apify.com`: 61/100, [markdown](https://verifymcp.io/servers/com-datasignalslab-datasignals-lab-events-mcp/mcp.md), [page](https://verifymcp.io/servers/com-datasignalslab-datasignals-lab-events-mcp/mcp)
- pypi · `datasignals-lab-events-mcp`: 42/100 (this document), [markdown](https://verifymcp.io/servers/com-datasignalslab-datasignals-lab-events-mcp/datasignals-lab-events-mcp.md), [page](https://verifymcp.io/servers/com-datasignalslab-datasignals-lab-events-mcp/datasignals-lab-events-mcp)

## Channel facts

- Registry: `pypi`
- Package: `datasignals-lab-events-mcp`
- Version: `1.1.1`
- 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-08-20.

- **Supply Chain Security**: 50/100
  - Malware scan not yet available for this package.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it.
  - 2 of 33 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 6/100
  - Repository check failed: no source repository is declared.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: no license is declared.
  - Actively maintained (last published 0 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 991 tokens (~141/item across 7 items; 7 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**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (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

### Claude

```bash
claude mcp add com-datasignalslab-datasignals-lab-events-mcp -- uvx datasignals-lab-events-mcp
```

### Codex

```bash
codex mcp add com-datasignalslab-datasignals-lab-events-mcp -- uvx datasignals-lab-events-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-datasignalslab-datasignals-lab-events-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "datasignals-lab-events-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-datasignalslab-datasignals-lab-events-mcp --command uvx --arg datasignals-lab-events-mcp
```

### Hermes

```yaml
mcp_servers:
  com-datasignalslab-datasignals-lab-events-mcp:
    command: "uvx"
    args: ["datasignals-lab-events-mcp"]
```

### Other

```json
{
  "mcpServers": {
    "com-datasignalslab-datasignals-lab-events-mcp": {
      "command": "uvx",
      "args": [
        "datasignals-lab-events-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-08-20 (score 42)

First indexed and scored.

## MCP tools (7)

### `search_events` (~300 tokens)

Search the feed of US filing events, newest last, with a cursor you can resume from.

All filters combine. Only records actually returned count against the
subscriber's monthly allowance, so filtering narrowly is cheaper, not dearer.

Args:
    event_type: One or more streams, comma separated. Call list_event_types
        for the valid names. Leave empty for all streams the plan covers.
    ticker: One or more tickers, comma separated, e.g. "AAPL,MSFT".
    cik: One or more SEC company identifiers, comma separated.
    min_score: Only records scoring at or above this, 0 to 100. Streams
        without a score are excluded when this is set.
    since: A cursor from an earlier answer. Returns only what arrived after
        it, with no duplicates and no gaps. Use 0 to start at the beginning.
    limit: Records per page, 1 to 1000. Keep it small unless the user asked
        for bulk; a large page spends allowance and context on rows nobody
        reads.
    full_records: Return every field instead of the trimmed view. Use only
        when the user needs a field the trimmed view leaves out.

Input parameters:

- `cik`
- `event_type`
- `full_records` (boolean)
- `limit` (integer)
- `min_score`
- `since`
- `ticker`

### `company_events` (~96 tokens)

Everything the feed holds for one company, across all twelve streams.

Args:
    company: A ticker such as "AAPL", or an SEC CIK such as "0000320193".
    limit: Records to return, 1 to 1000.
    full_records: Return every field instead of the trimmed view.

Input parameters:

- `company` (string, required)
- `full_records` (boolean)
- `limit` (integer)

### `get_event` (~63 tokens)

Fetch a single event by its event_id, with every field it carries.

Args:
    event_id: The event_id from an earlier answer, e.g.
        "insider_cluster:CAMP:2026-08-03".

Input parameters:

- `event_id` (string, required)

### `list_event_types` (~58 tokens)

List the twelve streams: which fields each carries, and whether its score can be recomputed.

Needs no API key. Call this before promising a user a field or writing a
parser, rather than assuming a stream carries something it does not.

### `feed_health` (~76 tokens)

How many hours old each of the twelve sources is right now, and how many records are anchored in the published hash chain.

Needs no API key. This is the honest answer to "is this data current?", with
numbers instead of a claim. A source that has gone quiet shows up here before
it shows up as missing data.

### `usage` (~54 tokens)

What this key has used in the current period, and the date the allowance resets.

The reset date is the subscriber's own renewal date, not the first of the
month. Free, and it does not count against the allowance.

### `check_setup` (~36 tokens)

Check whether an API key is configured and whether the feed answers.

Run this first when anything behaves oddly. It never reveals the key itself.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-datasignalslab-datasignals-lab-events-mcp/datasignals-lab-events-mcp#diagnostics

## Score history

- 2026-08-20: 42

## Links

- PyPI project: https://pypi.org/project/datasignals-lab-events-mcp/
- Socket report: https://socket.dev/pypi/package/datasignals-lab-events-mcp
- Website: https://datasignalslab.com/events-api.html
- Changelog RSS feed: https://verifymcp.io/servers/com-datasignalslab-datasignals-lab-events-mcp/datasignals-lab-events-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-datasignalslab-datasignals-lab-events-mcp/datasignals-lab-events-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-datasignalslab-datasignals-lab-events-mcp/datasignals-lab-events-mcp