Funding & Press Signal Scanner MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_funding_press_signalsA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
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.
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.
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.
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.