BounceWatch MCP MCP server

An official MCP server provided by Bounce Watch that allows AI agents to query company signal intelligence, including funding rounds, hiring trends, and expansion events. It supports both developer integration via API keys and direct user authentication for assistants like Claude and ChatGPT.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by Bounce Watch

MCP endpoint (Streamable HTTP)

https://api.bouncewatch.com/api/v1/mcp

Vendor documentation

What you can do with it

Query which companies recently raised funding
Identify companies actively hiring in specific regions
Track competitor monitoring and market trends
Enrich company profiles with live signal data

Tools advertised by the last live check:

search_signals
search_companies
find_company
get_company
get_company_signals
refresh_company
get_refresh_status
watch_company
check_watches
get_signal_taxonomy

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

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

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add bouncewatch-mcp --url https://api.bouncewatch.com/api/v1/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable bouncewatch-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "bouncewatch-mcp": {
      "url": "https://api.bouncewatch.com/api/v1/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "bouncewatch-mcp": {
      "type": "streamableHttp",
      "url": "https://api.bouncewatch.com/api/v1/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start bouncewatch-mcp and inspect its tools.

VS Code configuration

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

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

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

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "bouncewatch-mcp": {
      "url": "https://api.bouncewatch.com/api/v1/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "bouncewatch-mcp": {
      "serverUrl": "https://api.bouncewatch.com/api/v1/mcp"
    }
  }
}

See all 1,583

Do you run BounceWatch MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing