com.bouncewatch/signals

MCPcomunidaden línea
v1.2.0com.bouncewatchUnknownActualizado hace 1 m

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

Estado del endpointen línea
comprobado hace 16 h · 534 ms
100 % de las últimas 4 comprobaciones llegaron a este endpoint
Funciona en
ClaudeCursorCopilotChatGPTGemini

Inferido de los transportes que declara este listado (streamable-http). Que un cliente no aparezca aquí no significa que se haya descartado: simplemente Forge no puede confirmarlo.

Indexado automáticamente desde fuentes públicas. Aún sin verificar por su desarrollador en Forge.Reclamar este listado →
hace 1 mÚltima actualización
Paquete
Autorcom.bouncewatch
LicenciaUnknown
Versión1.2.0
Fuentemcp-registry
Estado de confianza
B
60/100Bueno
Listado en el índice de Forge+10/10
Identidad del publicador verificada+0/30
Publicador: este listado no tiene ningún repositorio registrado, así que `forge publish` no puede verificar la propiedad de forma automática. Usa «Reclamar este listado» arriba — en Forge lo revisamos a mano.
Verificación de dominio+0/10
Ahora mismo no está disponible para este tipo de listado: hoy la comprobación de dominio solo se ejecuta para paquetes publicados en npm, así que esta fila todavía no se puede conseguir aquí, sea lo que sea lo que haya alojado en el dominio.
Análisis de inyección de prompts · limpio+30/30
Análisis de ofuscación / exfiltración · limpio+20/20
EstadoIndexado por la comunidad
PublicadorSin verificar
FirmaSin firmar
Dominio
Procedencia
DependenciasSin auditar
Superficie de herramientas10 herramientas · ninguna privilegiada
Análisis de seguridad✓ Limpiovlive · hoy¿Qué tan bien funciona este análisis?
EvaluacionesNinguna
Indexado11 ago 2026

La verificación confirma la identidad del publicador (la propiedad del repo), no la seguridad del código. El análisis de seguridad cubre los CVE conocidos y los scripts de instalación sospechosos.

Herramientas

10 herramientas · ninguna privilegiada
Observado en vivo desde el endpoint del proveedor16h ago

Leído de un handshake MCP real initialize → tools/list contra el endpoint declarado. No se invocó ninguna herramienta: tools/list es la llamada de introspección de solo lectura que el protocolo define para esto. Refleja lo que el servidor anunciaba en ese momento; un endpoint alojado no está fijado a ninguna versión y puede cambiar sin avisar.

  • https://api.bouncewatch.com/api/v1/mcp10 herramientas · 534 ms
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 Netherlands", "who announ…

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

ParámetroTipoDescripción
signal_keysarraySignal types to match, e.g. ["recently_funded","key_hire_announced"]. See get_signal_taxonomy.
categoriesarraySignal categories to match: funding, hiring, business, product, growth, event, milestone, risk.
daysintegerLookback window in days. Default 30. Max 365. Shorter windows mean sharper timing.
countrystringISO 3166-1 alpha-2 country code of the company HQ, e.g. "NL", "DE", "US".
min_employeesintegerMinimum headcount. Companies whose headcount we do not hold are excluded when this is set — not knowing a number is not evidence it falls outside the range.
max_employeesintegerMaximum headcount. Same exclusion of unknown headcounts as min_employees.
funding_stagestringFunding stage, e.g. "Seed", "Series A", "Pre Seed". Spacing, case and hyphens are normalised; a value that matches nothing is rejected with the valid list rath…
require_all_keysbooleanWhen true, only return companies showing EVERY requested signal key in the window (signal stacking) rather than any of them. Default false.
min_weightintegerOnly count signals worth at least this much, 1-10. Background chatter (event attendance, news mentions, follower drift) sits at 1-2 and dominates an unfiltered…
founded_afterintegerOnly companies founded in or after this year, e.g. 2023. Companies whose founding year we do not hold are excluded when this is set, and the result says so.
founded_beforeintegerOnly companies founded in or before this year. Same exclusion of unknown founding years as founded_after.
sortstringmost_recent (default) ranks by newest matching signal; most_active by how many matched.
limitintegerMax companies to return. Default 25, max 100.
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 observation rather than a…

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…

ParámetroTipoDescripción
countrystringISO 3166-1 alpha-2 country code of the company HQ, e.g. "NL", "DE", "US".
min_employeesintegerMinimum headcount. Companies whose headcount we do not hold are excluded when this is set — same rule as founded_after, and for the same reason: not knowing a…
max_employeesintegerMaximum headcount. Same exclusion of unknown headcounts as min_employees.
funding_stagestringFunding stage, e.g. "Seed", "Series A", "Pre Seed". Spacing, case and hyphens are normalised; a value that matches nothing is rejected with the valid list rath…
observed_within_daysintegerOnly companies we observed within this many days, 30-365. Default 90. Widening it grows the result set but lowers confidence in the firmographics, because the…
founded_afterintegerOnly companies founded in or after this year, e.g. 2023. Companies whose founding year we do not hold are excluded when this is set, and the result says so.
founded_beforeintegerOnly companies founded in or before this year. Same exclusion of unknown founding years as founded_after.
limitintegerMax companies to return. Default 20, max 50.
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 actually hold, and sends…

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…

ParámetroTipoDescripción
name*stringCompany name to look for, e.g. "Silk and Cashmere". A domain is also accepted and resolved directly.
countrystringISO 3166-1 alpha-2 code of the company HQ, e.g. "NL". Narrows an ambiguous name; a code that matches nothing is rejected rather than silently ignored.
limitintegerMax candidates to return. Default 5, max 10.
get_companyFirmographic 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…

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…

ParámetroTipoDescripción
domain*stringCompany domain, e.g. "stripe.com". URLs are accepted and normalised.
includearrayOptional enrichment modules: business, technology, funding, team, competitors. Each adds credits — request only what you will use.
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 signal instead, use…

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…

ParámetroTipoDescripción
domain*stringCompany domain, e.g. "stripe.com". URLs are accepted and normalised.
daysintegerLookback window in days. Default 90, max 365.
categoriesarrayRestrict to signal categories (funding, hiring, business, product, growth, event, milestone, risk). Call get_signal_taxonomy for the list.
signal_keysarrayRestrict to exact signal keys, e.g. ["recently_funded","key_hire_announced"]. Unrecognised keys are rejected rather than silently ignored.
limitintegerMax signals to return, newest first. Default 50, max 100.
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. Anything you leave out…

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…

ParámetroTipoDescripción
domain*stringCompany domain, e.g. "stripe.com". URLs are accepted and normalised.
modulesarrayWhat to refresh: business, technology, funding, team, signals, competitors. Each adds credits. Defaults to signals only, which is the cheapest useful scan.
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. Read `is_finished`…

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

ParámetroTipoDescripción
batch_id*stringThe batch_id returned by refresh_company.
wait_secondsintegerHow long this call may block waiting for the scan, 0-25. Default 20. It returns the moment the scan finishes, and waiting the full 25 costs exactly what waitin…
watch_companyRegisters 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 someo…

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

ParámetroTipoDescripción
domain*stringCompany domain, e.g. "stripe.com". URLs are accepted and normalised.
signal_keysarrayOnly these signal types wake you. Omit for all of them. Values come from get_signal_taxonomy; an unrecognised key is rejected with the valid list rather than c…
min_weightintegerFloor on how much a signal has to matter, 1-10. Roughly: 8+ funding and leadership changes, 5+ hiring and expansion, below 4 background noise. Signals we do no…
labelstringYour own note for this watch, e.g. "Q3 pipeline". Returned with every event so you can route it without a second lookup.
deliver_webhookbooleanAlso push matches to this key's configured webhook URL. Default false. Events are queued for check_watches either way.
stopbooleanEnds the watch on this domain. Already-queued events stay collectable.
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". If the question is…

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…

ParámetroTipoDescripción
limitintegerMax events to return. Default 25, max 100. Anything beyond the limit stays queued for the next call.
domainstringOnly events for this watched domain.
include_acknowledgedbooleanAlso return events already collected, and do not acknowledge anything on this call. Use when you lost context and need to re-read. Default false.
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 designing a search: the ra…

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

No se publicó ningún esquema de entrada para esta herramienta.

10 de 10 herramientas publicaron una descripción.

Los nombres y descripciones de las herramientas los escribe el publicador y se muestran literalmente como texto inerte. Son las cadenas que un cliente MCP pasa al modelo, así que Forge las analiza en busca de patrones de inyección de prompts — cualquier hallazgo aparece junto al análisis de seguridad de arriba. «Privilegiada» es una coincidencia de palabra clave en el nombre de la herramienta, no una auditoría de lo que hace: un nombre inofensivo puede hacer cualquier cosa.

Acerca de

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

Palabras clave
mcp
Alternativas
Comparando superficies de herramientas…

Sin cobertura de dependencias

Esta entrada no publica ningún paquete de npm, así que Forge no tiene un árbol de dependencias para ella. Es una carencia de cobertura, no una afirmación de que no tenga dependencias.