Nginx UI is a self-hosted web interface for managing and working with Nginx. Nginx operators use it to configure and administer their web servers through a browser, and the catalogue rules, instructions, and skill provide coding-agent guidance for that workflow.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/0xJacky/nginx-uiWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/0xjacky/nginx-ui/context7)<a href="https://agentmods.dev/mcp/0xjacky/nginx-ui/context7"><img src="https://agentmods.dev/badge/mcp/0xjacky/nginx-ui/context7/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/0xjacky/nginx-ui/context7"><img src="https://agentmods.dev/badge/mcp/0xjacky/nginx-ui/context7.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
context7 scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
The source is not reproduced here
Licensed AGPL-3.0
The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
What else mcp.json configures
This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 9 lines scan A 6f9d71bbe560
context7 is an MCP server published in the GitHub repository 0xJacky/nginx-ui (11,629 stars, last pushed today), licensed AGPL-3.0. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-08.
Other mcp servers, from other repositories
gomodel
MCP server "gomodel" as configured in ENTERPILOT/GoModel. Runs in Docker (docker.io/enterpilot/gomodel:0.1.98). Needs 2 environment variables to run.
graymatter
MCP server "graymatter" as configured in angelnicolasc/graymatter. Launched with graymatter mcp serve.
lsp
MCP server "lsp" as configured in blackwell-systems/agent-lsp. Launched with agent-lsp go:gopls.
chrome-devtools
Lets the agent inspect and automate a live Chrome instance through the DevTools protocol: performance traces, network, console. Runs locally from the chrome-devtools-mcp npm package.
chrome-devtools
Lets the agent inspect and automate a live Chrome instance through the DevTools protocol: performance traces, network, console. Runs locally from the chrome-devtools-mcp npm package.
linear-server
Linear's hosted MCP server: lets the agent read and update issues, projects and cycles. Remote server at mcp.linear.app.