BounceWatch Signal Intelligence

{
  "id": "aix_1d17581a74",
  "name": "BounceWatch Signal Intelligence",
  "operator": "(unclaimed - source: registry-official · publisher: com.bouncewatch)",
  "description": "Millions of dated buying and momentum signals: who raised, who's hiring, what changed and when",
  "depth": 2,
  "status": "unclaimed",
  "last_crawled": "2026-09-24",
  "missing_fields": [
    "pricing",
    "operator.identity"
  ],
  "skills": [
    "api-integration"
  ],
  "protocols": {
    "mcp": "https://api.bouncewatch.com/api/v1/mcp",
    "a2a": null
  },
  "pricing": null,
  "regions": [
    "global"
  ],
  "languages": [
    "en"
  ],
  "reputation": {
    "tasks_completed": null,
    "dispute_rate": null,
    "p95_latency_ms": 947,
    "uptime_30d": 0.9819819819819819,
    "onchain_volume_30d_usd": null
  },
  "aix_score": 44,
  "verification": {
    "identity": "none",
    "health": "probe/24h",
    "pricing": "unknown",
    "last_check": "2026-09-24T20:01:18.515Z"
  },
  "pricing_model": "unknown",
  "links": [
    {
      "label": "homepage",
      "url": "https://bouncewatch.com/mcp"
    }
  ],
  "profile": {
    "mcp_server": "bouncewatch",
    "mcp_version": "1.2.0",
    "tool_count": 10,
    "tools": [
      {
        "name": "search_signals",
        "description": "The latest signals across the whole index: which companies did something recently,\nwhat it was, and when.\n\nThis is the tool for ANY question about what is happening. \"Show me the latest\nsignals\", \"what's new\", \"which companies raised a round and are now hiring sales in\nthe Netherlands\", \"who announced expansion in the last two weeks\", \"which of my\ntarget segment just made a key hire\". Returns matching companies with the signals\nthat matched and their dates.\n\nReach for this first. check_watches only reports on companies already being\nwatched by this key and cannot answer a question about the ma"
      },
      {
        "name": "search_companies",
        "description": "Finds companies by firmographics — country, headcount, funding stage — within the\nset BounceWatch actively observes, most recently refreshed first.\n\nBy default it returns only companies we have observed in the last 90 days, so the\nfirmographics you get are backed by recent observation rather than a record we\nlast touched years ago. Each result reports its signal activity, so you can tell a\nclosely-watched company from a thinly-covered one.\n\nIf you want companies selected by what HAPPENED to them rather than by what they\nARE — recently funded, hiring, expanding — use search_signals instead. Tha"
      },
      {
        "name": "find_company",
        "description": "Finds a company in the BounceWatch index by name, and returns its domain — which\nis what every other company tool needs.\n\nUse this whenever you have a company's NAME rather than its domain. Do not guess\nthe domain: a wrong guess comes back as \"not indexed\" for a company we actually\nhold, and sends you on to spend a scan on a domain nobody checked.\n\nReturns up to a handful of candidates with just enough to tell them apart —\ncountry, founding year, headcount, and when we last saw a signal. It never picks\nfor you: names are ambiguous and you have the context that decides. If several\nlook plausibl"
      },
      {
        "name": "get_company",
        "description": "Firmographic profile of one company from the BounceWatch index: identity, location,\nheadcount, funding history, tech stack, team and competitors.\n\nReturns what we currently hold — it never triggers a scan on its own. `coverage` says\nwhat monitoring this company is under; if it is not being followed continuously and\nthe answer depends on facts being current, call refresh_company explicitly.\n\nFor what has been HAPPENING at a company rather than what it IS, use\nget_company_signals.\n\nCost: 10 credits per call at minimum, rising with the extra data you request. Failed calls are not charged."
      },
      {
        "name": "get_company_signals",
        "description": "Returns the dated signal timeline for one company: funding, hiring, partnerships,\nexpansion, product launches, leadership changes and risk events.\n\nUse this when you already know which company you care about and need to know what\nhas been happening and when. To find companies by signal instead, use search_signals.\n\ncategories and signal_keys widen each other rather than narrowing to the overlap:\na category adds all of its keys to whatever signal_keys already lists.\n\nRead `coverage` before drawing conclusions. If `coverage.signal_absence_is_meaningful`\nis false, an empty or thin result reflects"
      },
      {
        "name": "refresh_company",
        "description": "Queues a fresh scan of one company and returns a batch id to poll with\nget_refresh_status. Works for companies already in the index and for domains we\nhave never seen, which is how you add one.\n\nA scan only refreshes what you ask for, and each module reads a different source.\nAnything you leave out keeps the date it already had, so pick by the fact you\nneed:\n\n  signals      recent events and announcements   (default)\n  funding      rounds, investors, valuations     (default)\n  team         headcount, leadership, open roles\n  technology   tech stack\n  business     positioning, model, target mar"
      },
      {
        "name": "get_refresh_status",
        "description": "Checks a scan queued by refresh_company, and WAITS for it.\n\nThis call blocks until the scan is done or `wait_seconds` runs out, so you do not\nhave to idle between polls — just call it again if it comes back unfinished. A\ntypical scan needs two or three calls at the default wait.\n\nRead `is_finished`, not `status`. A scan reaches `completed` when its jobs report\nback, but the signal analysis they started is still writing rows for a few seconds\nafter that — read too early and you get the pre-scan picture with a completed\nstamp on it. `status` becomes `settling` for that window and `is_finished` s"
      },
      {
        "name": "watch_company",
        "description": "Registers a standing watch on one company, so you find out what happened there\nwithout asking again. This is the only tool that persists between sessions.\n\nA watched company is kept under continuous monitoring — we keep looking at it for\nas long as the watch is active, rather than waiting for someone to ask about it.\n\nMatching signals are queued for you and collected with check_watches (free). If\nthis API key has a webhook URL configured, set deliver_webhook to also have them\npushed to it as they land — that is what lets a hosted agent be woken rather than\nhaving to poll.\n\nNarrow it. A watch w"
      },
      {
        "name": "check_watches",
        "description": "Returns what has happened at the companies THIS KEY ALREADY WATCHES, since the\nlast time you asked.\n\nThis is a personal inbox, not a view of the index. Use it when the question is\nabout continuity — \"anything new since last time\", \"what did I miss\", \"what fired\non my watchlist\". If the question is what is happening at companies generally —\nlatest signals, who raised, who is hiring, anything about the market or a company\nnot already watched — that is search_signals, and this tool cannot answer it.\n\nDo not open a session with this call. Answer what was actually asked first; reach\nfor this when t"
      },
      {
        "name": "get_signal_taxonomy",
        "description": "Lists every signal type BounceWatch detects, grouped by category, with what each\none means and whether it is an announcement or an unconfirmed inference.\n\nIt also returns `coverage`, which says which categories produce steadily and which\nare rare by nature. Read it before designing a search: the rarest signals are the\nhighest-value ones — funding, acquisitions, shutdowns — and searching a window for\nthem usually returns almost nothing, because that is how often they happen. Those\nare caught with watch_company, not with a query.\n\nCall this before filtering by signal type in search_signals or ge"
      }
    ],
    "profiled_at": "2026-09-24T20:01:18.515Z"
  },
  "unreachable": false
}