EarningsWatcher
com.earnings-watcherPublished by earnings-watcher.comv1.0.1Updated Oct 24, 2026
Options-implied earnings moves, 10y implied-vs-actual history, IV rush/crush, scanner, simulator.
Overview
A remote MCP server for options-implied earnings moves, implied-versus-actual history, IV rush/crush, scanning and simulation.
- What you can do
- EarningsWatcher exposes options-implied earnings moves together with a ten-year history comparing implied moves against actual outcomes. It also covers implied-volatility rush and crush around earnings, plus a scanner and a simulator. The manifest lists no individual tools, so the exact tool names and parameters are not documented here.
- When to use it
- Worth adding when an assistant needs to reason about expected earnings moves, compare implied expectations with past actual moves, or study volatility behaviour around earnings dates. Less useful for general market data or non-earnings research.
- Requirements
- A remote streamable HTTP endpoint at the provider's hosted address; no local runtime or package is needed. Authentication is OAuth and is required, so the user must complete an OAuth sign-in. No environment variables or headers are declared.
Installation
In SourceWeft
- Open EarningsWatcher in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.earnings-watcher%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"earningswatcher": {
"type": "http",
"url": "https://earnings-watcher-mcp-611514391657.us-central1.run.app/mcp"
}
}
}Tools
0Version history
2- v1.0.1LatestSep 29, 2026
- v1.0.0Sep 16, 2026
Score
67% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.