Servidor MCP de Bounce Watch

Qué servidores del registro oficial de MCP son de Bounce Watch, si responden y qué ofrecen. Un programa comprobó cada dato; nada está copiado de la página del producto.

leído el 2026-10-13

← Volver a Bounce Watch

De quién es el servidor

Nombre en el registrocom.bouncewatch/signalsverificado en el registro MCP

El nombre en el registro está bajo bouncewatch.com. El registro solo permite usar ese espacio de nombres a quien demuestra control del dominio por DNS o HTTP.

Cuando le preguntamoscomprobado el 2026-10-13

Estadorespondecomprobado el 2026-10-13
Herramientas10
El servidor se llamabouncewatch
Versión del servidor1.2.0
Versión del protocolo2025-06-18

El 2026-10-13 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 313 ms.

Herramientas que ofrece10 herramientas · leído el 2026-10-13

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…
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…
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…
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…
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…
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…
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…
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…
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…
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…

Cómo conectar

Añade el servidor a la configuración de tu cliente MCP. Claude Desktop, Cursor y la mayoría de los demás clientes leen este formato:

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

Especificación OpenAPI

9 rutas, leído el 2026-10-13. Abrir la especificación ↗

Cada línea es algo que un programa encontró al buscar: la entrada del registro, la respuesta del propio servidor, una especificación que se puede leer. Si falta una línea, es que no la encontramos, no que no exista.