Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.omniwatchguard/mcp

REMOTE · MCP.OMNIWATCHGUARD.COM

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

0 this week 72 Trust /100

Last scanned (20 hours ago)

Scores higher than 57% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Monitoring and Observability

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security46
Transport & Reachability100
Schema Quality & AI Usability73
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 601 tokens (~85/item across 7 items; 7 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_monitor" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (11)

  • TLS certificate
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (2)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 10 Oct 26 0
    • Tool “create_monitor” rewrote its description, which is the text the model reads security
    • Tool “delete_monitor” rewrote its description, which is the text the model reads security
    • Tool “get_monitor” rewrote its description, which is the text the model reads security
    • Tool “list_alerts” rewrote its description, which is the text the model reads security
    • Tool “list_monitors” rewrote its description, which is the text the model reads security
    • Tool “set_monitor_status” rewrote its description, which is the text the model reads security
    • Tool “update_monitor” rewrote its description, which is the text the model reads security
    • Tool coverage: 68% → 100% ▲ functional
    • “create_monitor” reworded the description of “frequency” cosmetic
    • “create_monitor” reworded the description of “name” cosmetic
    • “create_monitor” reworded the description of “notify_telegram” cosmetic
    • “create_monitor” reworded the description of “price_threshold_type” cosmetic
    • “create_monitor” reworded the description of “price_threshold_value” cosmetic
    • “create_monitor” reworded the description of “selector” cosmetic
    • “create_monitor” reworded the description of “stock_alert_type” cosmetic
    • “create_monitor” reworded the description of “type” cosmetic
    • “create_monitor” reworded the description of “url” cosmetic
    • “delete_monitor” reworded the description of “id” cosmetic
    • “get_monitor” reworded the description of “id” cosmetic
    • “list_alerts” reworded the description of “type” cosmetic
    • “set_monitor_status” reworded the description of “id” cosmetic
    • “set_monitor_status” reworded the description of “status” cosmetic
    • “update_monitor” reworded the description of “frequency” cosmetic
    • “update_monitor” reworded the description of “id” cosmetic
    • “update_monitor” reworded the description of “name” cosmetic
    • “update_monitor” reworded the description of “price_threshold_type” cosmetic
    • “update_monitor” reworded the description of “price_threshold_value” cosmetic
    • “update_monitor” reworded the description of “selector” cosmetic
    • “update_monitor” reworded the description of “stock_alert_type” cosmetic
    • “update_monitor” reworded the description of “url” cosmetic
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://mcp.omniwatchguard.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=omniwatchguard.com CN=WE1,O=Google Trust Services,C=US 11 Oct 2026 9 Jan 2027 ECDSA 256 ECDSA-SHA256 bb2049b7e21e43e40e84adc93d946253
SANs: omniwatchguard.com, mcp.omniwatchguard.com, *.mcp.omniwatchguard.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.omniwatchguard.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
omniwatchguard.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.omniwatchguard.com/mcp Verified 200
http (plaintext) http://mcp.omniwatchguard.com/mcp Inconclusive 405
MCP tools · 7 exposed · ~601 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
create_monitor ~270

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.

NameTypeReqDescription
frequencynumber–Check interval in minutes: 60 on Starter; 15, 30 or 60 on Pro; 5, 15, 30 or 60 on Agency
namestring–Display name for the monitor (default: the domain of the URL)
notify_telegramstring–Telegram chat ID for this monitor's alerts (Agency plan)
price_threshold_typestring–For type=price: 'any', 'increase' or 'decrease'
price_threshold_valuenumber–Price threshold that triggers an alert
selectorstring–Optional CSS selector that limits monitoring to one element of the page (used with type css)
stock_alert_typestring–For type=stock: 'any', 'in_stock' or 'out_of_stock'
typestring–Monitor type: text, price, stock, css, api, seo or ssl. Default: text
urlstringyesFull URL of the page to monitor

No output schema declared.

No examples provided.

delete_monitor ~22

Delete an existing monitor.

NameTypeReqDescription
idnumberyesMonitor ID

No output schema declared.

No examples provided.

get_monitor ~32

Get the full details of one monitor and its last 20 check results.

NameTypeReqDescription
idnumberyesMonitor ID

No output schema declared.

No examples provided.

list_alerts ~50

List the latest alerts sent to the user (email, webhook, Slack, Discord, Telegram), with details of the change that triggered each one.

NameTypeReqDescription
typestring–Optional filter by alert channel

No output schema declared.

No examples provided.

list_monitors ~37

List all OmniWatchGuard monitors of the authenticated user, with the number of changes in the last 7 days and the last detected change.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

set_monitor_status ~37

Pause or resume an existing monitor.

NameTypeReqDescription
idnumberyesMonitor ID
statusstringyesNew status of the monitor

No output schema declared.

No examples provided.

update_monitor ~153

Update fields of an existing monitor: name, URL, selector, check interval or price/stock thresholds.

NameTypeReqDescription
frequencynumber–New check interval in minutes (allowed values depend on the plan)
idnumberyesMonitor ID
namestring–New display name
price_threshold_typestring–For price monitors: 'any', 'increase' or 'decrease'
price_threshold_valuenumber–For price monitors: threshold that triggers an alert
selectorstring–New CSS selector
stock_alert_typestring–For stock monitors: 'any', 'in_stock' or 'out_of_stock'
urlstring–New page URL

No output schema declared.

No examples provided.

Install

How do I install the com.omniwatchguard/mcp server?

com.omniwatchguard/mcp is a hosted endpoint at https://mcp.omniwatchguard.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.omniwatchguard.com

# add to Claude Code
claude mcp add --transport http com-omniwatchguard-mcp 'https://mcp.omniwatchguard.com/mcp'
Common questions

What is the com.omniwatchguard/mcp server?

com.omniwatchguard/mcp is listed in the public MCP registry as com.omniwatchguard/mcp. AI-powered website change monitoring - manage monitors and alerts via MCP. This page covers its hosted endpoint (https://mcp.omniwatchguard.com/mcp).

Is the com.omniwatchguard/mcp server safe to use?

com.omniwatchguard/mcp scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the com.omniwatchguard/mcp server expose?

com.omniwatchguard/mcp exposes 7 tools: list_monitors, get_monitor, create_monitor, update_monitor, set_monitor_status, and 2 more. Their descriptions and schemas cost roughly 601 tokens of context every time the server is loaded.

Does the com.omniwatchguard/mcp server require authentication?

No. We connected to com.omniwatchguard/mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the com.omniwatchguard/mcp server still maintained?

com.omniwatchguard/mcp is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the com.omniwatchguard/mcp server?

VerifyMCP ran 11 checks on com.omniwatchguard/mcp, covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about com.omniwatchguard/mcp: Authorization and HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.