Skip to main content
Glama
mambalabsdev

Funding & Press Signal Scanner MCP Server

Funding & Press Signal Scanner MCP Server

Smithery 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.

What's Inside

Related MCP server: FundzWatch MCP Server

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."

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.

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.

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 (canonical immutable Actor ID URL):

https://apify.com/mambalabs/FS13X6dhQVgX3XOM6


Mamba Labs GTM Suite

This server is part of the Mamba Labs GTM Suite, a fleet of twelve specialized MCP servers for go-to-market signal intelligence, each backed by a dedicated Apify actor.

Actor

Immutable Actor ID

GTM Hiring Signal Scraper

D7O1SA2EqwHGsGr1P

GTM Tech Stack Signal Enrichment

qyd7nNyqFPelQViBx

GTM Signals Aggregator

xKdRfnfFNkdMpFuNs

Job Board Keyword Signal Scanner

4DvqpvhMR74NLcDDY

Domain to LinkedIn URL Resolver

3HtnSaqPHOg1Qg5gx

ICP Fit Scorer

W161DT8W4kW55dMFh

Domain Deliverability Checker

0tVgxI7A6o9jMlxmc

Company Firmographic Enricher

YlUtLWjfPpqykmB8g

Company Social Presence Mapper

4k6CCemkgBDz18m2h

Company Identity Resolver

lr8fTRAmZCBZmuwwh

Company Change-Event Feed

oX44rS0fkEJ3rXLWe

Funding & Press Signal Scanner

FS13X6dhQVgX3XOM6

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. Read-only; requires APIFY_TOKEN; consumes Apify credits.

ParametersJSON Schema
NameRequiredDescriptionDefault
domainYesCompany domain to scan, without https or www, e.g. stripe.com.
company_nameNoOptional company name hint, used when the domain does not match the brand name, e.g. Deel for deel.com.

TDQS

A4.5/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description adds behavioral traits beyond annotations: it states 'Read-only' (matching readOnlyHint), 'requires APIFY_TOKEN', 'consumes Apify credits', and that results are 'deduplicated, dated events'. These go beyond the annotation hints, providing useful operational context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences with no wasted words. It front-loads the purpose and then adds key details (output format, read-only, requirements). Every sentence adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the low complexity, complete schema/annotation coverage, and no output schema, the description fully covers input, output, and constraints. It explains what data is returned, how it's formatted, and what infrastructure is needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, and the description adds extra meaning: for 'domain' it specifies 'without https or www' and gives an example; for 'company_name' it explains it is optional and used when domain does not match brand, with an example. This enhances understanding beyond the schema definitions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool scans Google News and PR wires for specific signals (funding rounds, executive moves, etc.) and returns deduplicated, dated events in a flat JSON format. The verb 'scan' and the resource 'news/PR wires' are specific, and there are no sibling tools to differentiate.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the tool is used when needing to find funding/press signals for a company domain. It also mentions prerequisites (APIFY_TOKEN, credit consumption) but does not explicitly state when not to use it or provide alternatives. The context is clear enough for straightforward selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

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

  1. 1 tool updatev1.0.0
    • First observedget_funding_press_signals

TDQS

A4.7/5.0

Scored across 1 tool

Disambiguation5/5

Only one tool exists, so there is no possibility of confusion between tools.

Naming Consistency5/5

A single tool name follows a clear and consistent pattern, with no other tools to cause inconsistency.

Tool Count5/5

The single tool adequately covers the server's stated purpose of scanning for funding and press signals, making the count appropriate.

Completeness5/5

The tool covers all major signal types (funding, executive moves, launches, acquisitions) and returns deduplicated, dated events, satisfying the domain requirements.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Related MCP Connectors

Related MCP Servers

  • -
    license
    Not graded
    quality
    Not graded
    maintenance
    Enables 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.
    -
  • A
    license
    A
    quality
    C
    maintenance
    Provides real-time business event intelligence and AI-scored sales leads to help users track funding rounds, acquisitions, and executive hires. It enables AI agents to generate strategic market briefs and manage company watchlists for predictive business insights.
    7
    233 npm
    2
    MIT