Is the Bouncewatch Signals MCP server down?

mcp-registry/com.bouncewatch/signals · v1.2.0

down
Last checked 2026-10-20 06:35 UTC · handshake 210ms

As of 2026-10-20 06:35 UTC, the Bouncewatch Signals MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 99.3% of Glimind's liveness checks. It had 50 outages in 90 days, with a median recovery of 5 minutes.

uptime (30d checks)
99.3%
checks observed
3,920
outages (90d)
50
tools
10

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

Point your MCP client at this streamable-http endpoint: https://api.bouncewatch.com/api/v1/mcp

Agent-readiness: B (86/100)

B (86/100): 1 error(s), 1 warning(s) across 10 tool(s); ~4,117 tokens of tool definitions.
Scores higher than 55% of 15,387 MCP servers Glimind has audited.
Its tool list costs an agent ~4,117 tokens per session — more than 55% of servers.
94 → 94 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints100
Token cost100
Client compatibility70
Protocol100
Reliability0
Stability100

What to fix (3)

The endpoint did not complete an MCP handshake.

Check the URL, TLS certificate and that the server answers a JSON-RPC "initialize" POST. How to fix →

Handshake + tools/list takes ~1,902 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.bouncewatch/signals"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.bouncewatch/signals"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown 
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.bouncewatch%2Fsignals.svg)](https://glimind.com/server/mcp-registry%2Fcom.bouncewatch%2Fsignals?ref=badge)
HTML 
<a href="https://glimind.com/server/mcp-registry%2Fcom.bouncewatch%2Fsignals?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.bouncewatch%2Fsignals.svg" alt="MCP agent-readiness"></a>
reStructuredText 
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.bouncewatch%2Fsignals.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.bouncewatch%2Fsignals?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:eea85904cfc557cb…, first seen 2026-10-17, included at leaf 16453 of 31,553. Version history · verify what your client received.

Working alternatives

Tools (10)

Compare: most reliable data servers · most reliable search servers · most reliable knowledge servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Bouncewatch Signals MCP server down right now?

As of 2026-10-20 06:35 UTC, the Bouncewatch Signals MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 99.3% of Glimind's liveness checks. It had 50 outages in 90 days, with a median recovery of 5 minutes.

How many tools does Bouncewatch Signals MCP server provide?

Bouncewatch Signals MCP server advertises 10 tools, including check_watches, find_company, get_company, get_company_signals, get_refresh_status.

How do I install Bouncewatch Signals MCP server?

Point your MCP client at this streamable-http endpoint: https://api.bouncewatch.com/api/v1/mcp

Is the Bouncewatch Signals MCP server safe to connect to an AI agent?

Glimind scanned all 10 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Bouncewatch Signals MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve