io.github.oijusti/k8s-port-forward-mcp
io.github.oijusti/k8s-port-forward-mcp
Is the io.github.oijusti/k8s-port-forward-mcp MCP server down? Yes. It has given no valid answer since 2026-10-19: not found.
Kubernetes Port Forward — MCP Server: port-forward Kubernetes services with terminal integration
not found down since 2026-10-19 · probed 2026-11-15 · unchanged since 2026-10-26
npm error notarget In most cases you or one of your dependencies are requesting npm error notarget a package version that doesn't exist. npm error A complete lo
- Run it
- npx -y k8s-port-forward-mcp@0.0.8 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/oijusti/k8s-port-forward-mcp
- Registry
- active, updated 2026-02-24 · registry entry
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- io.github.ohad6k/viberaven · alive
- StoQuant — Quantitative Stock Research io.github.ohadf2015/stoquant-mcp · needs env
- Groundlink io.github.ohhavefun/groundlink · alive
- io.github.ohvenkat/hostinger-ssh-mcp · alive
- Ovellum io.github.oinam/ovellum · alive
- io.github.ok0/korean-parenting-mcp · alive
- Microsoft 365 Admin io.github.okapi-ca/ms-365-admin · needs env
- io.github.oktopeak/clio-mcp · needs env
Servers that mention forward.
- hood. — .hood name service ag.hood/name-service · alive
- em[ai]l ai.eml/email · needs your URL
- ai.sentfrom/mcp · needs auth
- Uruguay Invoices (DGI e-Factura CFE, merchant-signed SOAP relay) app.wishpool/uruguay-invoice-mcp · no DNS
- CurrencyGuard Guard Pricing com.currencyguard/guard-pricing · alive
- com.fbaforwarders/site · alive
- com.freightforwarderfinder/site · alive
- General Index com.general-index/gx-mcp · needs auth
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- No valid answer since 2026-10-19, in every probe since then.
- The endpoint answers HTTP 404. The registry entry points to a URL that is not an MCP endpoint any more. Publish a new version of the registry entry with the current URL.