Public Company Reporting Window Finder
公開企業の決算日と連絡期間検索 MCP サーバー
Mamba Labs の 公開企業の決算日と連絡期間検索 アクター向け MCP サーバー (Apify 上)。
ドメイン、ティッカー、ISIN、LEI、CIK を指定すると、その公開企業が いつ決算を発表するか、およびその前後の連絡に適した期間を知らせます:会計年度末、報告頻度、次の報告日、イベントまでの日数、定義した連絡期間の開始と終了。
タイミング情報は米国企業のみ対象。 企業識別、取引所、業種分類は全世界の公開可能なユニバースを対象に解決します。報告日は米国 SEC の提出履歴に基づき、米国企業のみ存在します。非米国企業は完全に解決されますが、
timing_unavailable_reasonに理由が示され、推測日は返されません。また、検索が実行されたためタイミング行として課金されます。
5 つのツール(アクターモードごとに 1 つ)
ツール | 入力 | 戻り値 |
| 識別子 | 企業識別と取引所、44 フィールド |
| 識別子 | 上場ステータスの判定 |
| 識別子 | 会計年度末、頻度、次のイベント、連絡期間、75 フィールド |
| フィルター | 企業リスト |
| フィルター | 週または月単位の報告負荷 |
mode を渡す必要はありません。各ツールが自動で設定し、各ツールはそのモードが実際に使用する入力のみを公開します。
build_company_universe と get_reporting_season はフィルターからリストを構築し、企業識別子は受け付けません。両方で limit を明示的に設定してください。デフォルトは 1000 で、返された行ごとに課金されます。
Related MCP server: corporate-events-mcp
インストール
{
"mcpServers": {
"mamba-public-company-reporting-window-finder": {
"command": "npx",
"args": ["-y", "@mambalabsdev/mcp-public-company-reporting-window-finder"],
"env": { "APIFY_TOKEN": "your-apify-token" }
}
}
}トークンは console.apify.com/account/integrations で取得してください。
出力の読み方
日付は予測であり、発表ではありません。 next_event_is_estimate は、提出履歴から導出された日付の場合に true になります。confidence_band は 0.80 と 0.50 に設定され、チェーン内の最も弱いリンクに基づいて計算されるため、confidence_effective はイベント信頼度と頻度信頼度の最小値(平均ではありません)となります。
window_status はフィルタリング対象のフィールドです。 値は open、not_yet、closed_passed、no_event(本日基準)です。no_event は、報告イベントがなく連絡期間を構築できない企業の状態です。
不明な頻度は拒否され、推測されません。 提出履歴が短すぎる、または不規則な企業は、null の頻度と理由が返され、日付は創作されません。
何も解決できない行でも課金されます。 一致する公開企業がない識別子は match_method が no_match となり、他のすべてのフィールドは null になります。これも実際の回答であり、検索が実行されて生成されました。
料金
Apify でイベントごとに従量課金され、フィルタリングで除外された行ではなく、返された行に対して課金されます。
イベント | 価格 |
企業解決 | $0.006/行 |
タイミング行返却 | $0.012/行 |
報告シーズン集計 | $0.05/行 |
アクター開始 | $0.00005/実行 |
Apify のブロンズ、シルバー、ゴールドプランでは、それぞれ 5%、10%、15% のボリュームディスカウントが適用されます。タイミング行は、解決済み企業として追加で課金されることはありません。
Mamba Labs GTM スイートの一部
ライセンス
MIT
Available Tools
5 toolsbuild_company_universeBuild Company UniverseAIdempotent
Build a list of listed companies from filters rather than from identifiers you already hold. Filter by exchange, country, region, sector, security type, public float band, fiscal year end month, reporting cadence, operating status and foreign private issuer status. Returns 44 fields per company, the same shape resolve_company returns. At least one filter is required, so a bare call cannot pull the whole universe. This tool does NOT accept company identifiers: use resolve_company, qualify_company or get_reporting_timing for specific companies. SET limit EXPLICITLY. It defaults to 1000 and you are charged per company row returned, so an unbounded call is an expensive call. Truncation is always reported, never silent. Requires an APIFY_TOKEN and consumes Apify credits. Read only.
Inputs: limit, regions, sectors, cadences, +13 more.
get_reporting_seasonGet Reporting SeasonAIdempotent
Show how reporting load is distributed over time, so you can find the busy weeks and the quiet ones. Returns aggregate rows per bucket, not per company: period start and end, event count, company count, estimated share and mean confidence. Bucket by week or month with season_group_by, and optionally split by sector, country or exchange with season_split_by. The window defaults to today through 180 days out; set season_from and season_to for another. At least one filter is required and company identifiers are not accepted. Use this to plan campaign timing across a market, not to time one account; for a single company use get_reporting_timing. Narrow the population with the same filters build_company_universe takes (exchange_codes, country_codes, regions, sectors, public_float_bands, cadences). Charged per aggregate row returned, which is far fewer rows than the companies behind them. Requires an APIFY_TOKEN and consumes Apify credits. Read only.
Inputs: limit, regions, sectors, cadences, +18 more.
get_reporting_timingGet Reporting TimingAIdempotent
Find when a public company next reports, and when to reach out around it. Returns 75 fields per input: fiscal year end, derived reporting cadence and its confidence, the next reporting event with its type, period and date, days to event, and the open and close of an outreach window you define with window_lead_days and window_lag_days, which default to 70 and 42. window_status is one of open, not_yet, closed_passed or no_event and is the field to filter on. Dates are PREDICTED from filing history, not announced: read next_event_is_estimate and confidence_band, whose thresholds sit at 0.80 and 0.50. TIMING ROWS COVER US COMPANIES ONLY. A non US company resolves fully for identity and returns a stated timing_unavailable_reason rather than a guessed date, and is still charged as a timing row because the work ran. Charged per timing row returned, never additionally as a resolved company. Requires an APIFY_TOKEN and consumes Apify credits. Read only.
Inputs: ciks, leis, isins, regions, +26 more.
qualify_companyQualify CompanyAIdempotent
Answer whether a company is publicly listed. Takes the same identifiers as resolve_company and returns a listed status verdict per input. Set listed_only to keep only the companies proven to be listed, or suppress_listed to remove them, which is what you want when selling only into private companies. By default an unmatched company returns is_listed null rather than false, because a non match may mean the company is private OR that the dataset does not hold its domain; set assume_unmatched_is_private to true to opt into reading a non match as private. Use this to split a prospect list into listed and private companies before outreach; use resolve_company when you need the full identity fields. Identify companies with company_domain, company_domains, tickers, isins, leis, ciks, or company_names; every other input is an optional filter shared with resolve_company (exchange, country, region, sector, security type, float band, fiscal year end, cadence, and data quality switches). Charged per company row returned. Requires an APIFY_TOKEN and consumes Apify credits. Read only.
Inputs: ciks, leis, isins, regions, +22 more.
resolve_companyResolve CompanyAIdempotent
Resolve a domain, ticker, ISIN, LEI, CIK or company name to a listed company identity. Returns 44 fields per input: legal name, primary ticker, ISIN, LEI, CIK, domain, primary exchange, country, currency, sector, security type, public float band, shares outstanding, and the provenance of each. Every input returns exactly one row, including the ones that match nothing, which come back with match_method set to no_match and every other field null. Read matched_on to see which identifier produced the row. Use this when you hold identifiers and need the listed identity behind them; use qualify_company for a yes or no on listed status, get_reporting_timing for dates, and build_company_universe when you hold filters rather than identifiers. The filter inputs (exchange_codes, country_codes, regions, sectors, and the rest) narrow which matched rows come back. Charged per company row returned, including a no_match row, because the lookup ran either way. Requires an APIFY_TOKEN and consumes Apify credits. Read only.
Inputs: ciks, leis, isins, regions, +19 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 5 tools
Each tool has a distinct input/output contract: build_company_universe takes filters only, resolve_company takes identifiers, qualify_company returns a listed-status verdict, get_reporting_timing returns per-company timing, and get_reporting_season returns aggregate season buckets. Descriptions explicitly cross-reference when to use each alternative, making misselection unlikely.
All five names use consistent snake_case with a verb_noun structure (build_, resolve_, qualify_, get_). The only slight length variation is build_company_universe, but it follows the same convention.
Five tools are well-scoped for a read-only reporting-data server; each covers a distinct query mode and none feels redundant. The count sits comfortably in the ideal 3-15 range.
The surface covers company enumeration, identity resolution, listed-status qualification, per-company timing, and aggregate season planning, which is a coherent lifecycle for the domain. Minor gap: get_reporting_timing is US-only, so non-US timing requests dead-end with timing_unavailable_reason and no alternative tool; bulk or historical event retrieval is also absent but agents can work around via batching or aggregation.
Maintenance
Related MCP Connectors
Earnings results, outlook, KPIs and call transcripts for ~400 US, Asian and European companies.
Earnings calls, news releases, decks, prices and shareholders for listed companies worldwide.
US earnings dates, confirmed or estimated, each with its SEC EDGAR or company source URL.
Institutional-grade financial data: earnings, estimates, guidance, stock prices, macro indicators.
Related MCP Servers
- -licenseNot gradedqualityNot gradedmaintenanceEnables deep analysis of SEC EDGAR filings through universal company search, document content extraction, and advanced filing search capabilities. Provides AI-ready access to business descriptions, risk factors, financial statements, and full-text search across any public company's SEC documents.-
- FlicenseNot gradedqualityDmaintenanceNormalizes and serves corporate events (earnings, dividends, splits, M\&A) from US, UK, Canada, and Australia via a programmatic MCP API.-
- AlicenseAqualityAmaintenanceEnables users and AI agents to resolve tickers, CIKs, or company names to official SEC entity data and retrieve recent EDGAR filings, XBRL financial facts, and optional filing-text excerpts. It delivers structured, source-linked rows for research and tooling, with schema-versioned output and machine-readable error codes.7MIT
- FlicenseNot gradedqualityAmaintenanceEnables natural-language research and structured, source-backed answers across SEC filings, earnings transcripts, company financials, stock and crypto market data, and prediction markets news and research.-