io.github.txn2/kubefwd

Is the io.github.txn2/kubefwd MCP server down? It gave no valid answer in the probe of 2026-11-11: crashed on start. One failed probe is not an outage.

Kubernetes port forwarding for local development with automatic /etc/hosts entries.

crashed on start no valid answer since 2026-11-11 · probed 2026-11-14 · unchanged since 2026-11-11

MCP error -32000: Connection closed
/work/bundle/kubefwd: 1: Syntax error: ")" unexpected

Bundle: https://github.com/txn2/kubefwd/releases/download/v1.25.18/kubefwd-1.25.18-darwin-arm64.mcpb (MCPB, for a client that installs bundles; probed in a container with the network off)
Host: github.com
Repository: https://github.com/txn2/kubefwd
Registry: active, updated 2026-10-16 · registry entry

Compare this server with others.

More servers

Other registry entries on github.com, the ones next to this name; all of them.

Code Index io.github.trondhindenes/code-index-mcp · crashed on start
io.github.tuannvm/mcp-trino · install failed
tunnels.io io.github.tunnels-io/tunnels-mcp · needs args
Parrot io.github.turantekin/parrot · crashed on start
io.github.txn2/mcp-datahub · crashed on start
io.github.txn2/mcp-trino · crashed on start
Obsidian MCP Server io.github.tylern91/obsidian-mcp-server · needs env
Envelope io.github.tymrtn/envelope · needs env

Servers that mention development or forwarding.

agency.lona/trading · needs auth
Projectory ae.projectory/mcp · alive
BeatBandit MCP ai.beatbandit/beatbandit · needs auth
OpenMandate ai.openmandate/mcp · alive
Synthetic Data — Random User ai.saifs/synthetic-data-random-user · needs auth
ai.smithery/devbrother2024-typescript-mcp-server-boilerplate · not found
ai.smithery/exa-labs-exa-code-mcp · not found
SSearch cc.ssearch/search · alive

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.

Atom feed

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

The package did not start as an MCP server at its probe on 2026-11-11. One failed probe is not an outage: the board calls a package down when it fails again at its next probe, a week later.
The process exited on start before it answered initialize. The error output is above.