EarningsCalls.dev

io.github.stockmarketscanPublished by GitHub account stockmarketscanv0.2.1Updated Nov 2, 2026

177,000+ earnings call transcripts for AI - speaker segments & full-text search.

The publisher's own server: StockMarketScan

VerifiedStreamable HTTPWeb executableFinanceKnowledge & Memory

Overview

AI-generated overview

Gives an assistant read access to 177,000+ earnings call transcripts, with company lookup, speaker segments and full-text search.

What you can do
  • Check dataset coverage and browse companies, sectors and industries
  • List latest, recent or upcoming earnings calls, or all calls for a ticker
  • Fetch call metadata and full, summary or component transcript text
  • Read speaker segments filtered by role such as Executive or Analyst
  • Run full-text search across all transcripts or within a single ticker
When to use it
Useful when you want to ask natural-language questions about earnings calls, compare management commentary across quarters, or find companies that mentioned a topic in their calls, without building your own transcript pipeline.
Requirements
A paid EarningsCalls subscription (Pro, Ultra or Enterprise); the free test key does not work. Remote use needs a connector URL or an X-API-Key header. Local stdio mode needs Node.js 18+ and the EARNINGSCALLS_API_KEY environment variable.
Before you install
The API key (EARNINGSCALLS_API_KEY or X-API-Key) is a paid credential and should be kept out of shared configs; connector URLs embed a token and should be generated per device and revoked when no longer needed. Queries and search terms are sent to the third-party EarningsCalls.dev API. Access is read-only and requires an ongoing paid plan.

Installation

In SourceWeft

  1. Open EarningsCalls.dev in the dashboard and add it to a workspace.
  2. Connect X-API-Key credentials. They are stored privately and never shown on public pages.
  3. 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/io.github.stockmarketscan%2Fearningscalls-mcp/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.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "earningscalls-dev": {
      "type": "http",
      "url": "https://mcp.earningscalls.dev/mcp",
      "headers": {
        "X-API-Key": "<YOUR_API_KEY>"
      }
    }
  }
}

README

EarningsCalls MCP Server

Website · MCP setup guide · API docs · License: MIT

Model Context Protocol server that gives AI agents direct access to the EarningsCalls.dev dataset — 177,000+ earnings call transcripts from 17,000+ companies across 70 countries and 170+ exchanges (2020 to present), with 11M+ speaker segments cleanly tagged by role (Executive / Analyst / Operator / Attendee / Shareholder), full-text search, and more.

Ask Claude (or any MCP-capable client) about any earnings call in natural language:

"What did NVIDIA's CFO say about data center growth in their last call?" "Compare Tesla's gross-margin commentary across the last four quarters." "Find S&P 500 companies that mentioned 'tariffs' in their Q2 2026 calls."

Built as a thin MCP wrapper around the public REST API at https://earningscalls.dev/api/v1. New calls land within minutes of the call ending.


Requirements

  • A paid EarningsCalls subscription (Pro, Ultra, or Enterprise). The free test key does not work here — grab a plan at earningscalls.dev/#pricing (from $24.99/month).
  • For the local method only: Node.js 18+.

Installation

Two remote options (zero install, recommended) and one local option.

Option A — Connector URL (recommended)

The easiest path: a personal connector URL with the token embedded, so there's no API-key header to manage.

  1. Go to earningscalls.dev/dashboard → Connectors → Generate.
  2. Copy the URL — it looks like https://earningscalls.dev/u/<your-token>/mcp.

Claude Desktop / claude.ai (web): Settings → Connectors → Add custom connector → paste the URL → Add. (On the web, leave the OAuth fields empty and confirm the consent popup.)

Claude Code (CLI):

bash
claude mcp add --transport http earningscalls "https://earningscalls.dev/u/<your-token>/mcp"# add --scope user to make it available in every project

Cursor — .cursor/mcp.json:

json
{  "mcpServers": {    "earningscalls": {      "url": "https://earningscalls.dev/u/<your-token>/mcp"    }  }}

Each connector URL is independently revocable — generate one per device or workspace.

Option B — API-key header

Point your client at the hosted endpoint and pass your API key (ect_...) via the X-API-Key header.

Claude Code (CLI):

bash
claude mcp add earningscalls --transport http https://mcp.earningscalls.dev/mcp \  --header "X-API-Key: ect_your_key_here"

Claude Desktop / Cursor — config:

json
{  "mcpServers": {    "earningscalls": {      "url": "https://mcp.earningscalls.dev/mcp",      "headers": { "X-API-Key": "ect_your_key_here" }    }  }}

Option C — Local (via npx)

Runs the server as a local process over stdio.

bash
claude mcp add earningscalls \  --env EARNINGSCALLS_API_KEY=ect_your_key_here \  -- npx -y @earningscalls/mcp-server

Or in a client config:

json
{  "mcpServers": {    "earningscalls": {      "command": "npx",      "args": ["-y", "@earningscalls/mcp-server"],      "env": { "EARNINGSCALLS_API_KEY": "ect_your_key_here" }    }  }}

Coverage

Earnings call transcripts177,000+
Companies17,000+
Countries / exchanges70 / 170+
History2020 – present (5+ years)
Speaker segments11M+ (Executive / Analyst / Operator / Attendee / Shareholder)
SectorsAll 11 GICS sectors
FreshnessNew calls within minutes of the call ending

Available Tools

ToolDescription
get_dataset_statsTotal counts and date range — call first to understand coverage.
list_latest_callsMost recent calls, optionally filtered by sector.
list_recent_transcriptsRecently added transcripts.
list_calls_by_tickerAll calls for a ticker (e.g. PLTR, AAPL), newest first.
get_latest_call_for_tickerSingle most recent call for a ticker.
get_company_by_nameLook up a company by full/partial name.
list_companiesBrowse / search companies.
list_upcoming_earningsScheduled calls in the next N days.
get_earnings_callMetadata for a single call.
get_transcriptFull text of a call — format full, summary, or components.
get_speaker_segmentsSpeaker segments with role filter (Executive / Analyst / Operator …).
search_transcriptsFull-text search across all transcripts and speaker segments.
search_within_tickerFull-text search scoped to one ticker.
list_sectors / list_industriesDiscover filter dimensions.

Environment Variables

Local mode (stdio)

VariableRequiredDefault
EARNINGSCALLS_API_KEYyes—
EARNINGSCALLS_BASE_URLnohttps://earningscalls.dev

Remote mode (HTTP)

VariableRequiredDefault
PORTno3000
EARNINGSCALLS_BASE_URLnohttps://earningscalls.dev

In remote mode the API key is provided per session by the connecting client — either embedded in the connector URL (Option A) or via the X-API-Key header (Option B).


Development

bash
npm installnpm run build
npm start    # local stdio modenpm run serve # remote HTTP mode

Source layout:

src/├── index.ts      # stdio entry + preflight (local mode)├── http.ts       # Streamable HTTP entry (remote mode)├── client.ts     # HTTP client for earningscalls.dev API├── config.ts     # env var loading├── messages.ts   # user-facing banners + error hints└── tools.ts      # MCP tool definitions

License

MIT

Source: README.md at commit 761fcc7

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v0.2.1LatestSep 16, 2026

Score

75% 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
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Stockmarketscan integrations