MCP servers › io.github.VoxNode-ux › nullwire-mcp
MCP server · registry snapshot 2026-10-28 · last checked 2026-10-28
nullwire-mcp MCP server
Registry name io.github.VoxNode-ux/nullwire-mcp
by VoxNode-ux · GitHub account (the registry's namespace rule)repository: same ownerSource ↗
RAM-only HTTP debugging proxy and MCP server in Go. AI agents see salted tags, never secrets. — the publisher's description
Summary
io.github.VoxNode-ux/nullwire-mcp is an MCP server listed in the official MCP registry at version 1.0.2, under the namespace of the GitHub account VoxNode-ux. Its linked repository, github.com/VoxNode-ux/nullwire-mcp, belongs to the same GitHub account.
Record checks
3 of 4 record checks met · 4 do not apply · 1 not checked
- not met: Registry entry is active and says how to run it
- met: Source repository link opens
- met: Repository is not archived
- met: Code pushed to the repository in the 90 days before our check
- not checked: Repository publishes a security policy (SECURITY.md)
- not applicable: Package names its licence with a standard (SPDX) identifier
- not applicable: The version the registry lists can be installed and is not withdrawn
- not applicable: npm package carries build provenance (attestation)
- not applicable: No known critical or high advisory in the package or its dependencies
- Not ranked by downloads: not an npm or PyPI package
- Not ranked by stars: 0 stars (ranked from 10)
From public records, not a safety rating. Each check with its reason · Is it safe to install?
Operate this server? Correct a fact · README badge · Run the checks yourself
Key facts
- Repository
- public
- Last tested
- not tested
Tool list
Not read: The registry entry declares no package and no remote endpoint, so there is nothing to run. So there is no tool-list size and no result from the three APIs.
How fresh this is
- Live-tested
- no
- Last tested
- not tested
- Latest version
- 1.0.2, published 2026-10-28 (registry, as of the 2026-10-28 snapshot)
- First listed version
- 2026-10-26 (earliest version still in the registry; older removed versions would be earlier)
- Version history
- 3 versions listed, 2026-10-26 to 2026-10-28; 3 in the 90 days before the 2026-10-28 snapshot.(versions still listed in the registry only)
Most recent 3 versions
1.0.2· 2026-10-281.0.1· 2026-10-281.0.0· 2026-10-26
- Registry data
- snapshot 2026-10-28
- Package and repository
- checked 2026-10-28
Dead or stale signals
None found in the records we hold
Looked for and not found: deprecated in the registry; repository link does not open; repository archived; no push in over 365 days. Does not apply: listed version cannot be installed or is withdrawn. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.
Changes since the last refresh
Version 1.0.0 (published 2026-10-26) → 1.0.2 (published 2026-10-28), between the registry lists of 2026-10-27 and 2026-10-28.
The publisher’s GitHub release note for v1.0.2, published 2026-10-28.
Read the release note (the publisher’s text, shown as plain text)
# NullWire-MCP v1.0.2 **The recommended stable release.** NullWire-MCP is a RAM-only HTTP debugging proxy and MCP server written in Go. AI agents see salted tags, never raw secrets. ## What's Changed - **Fixed:** the program now correctly reports its version as `1.0.2`. v1.0.1 still reported `1.0.0`. - **Signed build provenance:** every release binary now includes a signed attestation, so you can verify it came from this repository's CI. - **Reproducible builds:** all CI build tools and the Scorecard image are pinned to exact versions. ## Highlights - **Zero third-party dependencies:** pure Go standard library, built with Go 1.26. - **RAM-only:** a 50-slot circular buffer with zero disk writes. - **Salted SHA-256 correlation tags:** secrets are replaced with tags like `[REDACTED_TOKEN#xxxxxx]`, using a per-process nonce. Agents can see that a credential was reused without ever seeing its value. - **Dual-spec MCP support:** the `2026-07-28` stateless specification, plus legacy `2025-11-25` and `2024-11-05` handshakes. - **9 prebuilt static binaries:** Linux (amd64, arm64, armv7, riscv64), macOS (amd64, arm64), Windows (amd64, arm64) and FreeBSD (amd64). ## Verify your download - Checksums: compare against `SHA256SUMS.txt`. - Provenance: run `gh attestation verify <file> --repo VoxNode-ux/nullwire-mcp`. - An SBOM (`nullwire-sbom.cdx.json`) is attached. ## Upgrading v1.0.0 and v1.0.1 are superseded. v1.0.0 was built with Go 1.23, which has known standard-library vulnerabilities. Please upgrade to v1.0.2. **Full Changelog:** [v1.0.1...v1.0.2](https://github.com/VoxNode-ux/nullwire-mcp/compare/v1.0.1...v1.0.2)
Source: the official MCP Registry list on 2026-10-27 and on 2026-10-28; release notes from the GitHub Releases API, checked 2026-10-28.
What it is
Does the registry listing match what we found?
Feature #6The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.
| Registry says | We found | Result | Source · date |
|---|---|---|---|
| Repository github.com/VoxNode-ux/nullwire-mcp | Opens publicly | matches | api.github.com · 2026-10-28 |
Who made it?
Feature #7 · lineage
Facts about the publisher. We do not turn them into a trust score.
- Namespace
- io.github.VoxNode-ux
- GitHub owner
- a personal account (VoxNode-ux)
- Repository
- github.com/VoxNode-ux/nullwire-mcp
- Stars
- 0
- Repository age
- 0–30 days
- Last push
- 0–30 days ago
- Archived
- no
Source: the registry entry and api.github.com · 2026-10-28.
Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.
Choosing
Record checks
Public records · not a safety rating3 of 4 record checks met · 4 do not apply · 1 not checked
- Not ranked by downloads: not an npm or PyPI package
- Not ranked by stars: 0 stars (ranked from 10)
- Not metRegistry entry is active and says how to run itThe entry lists no package and no remote address, so a client cannot run it.What changes this check: This check reads the registry entry's status and whether it lists a package or a remote address. Marking an entry deprecated is the publisher's own choice. The registry's documentation says a published version's metadata cannot be changed; a new server.json with a unique version string is how an entry is updated. Versioning published MCP servers
- MetSource repository link opensThe linked GitHub repository is public.
- MetRepository is not archivedNot archived.
- MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
- Not checkedRepository publishes a security policy (SECURITY.md)We did not read this repository's security policy.
- Does not applyPackage names its licence with a standard (SPDX) identifierThe entry lists no package.
- Does not applyThe version the registry lists can be installed and is not withdrawnThe entry lists no package.
- Does not applynpm package carries build provenance (attestation)The entry lists no package.
- Does not applyNo known critical or high advisory in the package or its dependenciesThe entry lists no package.
Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-28. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral
Common questions about io.github.VoxNode-ux/nullwire-mcp
Answered from the data aboveWho publishes io.github.VoxNode-ux/nullwire-mcp?
The registry ties the namespace io.github.VoxNode-ux to the GitHub account VoxNode-ux; only its owner can publish under it. Its linked repository, github.com/VoxNode-ux/nullwire-mcp, belongs to the same GitHub account. These are facts from the registry and GitHub, not a rating.
Is io.github.VoxNode-ux/nullwire-mcp safe to install?
We do not rate servers as safe or unsafe. 3 of its 4 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.
Has io.github.VoxNode-ux/nullwire-mcp been security tested?
No. The registry entry declares no package and no remote endpoint, so there is nothing to run.
Where is the source code of io.github.VoxNode-ux/nullwire-mcp?
In github.com/VoxNode-ux/nullwire-mcp, which opens publicly.
Found this page useful?
Anonymous · no sign-inA quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.
Compare with another server
Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.
Security testing
Has it been tested?
Feature #1The registry entry declares no package and no remote endpoint, so there is nothing to run. — the server's own choice
Reference
How is it classified?
18 fields
One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.
“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.
Cite or correct this page
Sources and corrections
Suggested citation
ProtocolProbe. “io.github.VoxNode-ux/nullwire-mcp: MCP server record.” Data checked 2026-10-28. https://protocolprobe.com/mcp/servers/io.github.VoxNode-ux/nullwire-mcp
Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.
As JSON: this record in the API · API documentation.
Badge for your README
[](https://protocolprobe.com/mcp/servers/io.github.VoxNode-ux/nullwire-mcp)
It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.
Something wrong, or is this yours?
If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.
Write to hello@protocolprobe.com · corrections log · methodology