Nginx Proxy Manager (PyPI) MCP Server

nginx-proxy-manager-mcp PyPI v2.14.0

Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

MCP server for managing Nginx Proxy Manager instances

Trust grade
A
98/100
Last scanned get badge →
Trust
A · 98/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 = 98/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 − 2 = 98. 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
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

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 50

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

  • create_access_listno sensitive capability
  • create_dead_hostno sensitive capability
  • create_proxy_hostno sensitive capability
  • create_redirection_hostno sensitive capability
  • create_streamno sensitive capability
  • create_userno sensitive capability
  • delete_access_listno sensitive capability
  • delete_certificateno sensitive capability
  • delete_dead_hostno sensitive capability
  • delete_proxy_hostno sensitive capability
Show 40 more tools ↓
  • delete_redirection_hostno sensitive capability
  • delete_streamno sensitive capability
  • delete_userno sensitive capability
  • disable_dead_hostno sensitive capability
  • disable_proxy_hostno sensitive capability
  • disable_redirection_hostno sensitive capability
  • disable_streamno sensitive capability
  • enable_dead_hostno sensitive capability
  • enable_proxy_hostno sensitive capability
  • enable_redirection_hostno sensitive capability
  • enable_streamno sensitive capability
  • get_access_listno sensitive capability
  • get_certificateno sensitive capability
  • get_dead_hostno sensitive capability
  • get_host_reportno sensitive capability
  • get_proxy_hostno sensitive capability
  • get_redirection_hostno sensitive capability
  • get_settingno sensitive capability
  • get_streamno sensitive capability
  • get_userno sensitive capability
  • list_access_listsno sensitive capability
  • list_audit_logno sensitive capability
  • list_certificatesno sensitive capability
  • list_dead_hostsno sensitive capability
  • list_dns_providersno sensitive capability
  • list_proxy_hostsno sensitive capability
  • list_redirection_hostsno sensitive capability
  • list_settingsno sensitive capability
  • list_streamsno sensitive capability
  • list_usersno sensitive capability
  • renew_certificateno sensitive capability
  • request_certificateno sensitive capability
  • test_http_challengeno sensitive capability
  • update_access_listno sensitive capability
  • update_dead_hostno sensitive capability
  • update_proxy_hostno sensitive capability
  • update_redirection_hostno sensitive capability
  • update_settingno sensitive capability
  • update_streamno sensitive capability
  • update_userno 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
v2.14.0 latest A 98/100 0 1.13.0 2026-08-25

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 · 98/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/nginx-proxy-manager-mcp-2/badge.svg)](https://mcptrustchecker.com/registry/nginx-proxy-manager-mcp-2)
HTML
<a href="https://mcptrustchecker.com/registry/nginx-proxy-manager-mcp-2"><img src="https://mcptrustchecker.com/registry/nginx-proxy-manager-mcp-2/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/nginx-proxy-manager-mcp-2/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 nginx-proxy-manager-mcp --online --registry pypi

Use the free API → How scoring works

Other implementations of Nginx Proxy Manager 1

Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →

More in Developer Tools