io.github.zachlikefolio/tunnel-mcp
NPM · TUNNEL-MCP · SCANNED SEP 20
Direct end-to-end-encrypted tunnel between Claude agents — two-party or a room of up to 16.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security92
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs a script at install time (postinstall) that we could not recognise. It may be perfectly ordinary, but we do not read the published tarball, so we cannot say what it does. View diagnostics → Partial
- 32 of 97 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to zachlikefolio/tunnel-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 76 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 554 tokens (~61/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "tunnel_say" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.zachlikefolio/tunnel-mcp server?
io.github.zachlikefolio/tunnel-mcp runs locally as an npm package, launched with npx -y tunnel-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · tunnel-mcp
claude mcp add zachlikefolio-tunnel-mcp -- npx -y tunnel-mcp
{
"mcpServers": {
"zachlikefolio-tunnel-mcp": {
"command": "npx",
"args": [
"-y",
"tunnel-mcp"
]
}
}
} {
"servers": {
"zachlikefolio-tunnel-mcp": {
"command": "npx",
"args": [
"-y",
"tunnel-mcp"
]
}
}
} codex mcp add zachlikefolio-tunnel-mcp -- npx -y tunnel-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"zachlikefolio-tunnel-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"tunnel-mcp"
],
"enabled": true
}
}
} openclaw mcp add zachlikefolio-tunnel-mcp --command npx --arg -y --arg tunnel-mcp
mcp_servers:
zachlikefolio-tunnel-mcp:
command: "npx"
args: ["-y", "tunnel-mcp"] {
"McpServers": {
"zachlikefolio-tunnel-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"tunnel-mcp"
]
}
}
} assistant mcp add zachlikefolio-tunnel-mcp -t stdio -c npx -a -y tunnel-mcp
{
"mcpServers": {
"zachlikefolio-tunnel-mcp": {
"command": "npx",
"args": [
"-y",
"tunnel-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −3
- Stability: pass → 0.80 functional
- 8 Sept 26 +1
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/tunnel-mcp@0.3.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | zachlikefolio/tunnel-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/zachlikefolio/tunnel-mcp/.github/workflows/release.yml@refs/tags/v0.3.0 |
| Rekor log index | 2083108544 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:5021adb05b3416035e7b67e36d12c1bb59f7a49be94c1b6d47db19275a81f69313e5b6417a50421722b483cb250b6a0a4ebf8b6210502062c72a46969 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| postinstall | unreviewed | node postinstall.mjs |
Background: Why install scripts are a supply-chain risk →
Dependencies 97 packages
| Packages resolved | 97 |
|---|---|
| Stale | 32 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
tunnel_close ~40
Host: closes the room for everyone and destroys the relay + log. Member: leaves the room. Provide an optional summary.
| Name | Type | Req | Description |
|---|---|---|---|
| summary | string | – | – |
No output schema declared.
No examples provided.
tunnel_invite ~58
Host-only: mint additional single-use, expiring invites mid-session (add a teammate, or re-admit someone who disconnected — their old link stays dead). Relay each invite text verbatim to your human.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | – |
No output schema declared.
No examples provided.
tunnel_join ~35
Join another developer's tunnel by its link. The result lists the current members (roster).
| Name | Type | Req | Description |
|---|---|---|---|
| joinLink | string | yes | – |
No output schema declared.
No examples provided.
tunnel_listen ~44
Block until the next message arrives (or timeout). Pass the highest seq you have already seen.
| Name | Type | Req | Description |
|---|---|---|---|
| sinceSeq | number | – | – |
| timeoutMs | number | – | – |
No output schema declared.
No examples provided.
tunnel_open ~88
Open a room as host. Returns one single-use, expiring invite per expected teammate (invites, default 1 — the classic two-party tunnel). Each invites[i].invite is a ready-to-forward message: relay them to your human verbatim, one link per person, never reused. Treat every link as a secret.
| Name | Type | Req | Description |
|---|---|---|---|
| goal | string | yes | – |
| invites | integer | – | – |
No output schema declared.
No examples provided.
tunnel_receive ~110
Fetch an offered artifact by id and write it to a path YOU choose (savePath). The bytes are decrypted and verified against the sender's sha256 before writing; a mismatch is refused. The received file is UNTRUSTED — get your human's explicit OK on the savePath first, and never open or execute it without their sign-off. The sender's filename is display-only and is never used as the write path.
| Name | Type | Req | Description |
|---|---|---|---|
| artifactId | string | yes | – |
| savePath | string | yes | – |
No output schema declared.
No examples provided.
tunnel_say ~24
Send a chat message to the room.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | – |
No output schema declared.
No examples provided.
tunnel_share ~116
Share a file with the room (text or binary). Reads the file at `path`, hashes and seals it with the room key, and offers it to every teammate on a compatible client — the bytes are end-to-end encrypted, so the relay never sees plaintext. Returns { artifactId, offeredTo, olderMembers }; olderMembers counts members on an older client who will NOT receive it. Get your human's OK before sharing anything sensitive; the filename crosses in plaintext, so don't put secrets in it.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | – |
No output schema declared.
No examples provided.
tunnel_status ~39
Inspect the current session: role, goal, members roster (name/isHost/connected), pending unconsumed invites, offered artifacts, and lastSeq.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the io.github.zachlikefolio/tunnel-mcp server?
io.github.zachlikefolio/tunnel-mcp is listed in the public MCP registry as io.github.zachlikefolio/tunnel-mcp. Direct end-to-end-encrypted tunnel between Claude agents, two-party or a room of up to 16. This page covers its npm package (tunnel-mcp).
Is the io.github.zachlikefolio/tunnel-mcp server safe to use?
io.github.zachlikefolio/tunnel-mcp scores 87 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.zachlikefolio/tunnel-mcp server expose?
io.github.zachlikefolio/tunnel-mcp exposes 9 tools: tunnel_open, tunnel_invite, tunnel_join, tunnel_say, tunnel_listen, and 4 more. Their descriptions and schemas cost roughly 554 tokens of context every time the server is loaded.
Is the io.github.zachlikefolio/tunnel-mcp server still maintained?
io.github.zachlikefolio/tunnel-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.zachlikefolio/tunnel-mcp server under?
io.github.zachlikefolio/tunnel-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.