mcpdirectory.dev
9,129 servers · updated 23 Sept

Public Company Reporting Window Finder MCP server

community Active last commit 22 d 
{
  "mcpServers": {
    "mamba-public-company-reporting-window-finder": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-public-company-reporting-window-finder@latest"
      ],
      "env": {
        "APIFY_TOKEN": "<apify_token>"
      }
    }
  }
}
file .mcp.json (in your project root)install npx -y @mambalabsdev/mcp-public-company-reporting-window-finderversion 1.0.0

What it does

This server finds when public companies report their earnings, including fiscal year end, reporting cadence, next reporting date, and outreach windows. It resolves company identities across multiple identifier types and provides reporting season aggregates. Timing data covers US companies only, while identity resolution works globally.

  • Look up a company by ticker, domain, ISIN, LEI or CIK to find its next earnings date and when to contact stakeholders around the reporting window.
  • Build a filtered list of public companies and see their reporting schedule aggregated by week or month to plan outreach campaigns.
  • Check whether a company is currently within an open outreach window, recently closed one, or has no upcoming reporting event.

Tools this server exposes

ToolDoes
resolve_companyTakes company identifiers and returns 44 fields of identity and venue information.
qualify_companyTakes company identifiers and returns a listed status verdict.
get_reporting_timingTakes company identifiers and returns 75 fields including fiscal year end, cadence, next event date, and outreach window details.
build_company_universeTakes filters to build and return a list of companies; does not accept individual company identifiers.
get_reporting_seasonTakes filters and returns reporting load aggregated by week or month; does not accept individual company identifiers.

Before you enable it

An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.