com.datasignalslab/datasignals-lab-events-mcp
PYPI · DATASIGNALS-LAB-EVENTS-MCP · 3 COMPONENTS · SCANNED SEP 14
Twelve US filing and career-site streams in one schema: SEC, FDA, NIH, contracts, Congress, hiring
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 Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 1 of 32 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency6
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 24 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the com.datasignalslab/datasignals-lab-events-mcp server?
com.datasignalslab/datasignals-lab-events-mcp runs locally as a PyPI package, launched with uvx datasignals-lab-events-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · datasignals-lab-events-mcp
claude mcp add com-datasignalslab-datasignals-lab-events-mcp -- uvx datasignals-lab-events-mcp
{
"mcpServers": {
"com-datasignalslab-datasignals-lab-events-mcp": {
"command": "uvx",
"args": [
"datasignals-lab-events-mcp"
]
}
}
} {
"servers": {
"com-datasignalslab-datasignals-lab-events-mcp": {
"command": "uvx",
"args": [
"datasignals-lab-events-mcp"
]
}
}
} codex mcp add com-datasignalslab-datasignals-lab-events-mcp -- uvx datasignals-lab-events-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-datasignalslab-datasignals-lab-events-mcp": {
"type": "local",
"command": [
"uvx",
"datasignals-lab-events-mcp"
],
"enabled": true
}
}
} openclaw mcp add com-datasignalslab-datasignals-lab-events-mcp --command uvx --arg datasignals-lab-events-mcp
mcp_servers:
com-datasignalslab-datasignals-lab-events-mcp:
command: "uvx"
args: ["datasignals-lab-events-mcp"] {
"McpServers": {
"com-datasignalslab-datasignals-lab-events-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"datasignals-lab-events-mcp"
]
}
}
} assistant mcp add com-datasignalslab-datasignals-lab-events-mcp -t stdio -c uvx -a datasignals-lab-events-mcp
{
"mcpServers": {
"com-datasignalslab-datasignals-lab-events-mcp": {
"command": "uvx",
"args": [
"datasignals-lab-events-mcp"
]
}
}
} 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.
- 14 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 13 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.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
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 14 Sept 2026 · Analysed pypi/datasignals-lab-events-mcp@1.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 32 packages
| Packages resolved | 32 |
|---|---|
| No linked repository | 1 |
| 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 →
check_setup ~36
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
company_events ~96
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.
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | yes | – |
| full_records | boolean | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
feed_health ~76
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_event ~63
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".
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | string | yes | – |
No output schema declared.
No examples provided.
list_event_types ~58
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_events ~300
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cik | – | – | – |
| event_type | – | – | – |
| full_records | boolean | – | – |
| limit | integer | – | – |
| min_score | – | – | – |
| since | – | – | – |
| ticker | – | – | – |
No output schema declared.
No examples provided.
usage ~54
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the com.datasignalslab/datasignals-lab-events-mcp server?
com.datasignalslab/datasignals-lab-events-mcp is listed in the public MCP registry as com.datasignalslab/datasignals-lab-events-mcp. Twelve US filing and career-site streams in one schema: SEC, FDA, NIH, contracts, Congress, hiring. This page covers its PyPI package (datasignals-lab-events-mcp).
Is the com.datasignalslab/datasignals-lab-events-mcp server safe to use?
com.datasignalslab/datasignals-lab-events-mcp scores 56 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 14 September 2026. 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 com.datasignalslab/datasignals-lab-events-mcp server expose?
com.datasignalslab/datasignals-lab-events-mcp exposes 7 tools: search_events, company_events, get_event, list_event_types, feed_health, and 2 more. Their descriptions and schemas cost roughly 683 tokens of context every time the server is loaded.
Is the com.datasignalslab/datasignals-lab-events-mcp server still maintained?
com.datasignalslab/datasignals-lab-events-mcp is still listed as active in the MCP registry. We last reached this channel on 14 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.