Skip to main content
Glama
Funding & Press Signal Scanner MCP Server

Funding & Press Signal Scanner MCP Server

Funding & Press Signal Scanner MCP Server

Glama score MCP Registry npm version npm downloads license mcpservers.org

Give it a company domain, get back a clean list of that company's recent business events: funding rounds, executive moves, product launches, acquisitions, partnerships, and IPOs. The actor searches public news and press sources, classifies each story into a typed event, deduplicates the same event reported across multiple outlets, and returns one flat row per company. Built for Clay users, RevOps teams, and outbound agencies who want account signals without paying for a Crunchbase seat. It wraps the Mamba Labs Funding and Press Signal Scanner actor on Apify.

What's Inside

Related MCP server: mcp-gtm-signals-aggregator

What it does

This server gives an AI client one tool:

  • get_funding_press_signals: scan Google News and PR wires for a company's funding rounds, executive moves, product launches, acquisitions, partnerships, and IPOs. Returns deduplicated, dated events in flat, Clay-ready JSON, one row per company, with a per company summary (has_recent_funding, funding_total_estimated, latest_event_date, most_recent_event_type) and an events array where each event carries its type, date, amount, funding stage, source URL, and a corroborating source count.

All of the work runs on Apify. This package is a thin client that routes the tool call to the actor and hands back the result.

Quick start

You need Node.js 18 or newer and an Apify account with an API token.

Add this to your Claude Desktop config:

{
  "mcpServers": {
    "funding-press-signal-scanner": {
      "command": "npx",
      "args": ["-y", "@mambalabsdev/mcp-funding-press-signal-scanner"],
      "env": {
        "APIFY_TOKEN": "your-apify-token"
      }
    }
  }
}

Get your token at https://console.apify.com/account/integrations, paste it in, and restart Claude Desktop. The tool will be available.

Prerequisites

  • Node.js 18 or newer

  • An Apify account with an API token

Example prompts

  • "What funding, exec moves, and product launches has stripe.com had recently?"

  • "Has ramp.com raised any funding in the last year, and how much?"

  • "Scan deel.com (company name Deel) for acquisitions and partnerships."

  • "Show me the most recent press events for notion.so as flat JSON."

  • "Scan stripe.com, ramp.com, and deel.com for funding rounds in the last 90 days."

Tool and inputs

get_funding_press_signals:

  • domain (string, required): company domain to scan, without https or www, e.g. stripe.com.

  • company_name (string, optional): company name hint, used when the domain does not match the brand name, e.g. Deel for deel.com.

  • signal_types (array, optional): report only these event types: funding_round, ipo, acquisition, exec_move, product_launch, partnership. Narrowing narrows the search as well as the answer. Omit for every type.

  • lookback_days (integer, optional): how far back to search, in days. Default 365.

  • domains (array, optional): a list of company domains scanned in one run, one row per company. When set and non-empty it overrides domain (still required by the schema, so pass the first domain there too).

  • max_charge_usd (optional): a cost cap in USD for this run. The actor stops before an item that could take its charges past this amount. Omit it to rely on the maximum cost per run set in Apify.

The output is one row per company: company_domain, company_name, total_events, latest_event_date, has_recent_funding, funding_total_estimated, funding_total_currency, most_recent_event_type, most_recent_headline, an events array of typed events, a sources_queried array, and run_date. Each event in the array has event_type (funding_round, exec_move, product_launch, acquisition, partnership, ipo), date, headline, source_url, source_name, amount, currency, funding_stage, names, description, and corroborating_source_count.

Pricing

Price per event on the Apify FREE plan, from the live pricing record; paid Apify plans pay less per event.

Event

Price (USD)

Actor Start (apify-actor-start)

0.00005

result (apify-default-dataset-item)

0.03

Full actor documentation

For the complete input and output reference, pricing, and run history, see the Funding & Press Signal Scanner actor on the Apify Store:

https://apify.com/mambalabs/funding-press-signal-scanner


Mamba Labs GTM Suite

This server is one of 103 Mamba Labs MCP servers, each a thin client for one Mamba Labs actor on Apify. Every actor returns flat, Clay-ready rows that join on the company domain.

Built by Mamba Labs | npm | Apify Store

License

MIT

Built by Mamba Labs. https://apify.com/mambalabs

Available Tools

1 tool
get_funding_press_signalsGet Funding and Press SignalsA
Read-onlyIdempotent

Scan Google News and PR wires for funding rounds, executive moves, product launches, and acquisitions at any company domain. Returns deduplicated, dated events in flat Clay-ready JSON. Use it to find a trigger for outbound (a fresh raise, a new executive) or to qualify an account before a call. Pass signal_types to report one kind of event, lookback_days to set the window, and domains to scan a list in one call. Requires APIFY_TOKEN; consumes Apify credits.

Inputs: domain (required), domains, company_name, signal_types, +1 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.4/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only a single tool in the set, there is no possibility of overlap or misselection. The tool's purpose—scanning for funding and press signals—is unambiguous and self-contained.

    Naming Consistency5/5

    The lone name get_funding_press_signals follows a clear verb_noun pattern and is descriptive of its function. There are no competing conventions to conflict with it.

    Tool Count3/5

    A single tool is on the thin side for a server, even though this one is parameter-rich (signal_types, lookback_days, domains) and covers several event categories. It works, but the surface feels narrow for the stated scanning domain.

    Completeness4/5

    For a read-only signal scanner the core need—retrieving deduplicated, dated funding, exec, launch, and acquisition events—is covered with configurable filters. Minor gaps exist (no save/export, alerting, or targeting helpers), but the primary workflow is complete.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers