Connect BounceWatch Signal Intelligence and your agent gets 10 tools, among them check_watches, find_company, get_company. It answers at https://api.bouncewatch.com/api/v1/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 10 of 10 times since 4 September 2026; the last check, on 18 October 2026, succeeded.
Millions of dated buying and momentum signals: who raised, who's hiring, what changed and when
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
check_watches | Returns what has happened at the companies THIS KEY ALREADY WATCHES, since the last time you asked. This is a personal inbox, not a view of the index. Use it when the question is about continuity — "anything new since last time", "what did Inputs: limit, domain, include_acknowledged |
find_company | Finds a company in the BounceWatch index by name, and returns its domain — which is what every other company tool needs. Use this whenever you have a company's NAME rather than its domain. Do not guess the domain: a wrong guess comes back a Inputs: name, country, limit |
get_company | Firmographic profile of one company from the BounceWatch index: identity, location, headcount, funding history, tech stack, team and competitors. Returns what we currently hold — it never triggers a scan on its own. `coverage` says what mon Inputs: domain, include |
get_company_signals | Returns the dated signal timeline for one company: funding, hiring, partnerships, expansion, product launches, leadership changes and risk events. Use this when you already know which company you care about and need to know what has been ha Inputs: domain, days, categories, signal_keys, limit |
get_refresh_status | Checks a scan queued by refresh_company, and WAITS for it. This call blocks until the scan is done or `wait_seconds` runs out, so you do not have to idle between polls — just call it again if it comes back unfinished. A typical scan needs t Inputs: batch_id, wait_seconds |
get_signal_taxonomy | Lists every signal type BounceWatch detects, grouped by category, with what each one means and whether it is an announcement or an unconfirmed inference. It also returns `coverage`, which says which categories produce steadily and which are |
refresh_company | Queues a fresh scan of one company and returns a batch id to poll with get_refresh_status. Works for companies already in the index and for domains we have never seen, which is how you add one. A scan only refreshes what you ask for, and ea Inputs: domain, modules |
search_companies | Finds companies by firmographics — country, headcount, funding stage — within the set BounceWatch actively observes, most recently refreshed first. By default it returns only companies we have observed in the last 90 days, so the firmograph Inputs: country, min_employees, max_employees, funding_stage, observed_within_days, founded_after |
search_signals | The latest signals across the whole index: which companies did something recently, what it was, and when. This is the tool for ANY question about what is happening. "Show me the latest signals", "what's new", "which companies raised a round Inputs: signal_keys, categories, days, country, min_employees, max_employees |
watch_company | Registers a standing watch on one company, so you find out what happened there without asking again. This is the only tool that persists between sessions. A watched company is kept under continuous monitoring — we keep looking at it for as Inputs: domain, signal_keys, min_weight, label, deliver_webhook, stop |
Every block below points at https://api.bouncewatch.com/api/v1/mcp. Pick your client and copy.
claude mcp add --transport http bouncewatch-signal-intelligence https://api.bouncewatch.com/api/v1/mcp
{
"mcpServers": {
"bouncewatch-signal-intelligence": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://api.bouncewatch.com/api/v1/mcp"]
}
}
}{
"mcpServers": {
"bouncewatch-signal-intelligence": {
"url": "https://api.bouncewatch.com/api/v1/mcp"
}
}
}{
"servers": {
"bouncewatch-signal-intelligence": {
"type": "http",
"url": "https://api.bouncewatch.com/api/v1/mcp"
}
}
}{
"context_servers": {
"bouncewatch-signal-intelligence": {
"url": "https://api.bouncewatch.com/api/v1/mcp"
}
}
}{
"mcpServers": {
"bouncewatch-signal-intelligence": {
"serverUrl": "https://api.bouncewatch.com/api/v1/mcp"
}
}
}{
"mcpServers": {
"bouncewatch-signal-intelligence": {
"url": "https://api.bouncewatch.com/api/v1/mcp"
}
}
}name: BounceWatch Signal Intelligence
version: 0.0.1
schema: v1
mcpServers:
- name: BounceWatch Signal Intelligence
type: streamable-http
url: https://api.bouncewatch.com/api/v1/mcp{
"mcpServers": {
"bouncewatch-signal-intelligence": {
"httpUrl": "https://api.bouncewatch.com/api/v1/mcp"
}
}
}{
"mcpServers": {
"bouncewatch-signal-intelligence": {
"type": "http",
"url": "https://api.bouncewatch.com/api/v1/mcp"
}
}
}{
"mcpServers": {
"bouncewatch-signal-intelligence": {
"url": "https://api.bouncewatch.com/api/v1/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fapi.bouncewatch.com%2Fapi%2Fv1%2Fmcp&type=streamable_http&id=bouncewatch-signal-intelligence&name=BounceWatch%20Signal%20Intelligence
It answered our last check on 18 October 2026 in 213 ms. Over 10 checks since 4 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by bouncewatch.com and served from api.bouncewatch.com, the vendor's own domain: https://api.bouncewatch.com/api/v1/mcp.
10, as returned by the server's own tools/list on 10 September 2026: check_watches, find_company, get_company, get_company_signals, get_refresh_status, get_signal_taxonomy, refresh_company, search_companies, and 2 more.
It answered our last check on 18 October 2026 in 213 ms. Over 10 checks since 4 September 2026 it answered 10.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://api.bouncewatch.com/api/v1/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: com.bouncewatch. Endpoint host: api.bouncewatch.com. ARD identifier: urn:air:com.bouncewatch:mcp:signals.
First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.