omniwatchguard.com MCP server
com.omniwatchguard/mcpomniwatchguard.comstreamable-httpv1.0.0Scanned
AI-powered website change monitoring - manage monitors and alerts via MCP.
7 tools: 1 can delete or cancel things, 3 change things and 3 only read.
- Reads private data · 1
- Reads text others write · 1
- Can send data out · 2
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here can delete or cancel things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the omniwatchguard.com MCP server can do
The omniwatchguard.com MCP server is published by omniwatchguard.com, a domain the MCP Registry verified. It has 7 tools. It can delete or cancel things (1 tool: delete_monitor) and create or change data (3 tools: create_monitor, update_monitor and set_monitor_status). 3 tools only read.
1 tool reads private data (list_alerts); 1 tool brings in text other people can write (list_alerts); 2 tools can send data out of your system (create_monitor and update_monitor). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 10, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
7 tools
Deletes or cancels 1Claude Code: deny
delete_monitorDelete an existing monitor.No findings
Why it is in this group
- The name "delete_monitor" says "delete": a word for removing or ending something.
Description, as the server wrote it Delete an existing monitor.
Changes things 3Claude Code: ask
create_monitorCreate a new monitor for a web page.Can send data outNo findings
Why it is in this group
- The name "create_monitor" says "create": a word for a change.
What it can reach
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it 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.
set_monitor_statusPause or resume an existing monitor.No findings
Why it is in this group
- The name "set_monitor_status" says "set": a word for a change.
Description, as the server wrote it Pause or resume an existing monitor.
update_monitorUpdate fields of an existing monitor: name, URL, selector, check interval or price/stock thresholds.Can send data outNo findings
Why it is in this group
- The name "update_monitor" says "update": a word for a change.
What it can reach
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it Update fields of an existing monitor: name, URL, selector, check interval or price/stock thresholds.
Only reads 3Show 3 read-only tools
get_monitorGet the full details of one monitor and its last 20 check results.No findings
Why it is in this group
- The name "get_monitor" says "get": a word for reading.
Description, as the server wrote it Get the full details of one monitor and its last 20 check results.
list_alertsList the latest alerts sent to the user (email, webhook, Slack, Discord, Telegram), with details of the change that triggered each one.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "list_alerts" says "list": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "email": it reads mail.
- untrusted-inputThe description's first sentence says "list" and "email": it reads inbound email, which other people can write.
Description, as the server wrote it List the latest alerts sent to the user (email, webhook, Slack, Discord, Telegram), with details of the change that triggered each one.
list_monitorsList all OmniWatchGuard monitors of the authenticated user, with the number of changes in the last 7 days and the last detected change.No findings
Why it is in this group
- The name "list_monitors" says "list": a word for reading.
Description, as the server wrote it List all OmniWatchGuard monitors of the authenticated user, with the number of changes in the last 7 days and the last detected change.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
2 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 untrusted-input tool breaks every one.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out2
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
{
"permissions": {
"deny": [
"mcp__omniwatchguard__list_alerts"
]
}
}Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:43 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 4
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 4 tools that change things (1 destructive, 3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.omniwatchguard.com/mcp: tools/list returned 7 tools to an anonymous client, including delete_monitor (destructive), create_monitor (write), update_monitor (write), set_monitor_status (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http omniwatchguard https://mcp.omniwatchguard.com/mcp --header 'Authorization: <your-authorization>'claude mcp add --transport http omniwatchguard https://mcp.omniwatchguard.com/mcp --header 'Authorization: <your-authorization>'Run in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__omniwatchguard__list_monitors",
"mcp__omniwatchguard__get_monitor",
"mcp__omniwatchguard__list_alerts"
],
"ask": [
"mcp__omniwatchguard__create_monitor",
"mcp__omniwatchguard__update_monitor",
"mcp__omniwatchguard__set_monitor_status"
],
"deny": [
"mcp__omniwatchguard__delete_monitor"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as omniwatchguard. Review it before you use it.
Capability tags behind 3 rules
- mcp__omniwatchguard__create_monitor outbound
- mcp__omniwatchguard__update_monitor outbound
- mcp__omniwatchguard__list_alerts private-data, untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.omniwatchguard/mcp/verify?hash=fefd907594d71eee0cd935f0a6d150bb389d604b24e21f02a34b6d4ffa040647" | jq -e '.changed == false'Pinned hash fefd907594d7, from Nov 10, 2026, 22:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.omniwatchguard/mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.omniwatchguard/mcp)Source: MCP Registry · repository. Synced Oct 21, 2026, 17:59 UTC.
omniwatchguard.com MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the omniwatchguard.com MCP server safe?
- No scan can promise that. What its definitions show: 7 tools, 4 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the omniwatchguard.com MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: delete_monitor.
Can the omniwatchguard.com MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the omniwatchguard.com MCP server have?
- 7 tools: 1 destructive, 3 write, 3 read. delete_monitor, create_monitor, update_monitor, set_monitor_status, list_monitors, get_monitor and list_alerts.
Does the omniwatchguard.com MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the omniwatchguard.com MCP server send data to outside services?
- 2 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): create_monitor and update_monitor.
Has the omniwatchguard.com MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.