BounceWatch Signal Intelligence
Server Details
Millions of dated buying and momentum signals: who raised, who's hiring, what changed and when
Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 10.3% over 39 days
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP
- URL
TDQS
Scored across 10 tools
Each tool has a clearly distinct purpose: find_company resolves names to domains, get_company returns profiles, get_company_signals gives per-company timelines, search_companies filters by firmographics, search_signals queries the whole index by events, and check_watches is scoped to the user's watchlist. Cross-references in the descriptions eliminate ambiguity.
All tool names follow a consistent verb_noun pattern (check_watches, find_company, get_company, search_signals, watch_company, etc.) with no camelCase or irregular verbs. The naming is uniform and predictable.
The 10 tools cover the full lifecycle of a signal intelligence service: discovery, retrieval, refresh, watch management, and taxonomy. Each tool has a distinct role and none feel redundant or excessive for the stated purpose.
The toolset covers create (refresh_company adds new domains), read (get_company, get_company_signals), update (watch_company can modify filters), and delete (watch_company with stop:true). Search capabilities, watchlist management, refresh polling, and taxonomy lookup are all present, leaving no major workflow gaps.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
2 tool updates
- Changed
get_refresh_status1 field changed- changed
Input schema / properties / wait_seconds / descriptionPrevious value: -"How long this call may block waiting for the scan, 0-25. Default 20. Returns the moment the scan finishes; still free."New value: +"How long this call may block waiting for the scan, 0-25. Default 20. It returns the moment the scan finishes, and waiting the full 25 costs exactly what waiting 1 costs — so there is nothing to gain by polling with a low value."
- Changed
search_signals1 field changed- changed
Input schema / properties / days / descriptionPrevious value: -"Lookback window in days. Default 30. Max 365 when you filter by signal_keys or categories, 90 without a filter. Shorter windows mean sharper timing."New value: +"Lookback window in days. Default 30. Max 365. Shorter windows mean sharper timing."
2 tool updates
- Changed
search_companies2 fields changed- changed
Input schema / properties / founded_after / descriptionPrevious value: -"Only companies founded in or after this year, e.g. 2023. Companies whose founding year we do not hold are excluded when this is set — about 6% of the set we observe. The result says so."New value: +"Only companies founded in or after this year, e.g. 2023. Companies whose founding year we do not hold are excluded when this is set, and the result says so." - changed
Input schema / properties / funding_stage / descriptionPrevious value: -"Funding stage, e.g. \"Seed\", \"Series A\", \"Pre Seed\". Spacing, case and hyphens are normalised; a value that matches nothing is rejected with the valid list rather than returning a near-empty result. This is the costliest filter here: we hold a stage for only about 60% of the companies we observe, and the rest are excluded rather than guessed at — so it narrows the field twice, once by stage and once by what we know."New value: +"Funding stage, e.g. \"Seed\", \"Series A\", \"Pre Seed\". Spacing, case and hyphens are normalised; a value that matches nothing is rejected with the valid list rather than returning a near-empty result. This is the costliest filter here: a company whose stage we do not hold is excluded rather than guessed at, so it narrows the field twice — once by stage, once by what we know."
- Changed
search_signals3 fields changed- changed
Input schema / properties / founded_after / descriptionPrevious value: -"Only companies founded in or after this year, e.g. 2023. Companies whose founding year we do not hold are excluded when this is set — about 6% of the set we observe. The result says so."New value: +"Only companies founded in or after this year, e.g. 2023. Companies whose founding year we do not hold are excluded when this is set, and the result says so." - changed
Input schema / properties / funding_stage / descriptionPrevious value: -"Funding stage, e.g. \"Seed\", \"Series A\", \"Pre Seed\". Spacing, case and hyphens are normalised; a value that matches nothing is rejected with the valid list rather than returning a near-empty result. This is the costliest filter here: we hold a stage for only about 60% of the companies we observe, and the rest are excluded rather than guessed at — so it narrows the field twice, once by stage and once by what we know."New value: +"Funding stage, e.g. \"Seed\", \"Series A\", \"Pre Seed\". Spacing, case and hyphens are normalised; a value that matches nothing is rejected with the valid list rather than returning a near-empty result. This is the costliest filter here: a company whose stage we do not hold is excluded rather than guessed at, so it narrows the field twice — once by stage, once by what we know." - changed
Input schema / properties / min_weight / descriptionPrevious value: -"Only count signals worth at least this much, 1-10. Background chatter (event attendance, news mentions, follower drift) sits at 1-2 and is a third of everything we hold; 3 or 4 searches on substance and is the useful setting. Above 7 you are asking for rare events — funding, acquisitions, shutdowns are under 1% of what happens in any window, because that is how often they happen, not how well we see them. Searching for those usually returns little; watch_company is how you catch them. Default 0 (everything)."New value: +"Only count signals worth at least this much, 1-10. Background chatter (event attendance, news mentions, follower drift) sits at 1-2 and dominates an unfiltered result; 3 or 4 searches on substance and is the useful setting. Above 7 you are asking for rare events — funding, acquisitions, shutdowns are seldom what a window contains, because that is how often they happen, not how well we see them. Searching for those usually returns little; watch_company is how you catch them. Default 0 (everything)."
10 tool updates
- First observed
check_watches - First observed
find_company - First observed
get_company - First observed
get_company_signals - First observed
get_refresh_status - First observed
get_signal_taxonomy - First observed
refresh_company - First observed
search_companies - First observed
search_signals - First observed
watch_company
Related MCP Connectors
1000+ actively deploying VC funds and 415 disclosed LPs, with live investor signals
Private company data, entity-resolved news, targeted lists, and alternative signals for AI agents.
Company and market intelligence, news, enrichment, and agentic workflows for dealmakers.
Curated & traceable AI venture data: verified funding events, org & founder profiles, US + China
Related MCP Servers
AlicenseAqualityAmaintenanceTracks buying and momentum signals for companies, such as funding rounds, senior hires, office openings, customer wins, and partnerships, with each event carrying its date.1011 npmMIT- FlicenseNot gradedqualityBmaintenanceEnables sales agents to retrieve dated funding and SEC 8-K event evidence for companies, with source document links, to identify timely buying signals.-
- AlicenseAqualityCmaintenanceProvides 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.759 npm3MIT
- FlicenseNot gradedqualityCmaintenanceGive your AI agent 4 sales-timing tools: detect funding events, buying-signal hires, competitor pricing changes, and buying-intent Reddit posts. Know when to reach out, not just who.-
Glama MCP Gateway
Add one secure layer between your agents and this server.