Fortigate Readonly MCP Server

fortigate-readonly-mcp PyPI v0.2.0

Published by picaresco — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

Local read-only MCP server for Fortigate administration over SSH

Trust grade
A
99/100
Last scanned get badge →
Trust
A · 99/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Minimal
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 99/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 1 = 99. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 37

Each tool and what it can reach — statically extracted from the published source.

  • fortigate_compare_snapshotsno sensitive capability
  • fortigate_explain_flowno sensitive capability
  • fortigate_export_readonly_snapshotno sensitive capability
  • fortigate_find_policy_by_ipno sensitive capability
  • fortigate_find_policy_for_flowno sensitive capability
  • fortigate_get_admin_access_surfaceno sensitive capability
  • fortigate_get_auth_attack_summaryno sensitive capability
  • fortigate_get_dynamic_routing_statusno sensitive capability
  • fortigate_get_external_attack_surfaceno sensitive capability
  • fortigate_get_firewall_policiesno sensitive capability
Show 27 more tools ↓
  • fortigate_get_interface_healthno sensitive capability
  • fortigate_get_interfacesno sensitive capability
  • fortigate_get_ipsec_vpnsno sensitive capability
  • fortigate_get_local_in_policyno sensitive capability
  • fortigate_get_nat_overviewno sensitive capability
  • fortigate_get_policy_risk_summaryno sensitive capability
  • fortigate_get_policy_routesno sensitive capability
  • fortigate_get_proxy_policy_overviewno sensitive capability
  • fortigate_get_public_exposureno sensitive capability
  • fortigate_get_recent_errorsno sensitive capability
  • fortigate_get_routesno sensitive capability
  • fortigate_get_sdwan_statusno sensitive capability
  • fortigate_get_security_profiles_overviewno sensitive capability
  • fortigate_get_ssl_vpn_lan_connectionsno sensitive capability
  • fortigate_get_ssl_vpn_usersno sensitive capability
  • fortigate_get_system_statusno sensitive capability
  • fortigate_get_traffic_controlsno sensitive capability
  • fortigate_get_vpn_error_summaryno sensitive capability
  • fortigate_get_vpn_overviewno sensitive capability
  • fortigate_list_allowed_commandsno sensitive capability
  • fortigate_lookup_route_for_ipno sensitive capability
  • fortigate_run_audit_readonlyno sensitive capability
  • fortigate_run_readonly_commandno sensitive capability
  • fortigate_search_logsno sensitive capability
  • fortigate_search_traffic_logsno sensitive capability
  • fortigate_sniff_packetsno sensitive capability
  • fortigate_trace_sessionno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.2.0 latest A 99/100 0 1.12.1 2026-07-27

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 99/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/fortigate-readonly-mcp/badge.svg)](https://mcptrustchecker.com/registry/fortigate-readonly-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/fortigate-readonly-mcp"><img src="https://mcptrustchecker.com/registry/fortigate-readonly-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/fortigate-readonly-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan fortigate-readonly-mcp --online --registry pypi

Use the free API → How scoring works

More in Files & Storage