get_funding_press_signalsLABSCO SUMMARY
The corroborating source count is what makes the output usable.
News scraping usually fails in one of two ways: the same round appears five times, or a single blog post is presented with the same weight as a Reuters story. Collapsing duplicates into one event with a corroboration count fixes both at once — you see how widely a claim was reported, which is the closest thing to a confidence signal a press scan can offer. Narrowing the event types is worth doing for its own sake: it narrows the search, not just the answer.
What it is
A one-tool MCP server that scans public news and PR wires for a company's business events. It classifies each story into a typed event, deduplicates the same event reported by several outlets, and returns one flat row per company — the account-signal work you would otherwise pay a database subscription for.
What you get
- A company's recent business events from Google News and PR wires, typed and dated —
get_funding_press_signals - Six event types you can narrow to, which narrows the search as well as the answer:
funding_round,ipo,acquisition,exec_move,product_launch,partnership - A per-company summary that answers the common question directly:
has_recent_funding,funding_total_estimated,latest_event_date,most_recent_event_type,most_recent_headline - An events array where each entry carries its type, date, headline, source URL and source name, amount, currency, funding stage, the names involved, a description, and a corroborating source count
- Deduplication across outlets, so one funding round reported five times is one event with five corroborations rather than five events
- A lookback window in days, defaulting to 365, and a company name hint for domains that do not match the brand
Requirements
An Apify account with an API token, passed as APIFY_TOKEN — the scan runs as an Apify actor and this package is a thin client routing the call, so cost follows Apify's model. Node.js 18 or newer. Launch with npx -y @mambalabsdev/mcp-funding-press-signal-scanner; the package is @mambalabsdev/mcp-funding-press-signal-scanner (1.1.0) over stdio.
Setup effort
One command plus a key — npx -y @mambalabsdev/mcp-funding-press-signal-scanner, then supply credentials
USE CASES
01
Checking whether an account just raised
Ask for the company's signals and read the funding summary fields rather than searching the news yourself.
02
Timing outreach to a change at the top
Narrow to exec moves over a recent window, which is the event that most often opens a door.
03
Judging how solid a claim is
Read the corroborating source count on the event instead of taking the first headline at face value.
04
Building an account list without a data subscription
Run the scan per domain and take the flat JSON into your table, which is what the output shape was designed for.
05
Looking further back than a year
Raise the lookback days past the default when you need the full history of a company rather than its recent activity.
1 tool
Listed in project docs. Your client may show a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool named in the project's documentation.
Requires
- npx on PATH
- Node.js 18 or later
- APIFY_TOKEN in your environment
Where it runs
Both documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y @mambalabsdev/mcp-funding-press-signal-scannerMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"funding-press-signal-scanner": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-funding-press-signal-scanner"
],
"env": {
"APIFY_TOKEN": "<YOUR_APIFY_TOKEN>"
}
}
}
}Any MCP client
ANY MCP CLIENT · JSON
{
"mcpServers": {
"mamba-funding-press-signal-scanner": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-funding-press-signal-scanner"
],
"env": {
"APIFY_TOKEN": "<YOUR_APIFY_TOKEN>"
}
}
}
}
