Is the Omniwatchguard MCP server down?

mcp-registry/com.omniwatchguard/mcp · v1.0.0

Also listed as glama/isoprest/omniwatchguard-mcp

healthy
Last checked 2026-10-18 19:47 UTC · handshake 324ms

As of 2026-10-18 19:47 UTC, the Omniwatchguard MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
3,669
outages (90d)
0
tools
7

AI-powered website change monitoring - manage monitors and alerts via MCP.

Install Omniwatchguard MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http omniwatchguard-mcp-server https://mcp.omniwatchguard.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "omniwatchguard-mcp-server": {
      "type": "http",
      "url": "https://mcp.omniwatchguard.com/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (78/100)

C (78/100): 0 error(s), 3 warning(s) across 7 tool(s); ~1,072 tokens of tool definitions.
Scores higher than 30% of 15,312 MCP servers Glimind has audited.
Its tool list costs an agent ~1,072 tokens per session — lighter than 75% of servers.
78 → 78 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints0
Token cost100
Client compatibility70
Protocol100
Reliability85
Stability76

What to fix (5)

7 of 7 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: create_monitor, delete_monitor, get_monitor, list_alerts, list_monitors and 2 more

3 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: create_monitor, delete_monitor, update_monitor

Handshake + tools/list takes ~1,685 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 →

In the last 30 days: 0 tool(s) removed and 6 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →

Auto-fix: 7 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.omniwatchguard%2Fmcp/fixes

create_monitor 1 change
{
  "name": "create_monitor",
  "description": "Create a new monitor for a web page. Types: text, price, stock, css, api, seo, ssl (tech_stack and whois need the matching add-on). The number of monitors and the available check intervals depend on the user's plan.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "url"
    ],
    "properties": {
      "url": {
        "type": "string",
        "description": "Full URL of the page to monitor"
      },
      "name": {
        "type": "string",
        "description": "Display name for the monitor (default: the domain of the URL)"
      },
      "type": {
        "type": "string",
        "description": "Monitor type: text, price, stock, css, api, seo or ssl. Default: text"
      },
      "selector": {
        "type": "string",
        "description": "Optional CSS selector that limits monitoring to one element of the page (used with type css)"
      },
      "frequency": {
        "type": "number",
        "description": "Check interval in minutes: 60 on Starter; 15, 30 or 60 on Pro; 5, 15, 30 or 60 on Agency"
      },
      "notify_telegram": {
        "type": "string",
        "description": "Telegram chat ID for this monitor's alerts (Agency plan)"
      },
      "stock_alert_type": {
        "type": "string",
        "description": "For type=stock: 'any', 'in_stock' or 'out_of_stock'"
      },
      "price_threshold_type": {
        "type": "string",
        "description": "For type=price: 'any', 'increase' or 'decrease'"
      },
      "price_threshold_value": {
        "type": "number",
        "description": "Price threshold that triggers an alert"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
delete_monitor 1 change
{
  "name": "delete_monitor",
  "description": "Delete an existing monitor.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "id"
    ],
    "properties": {
      "id": {
        "type": "number",
        "description": "Monitor ID"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": true,
    "idempotentHint": true
  }
}
get_monitor 1 change
{
  "name": "get_monitor",
  "description": "Get the full details of one monitor and its last 20 check results.",
  "inputSchema": {
    "type": "object",
    "$schema": "https://json-schema.org/draft/2020-12/schema",
    "required": [
      "id"
    ],
    "properties": {
      "id": {
        "type": "number",
        "description": "Monitor ID"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

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.omniwatchguard/mcp"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.omniwatchguard/mcp"}) 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.omniwatchguard%2Fmcp.svg)](https://glimind.com/server/mcp-registry%2Fcom.omniwatchguard%2Fmcp?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fcom.omniwatchguard%2Fmcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.omniwatchguard%2Fmcp.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.omniwatchguard%2Fmcp.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.omniwatchguard%2Fmcp?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:36c9a4bfc4f5a7ce…, first seen 2026-10-17, included at leaf 3015 of 23,218. Version history · verify what your client received.

Tools (7)

Compare: most reliable data servers · most reliable devops servers · most reliable communication 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 Omniwatchguard MCP server down right now?

As of 2026-10-18 19:47 UTC, the Omniwatchguard MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Omniwatchguard MCP server provide?

Omniwatchguard MCP server advertises 7 tools, including create_monitor, delete_monitor, get_monitor, list_alerts, list_monitors.

How do I install Omniwatchguard MCP server?

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

Is the Omniwatchguard MCP server safe to connect to an AI agent?

Glimind scanned all 7 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 Omniwatchguard 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.