mcpbeat

BounceWatch Signal Intelligence MCP Server

com.bouncewatch/signals
answering

BounceWatch Signal Intelligence is answering right now. Last checked 15 min ago.

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

Uptime history 42 hours of history
42 hours agonow
100.0%
Uptime 24h
91 of 91 checks
—
Tools
hidden behind auth
184 ms
Response time
average over 24h
API key or OAuth
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 15 min ago.

run in your terminal
claude mcp add signals --transport http https://api.bouncewatch.com/api/v1/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "signals": {
      "url": "https://api.bouncewatch.com/api/v1/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.signals]
url = "https://api.bouncewatch.com/api/v1/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "signals": {
      "url": "https://api.bouncewatch.com/api/v1/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "signals": {
      "url": "https://api.bouncewatch.com/api/v1/mcp"
    }
  }
}

This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.

Endpoints

URLTransportStateLatencyChecked
https://api.bouncewatch.com/api/v1/mcp streamable-http needs key 183 ms 15 min ago

BounceWatch Signal Intelligence — questions

Answers built from our own checks of this server.

Why is there no tool list for BounceWatch Signal Intelligence?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is BounceWatch Signal Intelligence working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 184 ms. The bar chart above shows every period we have measured.
How do I connect BounceWatch Signal Intelligence?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own key or an OAuth login: it refuses anonymous clients.
Does BounceWatch Signal Intelligence need an API key?
Yes. Every time we knock, BounceWatch Signal Intelligence answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is BounceWatch Signal Intelligence?
It answers our handshake in 184 ms on average, which is faster than 66% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.