Skip to content

BounceWatch Signal Intelligence MCP server

com.bouncewatch/signalsbouncewatch.comstreamable-httpv1.2.0Scanned

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

15 tools: 1 can delete or cancel things, 4 change things and 10 only read.

Tools: 1 delete, 0 irreversible, 4 write, 10 read.
  • Reads private data · 0
  • Reads text others write · 15
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the BounceWatch Signal Intelligence MCP server can do

The BounceWatch Signal Intelligence MCP server is published by bouncewatch.com, a domain the MCP Registry verified. It has 15 tools. It can delete or cancel things (1 tool: update_watchlist_companies) and create or change data (4 tools: refresh_company, watch_company, manage_watchlist and scan_watchlist). 10 tools only read.

15 tools bring in text other people can write (search_signals, search_companies, find_company and 12 more).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 12, 2026, version 1.2.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

15 tools

Deletes or cancels 1Claude Code: deny
  • update_watchlist_companiesAdds companies to a watchlist or removes them, by domain.Reads text others writeNo findings

    Why it is in this group

    • The name "update_watchlist_companies" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Adds companies to a watchlist or removes them, by domain. Companies added are scanned straight away unless you pass scan:false. Scans run in the background at a pace the system can take, so this returns at once: follow progress with get_watchlist. A company already in the list is left alone and costs nothing, so repeating a call is safe. If the scan cannot be paid for, nothing is added. Removing a company stops any scan of it still waiting and returns those credits. Cost: 62 credits per company scanned with the default modules, changing with the modules you choose. Adding with scan:false and removing are free. Nothing is charged for a company read in the last 20 hours, and credits come back for any company that could not be read.

    Annotations the server declares

    • title: Update Watchlist Companies
    • readOnlyHint: false
    • destructiveHint: true
    • openWorldHint: true
Changes things 4Claude Code: ask
  • manage_watchlistCreates a watchlist, or renames, archives or restores one.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "create": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Creates a watchlist, or renames, archives or restores one. Make one list per client or project, so each can be scanned and read on its own. Creating a list costs nothing and scans nothing. Archiving hides a list and keeps everything in it; restore brings it back. Add companies with update_watchlist_companies. Cost: free — call it as often as you need.

    Annotations the server declares

    • title: Manage Watchlist
    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: true
  • refresh_companyQueues a fresh scan of one company and returns a batch id to poll with get_refresh_status.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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 keeps the date it already had, so pick by the fact you need: signals recent events and announcements (default) funding rounds, investors, valuations (default) hiring open roles and headcount business positioning, model, target market The default is signals + funding, because those are the two that go out of date fastest and the two most answers turn on. Pass modules explicitly to go cheaper — `["signals"]` alone is the least you can usefully scan. This spends credits and real scanning budget, so call it deliberately: when `coverage` on a previous answer showed stale data AND the decision depends on current facts. Do not call it speculatively across a list of candidates. Returns in a second or two; the scan itself typically takes 60-180 seconds. Poll get_refresh_status (free) until it reports finished, then re-read the data with get_company or get_company_signals. Cost: 36 credits per call at minimum, rising with the extra data you request. Failed calls are not charged.

    Annotations the server declares

    • title: Refresh Company
    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: true
  • scan_watchlistScans the companies in a watchlist, or cancels a scan in progress.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Scans the companies in a watchlist, or cancels a scan in progress. Called without max_credits, this only reports what a scan would cover and cost, and starts nothing. Do that first and confirm the cost with the user. Then call it again with max_credits to start. If the cost has risen above that figure, nothing starts. Companies read in the last 20 hours are skipped without charge, so re-running after a partial failure only pays for what is missing. Pass older_than_days to also leave out companies this list scanned more recently than that. Scans run in the background, and a long list can take hours. Follow progress with get_watchlist, which also shows how many signals each company has; read the ones worth a closer look with get_company_signals. A cancel stops what has not started and returns those credits. Cost: 62 credits per company scanned with the default modules, changing with the modules you choose. Estimates and cancelling are free, and credits come back for any company that could not be read.

    Annotations the server declares

    • title: Scan Watchlist
    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: true
  • watch_companyRegisters a standing watch on one company, so you find out what happened there without asking again.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Registers a standing watch on one company, so you find out what happened there without asking again. This is the only tool that keeps looking on its own 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 to ask about it. Matching signals are queued for you and collected with check_watches (free). If this API key has a webhook URL configured, set deliver_webhook to also have them pushed to it as they land — that is what lets a hosted agent be woken rather than having to poll. Narrow it. A watch with no filters delivers everything, including the background chatter that makes a feed unreadable: pass signal_keys for the events you care about, or min_weight to set a floor on how much a signal has to matter. Given both, a signal has to clear both — a named key that sits below the floor never fires. Call again with the same domain to change the filters, or with stop:true to end the watch. Watching a domain we have not indexed is allowed, but nothing will fire until it is — refresh_company indexes it. Cost: 5 credits per call. Failed calls are not charged.

    Annotations the server declares

    • title: Watch Company
    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: true
Only reads 10Show 10 read-only tools
  • check_watchesReturns what has happened at the companies THIS KEY ALREADY WATCHES, since the last time you asked.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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 what is happening at companies generally — latest signals, who raised, who is hiring, anything about the market or a company not already watched — that is search_signals, and this tool cannot answer it. Do not open a session with this call. Answer what was actually asked first; reach for this when the user's question is about their own watches. Each event is handed over once: collecting it marks it seen, so the next call returns only what is new. Pass include_acknowledged to re-read ones you already collected. An empty result means nothing matched YOUR watches. It is not a statement about the market, and if you hold no watches it says nothing at all — the response reports how many you have so the two cases can be told apart. The response also lists your active watches, so this is the only call needed to see both what fired and what is armed. Cost: free — call it as often as you need.

    Annotations the server declares

    • title: Check Watches
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • find_companyFinds a company in the BounceWatch index by name, and returns its domain — which is what every other company tool needs.Reads text others writeNo findings

    Why it is in this group

    • The name "find_company" says "find": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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 you on to spend a scan on a domain nobody checked. Returns up to a handful of candidates with just enough to tell them apart — country, founding year, headcount, and when we last saw a signal. It never picks for you: names are ambiguous and you have the context that decides. If several look plausible, say so rather than choosing silently. Once you have picked, get_company returns the full profile. An empty result means no company by that name is in our index. It is not a statement about whether the company exists. If you know its domain, refresh_company indexes it. Cost: 3 credits per call. Failed calls are not charged.

    Annotations the server declares

    • title: Find Company
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • get_companyFirmographic profile of one company from the BounceWatch index: identity, location, headcount, business model and funding history.Reads text others writeNo findings

    Why it is in this group

    • The name "get_company" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Firmographic profile of one company from the BounceWatch index: identity, location, headcount, business model and funding history. 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 continuously and the answer depends on facts being current, call refresh_company explicitly. For what has been HAPPENING at a company rather than what it IS, use get_company_signals. Cost: 10 credits per call at minimum, rising with the extra data you request. Failed calls are not charged.

    Annotations the server declares

    • title: Get Company
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • get_company_signalsReturns the dated signal timeline for one company: funding, hiring, partnerships, expansion, product launches, leadership changes and risk events.Reads text others writeNo findings

    Why it is in this group

    • The name "get_company_signals" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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 search_signals. categories and signal_keys widen each other rather than narrowing to the overlap: a category adds all of its keys to whatever signal_keys already lists. A company with more signals than `limit` returns `next_cursor`: call again with it to read the older ones, until it comes back null. `total_signals` is how many the whole window holds, and the number to report; `signal_count` is only this page. Read `coverage` before drawing conclusions. If `coverage.signal_absence_is_meaningful` is false, an empty or thin result reflects our scanning gap, not the company — say so rather than reporting the company as quiet. Cost: 8 credits per call. Failed calls are not charged.

    Annotations the server declares

    • title: Get Company Signals
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • get_refresh_statusChecks a scan queued by refresh_company, and WAITS for it.Reads text others writeNo findings

    Why it is in this group

    • The name "get_refresh_status" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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`, not `status`. A scan reaches `completed` when its jobs report back, but the signal analysis they started is still writing rows for a few seconds after that — read too early and you get the pre-scan picture with a completed stamp on it. `status` becomes `settling` for that window and `is_finished` stays false until the writes stop. Do not answer from the old data while a scan you asked for is unfinished: you requested it because the existing figures were too stale to rely on, and they have not changed yet. Either wait for it, or say plainly that a refresh is in flight. When it finishes, `signals_added` says how many new signals the scan actually produced — zero is a real answer and means we looked and found nothing new, not that the scan failed. Then read the data with get_company or get_company_signals; this tool returns progress, not company data. Lost the batch_id? Pass `domain` instead: it checks the latest scan this key queued for that company. Cost: free — call it as often as you need.

    Annotations the server declares

    • title: Get Refresh Status
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • 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.Reads text others writeNo findings

    Why it is in this group

    • The name "get_signal_taxonomy" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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 rarest signals are the highest-value ones — funding, acquisitions, shutdowns — and searching a window for them usually returns almost nothing, because that is how often they happen. Those are caught with watch_company, not with a query. Call this before filtering by signal type in search_signals or get_company_signals: filters are matched exactly, and an unrecognised key returns nothing rather than an error. The answer is stable, so once per session is enough. Cost: free — call it as often as you need.

    Annotations the server declares

    • title: Get Signal Taxonomy
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • get_watchlistReturns one watchlist as a map of where to look: each company with how many signals it has in the window and the strongest of them, plus when it was last scanned and the progress o…Reads text others writeNo findings

    Why it is in this group

    • The name "get_watchlist" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Returns one watchlist as a map of where to look: each company with how many signals it has in the window and the strongest of them, plus when it was last scanned and the progress of any scan in progress. It carries no signal bodies; read a company worth a closer look with get_company_signals. The window is the last `days` (default 30) by event date. With since_last_pull it is instead everything recorded since the last complete since_last_pull read of this list, which includes older events a recent scan only just found, and reaching the last page of such a read moves that marker. with_signals_only leaves out companies with nothing in the window. Pages stop at `limit` companies or at a size every client can hold, whichever comes first. Follow next_cursor to reach the whole list. A scan's `status` moves through running and settling to completed. Settling means the companies are done and the last signals are still being written, so read results once it reports completed. Cost: free — call it as often as you need.

    Annotations the server declares

    • title: Get Watchlist
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • list_watchlistsLists the watchlists on this account: named sets of companies, usually one per client or project, with how many companies each holds and what has been spent on it.Reads text others writeNo findings

    Why it is in this group

    • The name "list_watchlists" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Lists the watchlists on this account: named sets of companies, usually one per client or project, with how many companies each holds and what has been spent on it. A watchlist is not a watch. Nothing in it is scanned until companies are added or a scan is requested. For a company you want followed continuously, that is watch_company. Cost: free — call it as often as you need.

    Annotations the server declares

    • title: List Watchlists
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • search_companiesFinds companies by firmographics — country, headcount, funding stage — within the set BounceWatch actively observes, most recently refreshed first.Reads text others writeNo findings

    Why it is in this group

    • The name "search_companies" says "search": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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 record we last touched years ago. Each result reports its signal activity, so you can tell a closely-watched company from a thinly-covered one. If you want companies selected by what HAPPENED to them rather than by what they ARE — recently funded, hiring, expanding — use search_signals instead. That is the stronger discovery path and usually the one you want. Cost: 5 credits per call. Failed calls are not charged.

    Annotations the server declares

    • title: Search Companies
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • search_signalsThe latest signals across the whole index: which companies did something recently, what it was, and when.Reads text others writeNo findings

    Why it is in this group

    • The name "search_signals" says "search": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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 announced expansion in the last two weeks", "which of my target segment just made a key hire". Returns matching companies with the signals that matched and their dates. Reach for this first. check_watches only reports on companies already being watched by this key and cannot answer a question about the market or about a company that is not on that list. Filter by signal type, category, recency, country, headcount and funding stage. Call get_signal_taxonomy first if you are unsure which signal keys exist — unrecognised keys are rejected rather than quietly returning nothing. The two signal filters WIDEN each other rather than narrowing to the overlap: a category adds all of its keys to whatever signal_keys already lists. min_weight then cuts what is left, so a low-weight signal type named alongside a floor above its own weight returns nothing rather than one of the two being quietly ignored. `coverage` is working material for you, not for the answer: it bounds what this search could have found. Let it shape what you claim, and offer a narrower search rather than reporting figures about our index. Cost: 12 credits per call. Failed calls are not charged.

    Annotations the server declares

    • title: Search Signals
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write15
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:35 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
5
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://api.bouncewatch.com/.well-known/oauth-protected-resource/api/v1/mcp
Authorization servers
https://api.bouncewatch.com
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 5 tools that change things (1 destructive, 4 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://api.bouncewatch.com/api/v1/mcp: tools/list returned 15 tools to an anonymous client, including update_watchlist_companies (destructive), refresh_company (write), watch_company (write), manage_watchlist (write), scan_watchlist (write)

    What this check looks for

Posture changes

  1. Nov 6, 2026
    • Tools that change things, listed without credentials: 2 to 5

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools5 added, 5 changed.+5 added~5 changedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 2 -> 5.View diff
    • Tools that change things, listed without credentials: 2 to 5

Install

Pinned to version 1.2.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__signals__search_signals",
      "mcp__signals__search_companies",
      "mcp__signals__find_company",
      "mcp__signals__get_company",
      "mcp__signals__get_company_signals",
      "mcp__signals__get_refresh_status",
      "mcp__signals__check_watches",
      "mcp__signals__list_watchlists",
      "mcp__signals__get_watchlist",
      "mcp__signals__get_signal_taxonomy"
    ],
    "ask": [
      "mcp__signals__refresh_company",
      "mcp__signals__watch_company",
      "mcp__signals__manage_watchlist",
      "mcp__signals__scan_watchlist"
    ],
    "deny": [
      "mcp__signals__update_watchlist_companies"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as signals. Review it before you use it.

Capability tags behind 15 rules
  • mcp__signals__search_signals untrusted-input
  • mcp__signals__search_companies untrusted-input
  • mcp__signals__find_company untrusted-input
  • mcp__signals__get_company untrusted-input
  • mcp__signals__get_company_signals untrusted-input
  • mcp__signals__refresh_company untrusted-input
  • mcp__signals__get_refresh_status untrusted-input
  • mcp__signals__watch_company untrusted-input
  • mcp__signals__check_watches untrusted-input
  • mcp__signals__list_watchlists untrusted-input
  • mcp__signals__manage_watchlist untrusted-input
  • mcp__signals__update_watchlist_companies untrusted-input
  • mcp__signals__scan_watchlist untrusted-input
  • mcp__signals__get_watchlist untrusted-input
  • mcp__signals__get_signal_taxonomy untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.bouncewatch/signals/verify?hash=a171377f857bf378c081abdfac535c8b848cc9a4a9eebf69757820c14686fe80" | jq -e '.changed == false'

Pinned hash a171377f857b, from Nov 12, 2026, 18:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.bouncewatch/signals/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.bouncewatch/signals
[![Anlyon Radar](https://radar.anlyon.com/badge/com.bouncewatch/signals.svg)](https://radar.anlyon.com/servers/com.bouncewatch/signals)

Source: MCP Registry. Synced Oct 21, 2026, 17:52 UTC.

BounceWatch Signal Intelligence MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the BounceWatch Signal Intelligence MCP server safe?

No scan can promise that. What its definitions show: 15 tools, 5 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the BounceWatch Signal Intelligence MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: update_watchlist_companies.

Can the BounceWatch Signal Intelligence MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the BounceWatch Signal Intelligence MCP server have?

15 tools: 1 destructive, 4 write, 10 read. update_watchlist_companies, refresh_company, watch_company, manage_watchlist, scan_watchlist, search_signals, search_companies, find_company and 7 more.

Does the BounceWatch Signal Intelligence MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the BounceWatch Signal Intelligence MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the BounceWatch Signal Intelligence MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 12, 2026. Every change is on this page and in its Atom feed.