Skip to content

Grok Cybersecurity News & Breach Alerts — buy per-query in-session (bleepingwatch) get_recommended_action

How to: Grok Cybersecurity News & Breach Alerts — buy per-query in-session (bleepingwatch) get_recommended_action

client:Grok transport:streamable-http tool:get_recommended_action

Add Cybersecurity News & Breach Alerts — buy per-query in-session (bleepingwatch) to Grok

  1. 01

    Open .mcp.json (in your project root) and merge this in. Keep any servers already there.

{
  "mcpServers": {
    "data-cybersecurity-news-breach-alert": {
      "type": "http",
      "url": "https://a2awire.com/mcp/data/bleepingwatch-cybersecurity-news-breach-alerts-522e02/http"
    }
  }
}
  1. 02

    Save the file and restart Grok.

  2. 03

    Ask for something get_recommended_action does. Grok lists the server's tools on connect and calls get_recommended_action itself — you do not invoke it by name.

  3. 04

    If nothing happens, check the server is running and that Cybersecurity News & Breach Alerts — buy per-query in-session (bleepingwatch)'s identifier in your config matches the one above exactly.

Grok Build reads Claude Code's .mcp.json and Claude Desktop's config unchanged, so a server you have already set up there needs nothing new. The Grok web app and X integration do not take custom servers. Grok docs

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what the server actually exposes, not what its listing claims.

Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.