io.github.benjamin-di/earnings-watch
PYPI · EARNINGS-WATCH
Verified issuer earnings calendars and results documents
Available components
Last scanned (3 hours ago)
Scores higher than 60% of PyPI servers
Category Finance and Payments
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 build step with no custom scripting around it. View diagnostics → Pass
- 1 of 29 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to benjamin-di/earnings-watch). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability59
- 75% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 443 tokens (~40/item across 11 items; 10 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 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
- 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 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
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.
- 5 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 4 Nov 26 +1
- Package version: 0.3.1 → 0.3.3 functional
- 2 Nov 26 +28
- Injection markers: unverified → pass ▲ security
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.10 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → 75 ▲ functional
- Package version: 0.2.1 → 0.3.1 functional
- 1 Nov 26 −1
- Stability: 0.03 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Provenance: fail → pass ▲ security
- The attested source repository moved: benjamin-di/earnings-watch security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 75 → unverified ▼ functional
- Package version: 0.2.1 → 0.3.1 functional
- Package version: 0.2.1 → 0.2.2 functional
- 31 Oct 26 0
- Malware scan: unverified → pass ▲ security
- Stability: unverified → 0.03 ▲ functional
- Package version: 0.1.0 → 0.2.1 functional
- 30 Oct 26 51
First indexed and scored.
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 5 Nov 2026 · Analysed pypi/earnings-watch@0.3.3
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | benjamin-di/earnings-watch |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/benjamin-di/earnings-watch/.github/workflows/release.yml@refs/tags/v0.3.3 |
| Rekor log index | 3686456145 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:5743383ba060f53631e94101bcdd9607eaad24647a6a29c70e5ff88a84016447 |
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 29 packages
| Packages resolved | 29 |
|---|---|
| Stale | 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 →
earnings_calendar_ack Earnings Calendar Ack ~37
R1. Record confirmed external operations; reject stale or altered plans.
| Name | Type | Req | Description |
|---|---|---|---|
| handle | string | yes | – |
| results | array | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
earnings_calendar_plan Earnings Calendar Plan ~44
R0. Plan optional Outlook operations. Apply through your external Outlook app.
| Name | Type | Req | Description |
|---|---|---|---|
| event_ids | – | – | – |
| full | boolean | – | – |
| sink | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
earnings_changes Earnings Changes ~37
R0. Read the shared change feed; keep the returned cursor for next time.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | – | – | – |
| limit | integer | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
earnings_documents Earnings Documents ~57
R0. List official result-document links and their verification status.
| Name | Type | Req | Description |
|---|---|---|---|
| event_ids | – | – | – |
| limit | integer | – | – |
| roles | – | – | – |
| scope | string | – | – |
| since | – | – | – |
| tickers | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
earnings_get_events Earnings Get Events ~32
R0. Read up to 20 public events with evidence and bounded history.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | array | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
earnings_status Earnings Status ~21
R0. Read catalogue counts and maintenance status without model calls.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
earnings_unwatch Earnings Unwatch ~34
R1. Remove your manual follow; public history is retained.
| Name | Type | Req | Description |
|---|---|---|---|
| exchange | – | – | – |
| ticker | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
earnings_upcoming Earnings Upcoming ~59
R0. List upcoming verified dates, including explicit timing uncertainty.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | – | – | – |
| days | integer | – | – |
| limit | integer | – | – |
| scope | string | – | – |
| tickers | – | – | – |
| types | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
earnings_watch Earnings Watch ~45
R1. Follow an issuer for yourself; ambiguous tickers return candidates.
| Name | Type | Req | Description |
|---|---|---|---|
| exchange | – | – | – |
| isin | – | – | – |
| name | – | – | – |
| ticker | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
earnings_watchlist Earnings Watchlist ~20
R0. Read your follows and pending registration states.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the io.github.benjamin-di/earnings-watch MCP server?
io.github.benjamin-di/earnings-watch runs locally as a PyPI package, launched with uvx earnings-watch. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · earnings-watch
claude mcp add benjamin-di-earnings-watch -- uvx earnings-watch
What is the io.github.benjamin-di/earnings-watch MCP server?
io.github.benjamin-di/earnings-watch is an MCP server listed in the public MCP registry as io.github.benjamin-di/earnings-watch. Verified issuer earnings calendars and results documents. This page covers its PyPI package (earnings-watch).
Is the io.github.benjamin-di/earnings-watch MCP server safe to use?
io.github.benjamin-di/earnings-watch scores 64 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. 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.benjamin-di/earnings-watch MCP server expose?
io.github.benjamin-di/earnings-watch exposes 10 tools: earnings_upcoming, earnings_get_events, earnings_documents, earnings_changes, earnings_watchlist, and 5 more. Their descriptions and schemas cost roughly 386 tokens of context every time the server is loaded.
Is the io.github.benjamin-di/earnings-watch MCP server still maintained?
io.github.benjamin-di/earnings-watch is still listed as active in the MCP registry. We last reached this channel on 5 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.benjamin-di/earnings-watch MCP server under?
io.github.benjamin-di/earnings-watch declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.