Nginx Manager MCP Server

@kognar/nginx-manager-mcp-server npm v0.1.3

Published by @kognar — 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.

MCP server wrapping the Nginx Proxy Manager API

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/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
Moderate
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 = 96/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 − 4 = 96. 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
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−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 54

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

  • npm_create_userreads sensitive data
  • npm_get_audit_logingests untrusted input
  • npm_set_user_passwordreads sensitive data
  • npm_create_access_listno sensitive capability
  • npm_create_certificate_customno sensitive capability
  • npm_create_certificate_letsencryptno sensitive capability
  • npm_create_dead_hostno sensitive capability
  • npm_create_proxy_hostno sensitive capability
  • npm_create_redirection_hostno sensitive capability
  • npm_create_streamno sensitive capability
Show 44 more tools ↓
  • npm_delete_access_listno sensitive capability
  • npm_delete_certificateno sensitive capability
  • npm_delete_dead_hostno sensitive capability
  • npm_delete_proxy_hostno sensitive capability
  • npm_delete_redirection_hostno sensitive capability
  • npm_delete_streamno sensitive capability
  • npm_delete_userno sensitive capability
  • npm_disable_dead_hostno sensitive capability
  • npm_disable_proxy_hostno sensitive capability
  • npm_disable_redirection_hostno sensitive capability
  • npm_disable_streamno sensitive capability
  • npm_enable_dead_hostno sensitive capability
  • npm_enable_proxy_hostno sensitive capability
  • npm_enable_redirection_hostno sensitive capability
  • npm_enable_streamno sensitive capability
  • npm_get_access_listno sensitive capability
  • npm_get_certificateno sensitive capability
  • npm_get_dead_hostno sensitive capability
  • npm_get_meno sensitive capability
  • npm_get_proxy_hostno sensitive capability
  • npm_get_redirection_hostno sensitive capability
  • npm_get_reports_hostsno sensitive capability
  • npm_get_settingno sensitive capability
  • npm_get_settingsno sensitive capability
  • npm_get_streamno sensitive capability
  • npm_get_userno sensitive capability
  • npm_healthno sensitive capability
  • npm_list_access_listsno sensitive capability
  • npm_list_certificatesno sensitive capability
  • npm_list_dead_hostsno sensitive capability
  • npm_list_proxy_hostsno sensitive capability
  • npm_list_redirection_hostsno sensitive capability
  • npm_list_streamsno sensitive capability
  • npm_list_usersno sensitive capability
  • npm_renew_certificateno sensitive capability
  • npm_set_user_permissionsno sensitive capability
  • npm_test_certificate_http_reachno sensitive capability
  • npm_update_access_listno sensitive capability
  • npm_update_dead_hostno sensitive capability
  • npm_update_proxy_hostno sensitive capability
  • npm_update_redirection_hostno sensitive capability
  • npm_update_settingno sensitive capability
  • npm_update_streamno sensitive capability
  • npm_update_userno sensitive capability

What this scan could not see

Versions 2

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.1.3 latest A 96/100 0 1.13.0 2026-09-07
v0.1.2 A 96/100 0 1.13.0 2026-09-01

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

Use the free API → How scoring works

More in Cloud & DevOps