Millions of dated buying and momentum signals: who raised, who's hiring, what changed and when
Connect Remote server
claude mcp add --transport http signals https://api.bouncewatch.com/api/v1/mcp --header "X-API-Key: <X_API_KEY>"
{
"mcpServers": {
"signals": {
"url": "https://api.bouncewatch.com/api/v1/mcp",
"headers": {
"X-API-Key": "<X_API_KEY>"
}
}
}
}
{
"servers": {
"signals": {
"type": "http",
"url": "https://api.bouncewatch.com/api/v1/mcp",
"headers": {
"X-API-Key": "<X_API_KEY>"
}
}
}
}
Settings > Connectors > Add custom connector
URL: https://api.bouncewatch.com/api/v1/mcp
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools 15 found in our last check
search_signalsThe 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 and are now hiring sales in the Nether…
search_companiesFinds 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 firmographics you get are backed by recent observ…
find_companyFinds 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 as "not indexed" for a company we actual…
get_companyFirmographic profile of one company from the BounceWatch index: identity, location, headcount, business model and funding history. Returns what we currently hold — it never triggers a scan on its own. `coverage` says what monitoring this company is under; if it is not being foll…
get_company_signalsReturns 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 happening and when. To find companies by…
refresh_companyQueues 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 each module reads a different source. Any…
get_refresh_statusChecks 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 two or three calls at the default wait.…
watch_companyRegisters a standing watch on one company, so you find out what happened there without asking again. This is the only tool that keeps looking on its own between sessions. A watched company is kept under continuous monitoring — we keep looking at it for as long as the watch is ac…
check_watchesReturns 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 I miss", "what fired on my watchlist".…
list_watchlistsLists the watchlists on this account: named sets of companies, usually one per client or project, with how many companies each holds and what has been spent on it. A watchlist is not a watch. Nothing in it is scanned until companies are added or a scan is requested. For a compan…
manage_watchlistCreates a watchlist, or renames, archives or restores one. Make one list per client or project, so each can be scanned and read on its own. Creating a list costs nothing and scans nothing. Archiving hides a list and keeps everything in it; restore brings it back. Add companies w…
update_watchlist_companiesAdds companies to a watchlist or removes them, by domain. Companies added are scanned straight away unless you pass scan:false. Scans run in the background at a pace the system can take, so this returns at once: follow progress with get_watchlist. A company already in the list i…
scan_watchlistScans the companies in a watchlist, or cancels a scan in progress. Called without max_credits, this only reports what a scan would cover and cost, and starts nothing. Do that first and confirm the cost with the user. Then call it again with max_credits to start. If the cost has…
get_watchlistReturns one watchlist as a map of where to look: each company with how many signals it has in the window and the strongest of them, plus when it was last scanned and the progress of any scan in progress. It carries no signal bodies; read a company worth a closer look with get_co…
get_signal_taxonomyLists 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 rare by nature. Read it before designi…
Headers
| Name | Description |
|---|---|
X-API-KeyOptional, secret | Optional. Leave this blank to connect with OAuth — press Connect and approve in the browser, and no key is needed. Paste a key only if your client cannot do OAuth. Keys with free trial credits: https://bouncewatch.com/api-panel/mcp — same key and credit pool as the REST API, no separate subscriptio… |
Details
| Endpoint | https://api.bouncewatch.com/api/v1/mcp (Streamable HTTP) |
| First published | 13 Aug 2026 |
| Last updated | 13 Aug 2026 |
| Registry name | com.bouncewatch/signals |
More search and web servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
