← Index

Fortinet MCP

io.github.Servosity/fortinet-mcpv0.1.1Other

Audit every client FortiGate for firmware, SSL-VPN exposure, admin accounts and license expiry.

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 Other by this index, and declares 13 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 Fortinet 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-14 21:05 UTC
screened 2026-10-15tier: scannedgranularity: description-levelsource: registry

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

mcpindex.integrity.descriptionpassINFO

evidence“Tool audits FortiGate firmware, SSL‑VPN, admin accounts, license expiry.”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
  • - The registry listing (version, packages, links) changed after this screen ran - the description we assessed did not

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-20).

Contracts can change after screening, with no version bump. The gate pins Fortinet 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 Fortinet MCP](https://mcpindex.ai/server/io-github-servosity-fortinet-mcp) - screening verdict, registry provenance, and contract drift monitoring.
HTML
<a href="https://mcpindex.ai/server/io-github-servosity-fortinet-mcp">Independent trust record for Fortinet 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-fortinet-mcp)](https://mcpindex.ai/server/io-github-servosity-fortinet-mcp)
HTML
<a href="https://mcpindex.ai/server/io-github-servosity-fortinet-mcp"><img src="https://mcpindex.ai/api/v1/badge/io-github-servosity-fortinet-mcp" alt="mcpindex verdict" height="20" /></a>
Environment variables
FORTINET_BASE_URL
required

Your FortiGate's REST API root, e.g. https://203.0.113.10:8443/api/v2.

FORTINET_API_TOKEN
requiredsecret

The FortiGate REST API admin token (System > Administrators > Create New > REST API Admin). Use a read-only admin profile.

FORTINET_DEVICES

Optional. Path to a devices.toml listing every FortiGate the fleet, audit and policies hygiene commands check, each with a token_file. Leave blank to check only the FortiGate above.

FORTINET_FMG_URL

Optional. https://<fortimanager> for the read-only fmg commands. Leave blank if you do not use FortiManager.

FORTINET_FMG_API_KEY
secret

Optional. API key of a FortiManager REST API admin (FortiManager 7.2.2 or later) for the fmg commands.

FORTINET_CLOUD_API_USER

Optional. FortiCloud IAM API user (with FortiGate Cloud portal permission) for the read-only cloud commands.

FORTINET_CLOUD_API_PASSWORD
secret

Optional. Password of the FortiCloud IAM API user. Repeated failed logins lock the FortiCloud account for 15-30 minutes.

FORTINET_CLOUD_REGION

Optional. global (default), us, eu or jp: the region your FortiGates were provisioned in.

FORTINET_CLOUD_ACCOUNT_ID

Optional. Required only when FortiCloud Organizations are enabled.

FORTINET_MCP_READ_ONLY

Optional. Set to 1 to expose only read-only mirrored tools and refuse any non-GET execute call.

FORTINET_MCP_HTTP_TOKEN
secret

Required only when running the MCP server with --transport http (a remote/hosted deployment); callers must send a matching Authorization: Bearer header. Not needed for the default local stdio transport Claude Desktop uses.

FORTINET_USER_AGENT

Optional. Overrides the User-Agent the CLI sends to your FortiGates. Leave blank to use the built-in one.

PRINTING_PRESS_CLIENT_PROFILE
secret

Only used when the MCP server is bound to a tenant-gated client profile. This connector registers no tenant-gated source, so leave it blank.

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