Усильте агента
Собственная команда издателя. Не эндпоинт PlugMCP.
Host a copy with our keys and logs.
npx -y @bouncewatch/[email protected]У Claude Code нет ссылки для установки локальной команды. Скопируйте команду ниже и выполните её в терминале.
claude mcp add bouncewatch-mcp -- npx -y @bouncewatch/mcp@1.3.0Выполните в терминале.
{ "mcpServers": { "bouncewatch-mcp": { "command": "npx", "args": [ "-y", "@bouncewatch/[email protected]" ] } }}claude_desktop_config.json
Удалённый URL или команда на вашем компьютере? Чем различаются два способа установки
Запустить на PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
ЗапускОт издателя
Find out what changed at a company, and when.
Bounce Watch tracks buying and momentum signals for companies — who raised money, who hired a senior person, who opened an office, won a customer, or announced a partnership. Over forty kinds of event, and every one carries the date it happened. This repository holds the connection details and client configs for the hosted Model Context Protocol server.
Launcher for the hosted Bounce Watch MCP server — company buying and momentum signals, each carrying the date it happened
The server itself is hosted. There is nothing to install or run.
https://api.bouncewatch.com/api/v1/mcp
X-API-Key / Authorization: BearerThere is a Dockerfile here for running the launcher inside a container. It
packages the launcher and nothing else — the server itself is hosted, so running
the image gives you a connection to Bounce Watch, not a copy of it.
com.bouncewatch/signalsclaude mcp add bouncewatch --transport http https://api.bouncewatch.com/api/v1/mcp
Press Connect and approve in the browser. No key to paste.
Ready-made config files are in clients/. Cursor takes the URL
directly:
{
"mcpServers": {
"bouncewatch": {
"url": "https://api.bouncewatch.com/api/v1/mcp"
}
}
}
Add it in the app: Settings → Connectors → Add custom connector, with the URL above. Claude Desktop's config file will not take a remote URL — that file is for servers running on your own machine.
If you would rather keep it in the config file anyway, point it at the launcher below.
For clients that cannot open an HTTP connection, this repository publishes a launcher — a transparent pipe to the same endpoint, with no dependencies:
{
"mcpServers": {
"bouncewatch": {
"command": "npx",
"args": ["-y", "@bouncewatch/mcp"],
"env": { "BOUNCEWATCH_API_KEY": "your-key" }
}
}
}
Both connect to remote MCP servers without any custom node or app. Paste the URL,
add your API key as a header, and the tool list loads itself. See
clients/n8n.md and clients/make.md.
Ask in plain language. The server answers with real company names, dates and sources.
Ten tools, eight of them read-only.
refresh_company and watch_company are the two that write.
Five saved prompts ship with the server.
Every signal carries its own date. Not the date we found it — the date the thing happened. That is what lets you separate this week's news from last year's.
Every signal carries a weight from 1 to 10. A funding round outranks a conference booth. Roughly a third of what happens at any company is background — event attendance, news mentions, follower drift — and all of it is weighted 1 or 2 so you can drop it in one filter. Set a floor of 3 or 4 and you are searching on substance.
An empty result is not the same as a quiet company. Every answer states how recently the company was looked at. When coverage is thin, the answer says so rather than implying nothing happened.
One question typically costs around 50 credits — a signal search plus a timeline
for a handful of companies — so the free tier's 2,500 credits cover about 50 of
them. get_signal_taxonomy and get_refresh_status cost nothing at all.
Keys and balances: https://bouncewatch.com/api-panel/mcp
com.bouncewatch/signals
(entry)MIT. See LICENSE. The hosted service itself is a commercial product; this repository covers the connection details and examples.
Launcher for the hosted Bounce Watch MCP server — company buying and momentum signals, each carrying the date it happened
{ "mcpServers": { "bouncewatch-mcp": { "command": "npx", "args": [ "-y", "@bouncewatch/[email protected]" ] } }}Инструменты
Списка инструментов пока нет. У удалённых серверов он появляется после первой проверки состояния.
FAQ
Скопируйте на этой странице конфигурацию stdio для Cursor, Claude Desktop, Claude Code или VS Code. Она использует установку издателя, а не прокси PlugMCP.
В этой записи не указано обязательных переменных окружения.
@bouncewatch/mcp работает локально через stdio.
Последняя проверка: 2026-11-15. Launcher for the hosted Bounce Watch MCP server — company buying and momentum signals, each carrying the date it happened