SSyncDev

NullWire MCP Server

A loopback HTTP debugging proxy that shows your AI assistant recent traffic with tokens and keys scrubbed out.

Local server

What is the NullWire MCP Server?

Debugging a failed API call with an AI assistant usually means pasting the request, and the request usually carries a Bearer token. NullWire takes the pasting out of the loop. The NullWire MCP server runs a proxy on your machine, records what passes through, scrubs the recorded copy and lets the assistant read only that cleaned version.

Live traffic is forwarded untouched. Only a couple of negotiation headers change, so the behaviour you are debugging stays the behaviour you get.

Three tools, deliberately few

  • inspect_traffic returns recent scrubbed flows, filtered by limit (1 to 50), method or url_filter
  • export_sanitized_curl rebuilds a captured request as a curl command, with redacted values swapped for environment variables such as NULLWIRE_AUTH_TOKEN
  • clear_ram_buffer empties the buffer and resets counters

Redacted values become tags like [REDACTED_TOKEN#a1b2c3]. The tag is a salted hash, stable within one run, so the assistant can tell two requests used the same token without ever learning it. Restarting changes the salt.

How traffic reaches it

Mode Assistant sees
Forward proxy for http:// URLs full request and response, scrubbed
HTTPS via CONNECT only host, timing and byte counts
Reverse gateway with -target full HTTPS content; NullWire makes the TLS connection
WebSocket upgrade text frames both ways, recorded when the socket closes

There is no certificate-based interception. If you need HTTPS bodies, point your app's base URL at the reverse gateway, which can also route named upstreams by path prefix.

What gets scrubbed

Twelve layers run in order: PEM private keys, secret-named JSON and query fields, XML elements, credentials in URLs, Bearer and Basic auth, JWTs, more than 200 vendor key prefixes, secrets inside base64, IP addresses, your own regexes and a randomness detector for unknown key formats. A JSON config passed with -secrets-config adds headers, patterns or ignored URLs.

Installing

It is a single static Go binary with no dependencies. The npx -y nullwire-mcp launcher fetches and checksum-verifies it, and packages exist for winget, Chocolatey, Homebrew, Scoop, pipx, Nix, Docker and the common Linux formats. Running nullwire-mcp install --client all --dry-run previews config changes across Claude Desktop, Claude Code, Cursor, Windsurf, VS Code and others before writing anything. The proxy listens on 127.0.0.1:8080 unless you change -port.

Where it stops

Redaction is pattern-based, so an unusual low-entropy secret can slip through, and the detector may hide harmless long IDs. Only the last 50 flows are kept. Brotli and Zstd request bodies are refused with a 415. Upstream connections use HTTP/1.1, so HTTP/2 and gRPC bodies are not captured.

For packet-level work, a Wireshark server goes deeper, and Chrome DevTools covers browser-side requests. More tools are in networking and diagnostics.

Recorded tools

Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.

ToolWhat it does
inspect_trafficReturn recent scrubbed flows; accepts limit (1 to 50, default 10), method and url_filter.
export_sanitized_curlRebuild a captured request as a curl command with redacted values replaced by environment variables. Requires flow_id.
clear_ram_bufferClear all 50 buffer slots and reset the redaction counters.

How to install the NullWire MCP Server

{
  "mcpServers": {
    "nullwire": {
      "command": "/path/to/nullwire-mcp",
      "args": [
        "-port",
        "8080"
      ]
    }
  }
}

Replace /path/to/nullwire-mcp with the installed binary. Alternatively run nullwire-mcp install --client claude-desktop to write the entry for you, then restart the client.

Frequently asked questions

Through the reverse gateway, yes: start it with -target and point your app's base URL at 127.0.0.1:8080. Plain HTTPS through the forward proxy is tunnelled blind, showing only host, timing and byte counts.