All servers · Company & business data

BounceWatch Signal Intelligence

com.bouncewatch/signals · v1.2.0

Measured by MCP Station

Description written by the publisher, not verified

Millions of dated buying and momentum signals: who raised, who's hiring, what changed and when

Connect

claude mcp add --transport http signals https://api.bouncewatch.com/api/v1/mcp

{
  "mcpServers": {
    "signals": {
      "url": "https://api.bouncewatch.com/api/v1/mcp"
    }
  }
}

Tools as reported by the server

• 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 and are now hiring sales in the Netherlands", "who announce
• 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 firmographics you get are backed by recent observation rather than a r
• 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 as "not indexed" for a company we actually hold, and sends yo
• 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 monitoring this company is under; if it is not being followed c
• 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 happening and when. To find companies by signal instead, use s
• 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 each module reads a different source. Anything you leave out k
• 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 two or three calls at the default wait. Read `is_finished`, n
• 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 long as the watch is active, rather than waiting for someone
• 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 I miss", "what fired on my watchlist". If the question is wh
• 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 rare by nature. Read it before designing a search: the rare

Website · JSON · Text for agents · Registry updated 2026-08-13