← Index

WatchGuard MCP

io.github.Servosity/watchguard-mcpv0.1.1Security

WatchGuard Cloud Firebox, Endpoint Security, ThreatSync, NDR and AuthPoint APIs for every customer

The current version, v0.1.1, was published to the official MCP registry on 2026-10-16. It is distributed through a declared package, filed under Security by this index, and declares 12 environment variables. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; the index's current counts put this record in context.

In-path gate · all MCP tools

Using WatchGuard MCP in Claude, Cursor, Gemini CLI, Cline, or Zed?

MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).

Install the mcpindex gate (one command)

Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less

uv tool install mcpindex-gate && mcpindex-config-wire
Trust verdict · v1 advisory · method
REVIEWstatus: PARTIALfresh until 2026-11-15 19:08 UTC
screened 2026-10-16tier: scannedgranularity: description-levelsource: registry

Semantic screen found no manipulation pattern in the description. Conformance probe not yet run.

mcpindex.integrity.descriptionpassINFO

evidence“Tool provides WatchGuard security APIs for customers.”via static_description

Limits of this verdict
  • - Semantic screen only - the deterministic conformance probe has not run on this server
  • - Confidence is reported but not yet calibrated (v1)
  • - Screen reads the tool description, not the live behavior
  • - advisory
  • - registry description only no input schema
  • - screen model 8b

Semantic screen: an LLM judge reads the tool description for hidden instructions (status PARTIAL). A pass means the description is not lying, not that the tool is safe: a high-capability tool with an honest description still warrants caution. The deterministic conformance probe has not been run on this server yet, so the screen here is semantic-only. Posture: advisory. Confidences are reported but not yet calibrated (calibrated=false at v1). Full verdict history is not shown on this page.

Own this server? Test a description on the public screen → It is a separate check from the verdict above, so the two can differ.

That verdict was true at screening time (snapshot 2026-10-19).

Contracts can change after screening, with no version bump. The gate pins WatchGuard MCP’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.

See your first HOLD in 2 minutes →

Related: how to trust an MCP server · screen before install · silent contract drift

Cite this record

People vet a server before wiring it in. One line on your project site or docs answers that with an independent record: screening verdict, registry provenance, contract drift history. It stays current as new screens and drift events land.

Markdown
[Independent trust record for WatchGuard MCP](https://mcpindex.ai/server/io-github-servosity-watchguard-mcp) - screening verdict, registry provenance, and contract drift monitoring.
HTML
<a href="https://mcpindex.ai/server/io-github-servosity-watchguard-mcp">Independent trust record for WatchGuard MCP</a> - screening verdict, registry provenance, and contract drift monitoring.
Embed this badge

A live verdict badge for your README or listing. It reflects the current screen, links back here, and updates when the verdict does.

Markdown
[![mcpindex](https://mcpindex.ai/api/v1/badge/io-github-servosity-watchguard-mcp)](https://mcpindex.ai/server/io-github-servosity-watchguard-mcp)
HTML
<a href="https://mcpindex.ai/server/io-github-servosity-watchguard-mcp"><img src="https://mcpindex.ai/api/v1/badge/io-github-servosity-watchguard-mcp" alt="mcpindex verdict" height="20" /></a>
Environment variables
WATCHGUARD_CLIENT_ID
requiredsecret

WatchGuard Cloud API Access ID (read-write or read-only).

WATCHGUARD_CLIENT_SECRET
requiredsecret

Password for that Access ID.

WATCHGUARD_API_KEY
requiredsecret

WatchGuard Cloud API key (WatchGuard-API-Key header).

WATCHGUARD_ACCOUNT_ID
required

Your WatchGuard Cloud account ID (ACC-... or WGC-...).

WATCHGUARD_BASE_URL

Optional: region API base URL; default https://api.usa.cloud.watchguard.com (EMEA api.deu, APAC api.jpn).

WATCHGUARD_TOKEN_URL

Optional: region OAuth token URL; default https://api.usa.cloud.watchguard.com/oauth/token.

WATCHGUARD_AUDIENCE

Optional: a managed account's audience value; requests use that customer's token (not a security boundary).

WATCHGUARD_OAUTH_SCOPE

Optional: OAuth scope to request; default api-access.

WATCHGUARD_USER_AGENT

Optional: override the User-Agent the CLI sends.

WATCHGUARD_MCP_READ_ONLY

Optional: set to 1 to run the MCP server read-only.

WATCHGUARD_MCP_HTTP_TOKEN
secret

Bearer token callers must present when the server runs with --transport http; not used by the stdio transport.

PRINTING_PRESS_CLIENT_PROFILE

Not enforced by this connector (no tenant-gated profiles); leave unset. It does not limit which accounts a call can reach.

MCP quality score · maturity, not trust · methodology
freshness
25
completeness
20
installability
25
documentation
15
stability
5
Alternatives in Security