com.bouncewatch/signals

MCPCommunitylive
v1.2.0com.bouncewatchUnknownAktualisiert vor 1 Mon.

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

Endpunkt-Statuslive
geprüft vor 16 Std. · 534 ms
100 % der letzten 4 Prüfungen haben diesen Endpunkt erreicht
Läuft in
ClaudeCursorCopilotChatGPTGemini

Abgeleitet aus den Transporten, die dieser Eintrag deklariert (streamable-http). Ein Client, der hier nicht steht, ist damit nicht ausgeschlossen — Forge kann ihn nur nicht bestätigen.

Automatisch aus öffentlichen Quellen indexiert. Vom Entwickler auf Forge noch nicht verifiziert.Diesen Eintrag beanspruchen →
vor 1 Mon.Letzte Aktualisierung
Paket
Autorcom.bouncewatch
LizenzUnknown
Version1.2.0
Quellemcp-registry
Trust-Status
B
60/100Gut
Im Forge-Index gelistet+10/10
Publisher-Identität verifiziert+0/30
Publisher: für diesen Eintrag ist kein Repository hinterlegt, daher kann `forge publish` die Inhaberschaft nicht automatisch prüfen. Nutze oben „Diesen Eintrag beanspruchen“ — Forge prüft diese Fälle von Hand.
Domain-Verifizierung+0/10
Für diesen Eintragstyp derzeit nicht verfügbar — die Domain-Prüfung läuft heute nur für npm-gestützte Pakete, diese Zeile lässt sich hier also noch nicht erreichen, unabhängig davon, was auf der Domain liegt.
Prompt-Injection-Scan · sauber+30/30
Obfuskations-/Exfiltrations-Scan · sauber+20/20
StatusVon der Community indexiert
PublisherNicht verifiziert
SignaturNicht signiert
Domain
Herkunft
AbhängigkeitenNicht auditiert
Tool-Oberfläche10 Tools · keines privilegiert
Sicherheits-Scan✓ Saubervlive · heuteWie gut funktioniert dieser Scan?
EvaluierungenKeine
Indexiert11. Aug. 2026

Die Verifizierung bestätigt die Identität des Publishers (die Inhaberschaft am Repo), nicht die Sicherheit des Codes. Der Sicherheits-Scan deckt bekannte CVEs und verdächtige Installationsskripte ab.

Tools

10 Tools · keines privilegiert
Live am Endpunkt des Anbieters beobachtet16h ago

Aus einem echten MCP-Handshake initialize → tools/list gegen den deklarierten Endpunkt gelesen. Es wurde nie ein Tool aufgerufen — tools/list ist der lesende Introspektionsaufruf, den das Protokoll dafür vorsieht. Es spiegelt wider, was der Server in diesem Moment angeboten hat; ein gehosteter Endpunkt ist an keine Version gebunden und kann sich ohne Ankündigung ändern.

  • https://api.bouncewatch.com/api/v1/mcp10 Tools · 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…

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

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

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

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

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

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

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

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

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

Für dieses Tool wurde kein Eingabeschema veröffentlicht.

10 von 10 Tools haben eine Beschreibung veröffentlicht.

Tool-Namen und -Beschreibungen stammen vom Publisher und werden wortgetreu als inerter Text angezeigt. Es sind die Zeichenketten, die ein MCP-Client an ein Modell übergibt, deshalb prüft Forge sie auf Prompt-Injection-Muster — jeder Befund erscheint oben beim Sicherheits-Scan. „Privilegiert“ ist ein Schlagwort-Treffer im Tool-Namen, keine Prüfung dessen, was das Tool tut: ein harmlos klingender Name kann trotzdem alles tun.

Über

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

Schlagwörter
mcp
Alternativen
Tool-Oberflächen werden verglichen…

Keine Abdeckung der Abhängigkeiten

Dieser Eintrag veröffentlicht kein npm-Paket, daher hat Forge keinen Abhängigkeitsbaum dafür. Das ist eine Lücke in der Abdeckung — keine Aussage, dass er keine Abhängigkeiten hat.