Ingress Nginx Retirement Lint MCP server

by jmshinhwa·io.github.jmshinhwa/ingress-nginx-retirement-lint·v1.0.1

Names the Gateway API field that replaces each retired ingress-nginx annotation — or tells you there

A89/100grade A

What users say

No reviews yet

Safety scan

A89/100

Adoption

New

0 stars

Reviews

Nobody has reviewed Ingress Nginx Retirement Lint yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

No tool declarations could be read from the package source. They show once the server is installed.

scanner v0.1.3 · 2026-09-19 · same rubric, same numbers if you re-run it

no findings

Code scan6 source files scanned25/25
–Live reliabilityno gateway calls yet and no remote to proben/a
–Tool poisoningtools not inspected (local package is not executed); not countedn/a
Auth qualitylocal package, no credentials required12/15
Maintenancelast push 0 days ago15/15
Maintainer identityregistry namespace matches repository owner6/10

Overall 89/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

Runs npx -y @readystack/ingress-nginx-retirement-lint on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add ingress-nginx-retirement-lint -- npx -y @readystack/ingress-nginx-retirement-lint

Is Ingress Nginx Retirement Lint MCP server safe?: Yes, by our scan: it is graded A (89/100). Read the Ingress Nginx Retirement Lint safety report
How do I install Ingress Nginx Retirement Lint?: It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
Does Ingress Nginx Retirement Lint need an API key?: Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Ingress Nginx Retirement Lint maintained?: The last commit was in the last day (2026-09-19). The latest release is v1.0.1.