rustunnel
OCI · GHCR.IO/JOAOH82/RUSTUNNEL-MCP:0.8.5 · 6 COMPONENTS · SCANNED SEP 21
Give AI agents public HTTPS/TCP/UDP URLs for any localhost service. Open source, self-hostable.
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 Security0
- Malware scan not yet available for this package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (AGPL-3.0).Pass
- Actively maintained (last published 16 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1191 tokens (~198/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
- Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the rustunnel MCP server?
rustunnel runs locally as a container image, launched with docker run --rm -i ghcr.io/joaoh82/rustunnel-mcp:0.8.5. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/joaoh82/rustunnel-mcp:0.8.5
claude mcp add joaoh82-rustunnel -- docker run --rm -i ghcr.io/joaoh82/rustunnel-mcp:0.8.5
{
"mcpServers": {
"joaoh82-rustunnel": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/joaoh82/rustunnel-mcp:0.8.5"
]
}
}
} {
"servers": {
"joaoh82-rustunnel": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/joaoh82/rustunnel-mcp:0.8.5"
]
}
}
} codex mcp add joaoh82-rustunnel -- docker run --rm -i ghcr.io/joaoh82/rustunnel-mcp:0.8.5
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"joaoh82-rustunnel": {
"type": "local",
"command": [
"docker",
"run",
"--rm",
"-i",
"ghcr.io/joaoh82/rustunnel-mcp:0.8.5"
],
"enabled": true
}
}
} mcp_servers:
joaoh82-rustunnel:
command: "docker"
args: ["run", "--rm", "-i", "ghcr.io/joaoh82/rustunnel-mcp:0.8.5"] {
"McpServers": {
"joaoh82-rustunnel": {
"Transport": "stdio",
"Command": "docker",
"Arguments": [
"run",
"--rm",
"-i",
"ghcr.io/joaoh82/rustunnel-mcp:0.8.5"
]
}
}
} {
"mcpServers": {
"joaoh82-rustunnel": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/joaoh82/rustunnel-mcp:0.8.5"
]
}
}
} 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 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 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 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +4
- Stability: unverified → 0.27 ▲ functional
- 5 Sept 26 +1
- Security disclosure: fail → pass ▲ functional
- 3 Sept 26 39
First indexed and scored.
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 oci/ghcr.io/joaoh82/rustunnel-mcp:0.8.5
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
close_tunnel ~97
Force-close a specific tunnel by its ID. The public URL stops working immediately. Use this when a tunnel is no longer needed or public access must be revoked right away — e.g. after a webhook test or demo finishes. Use list_tunnels to find the tunnel_id.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | – | API token. Optional if RUSTUNNEL_TOKEN is set. |
| tunnel_id | string | yes | UUID of the tunnel to close |
No output schema declared.
No examples provided.
create_tunnel ~547
Open a tunnel to a locally running service and get a public URL. Use this when the user or task needs a public URL for a service running locally — webhook testing, sharing a dev server, or letting another agent or device reach localhost. Spawns the rustunnel CLI as a subprocess — the tunnel stays open until close_tunnel is called or the MCP server exits. Modes: - protocol='http' → public https:// URL (web/API services) - protocol='tcp' → public host:port (databases, SSH, raw TCP) - protocol='udp' → public host:port (game servers, DNS) - protocol='p2p' → peer-to-peer; requires `secret` plus `peer_name` (to publish) or `peer_target` (to connect) - load balancing → set `group` + `group_key` (http/tcp only) to join this tunnel into a load-balanced pool; add `health_check` to auto-remove sick backends. The token may be omitted if RUSTUNNEL_TOKEN is configured.
| Name | Type | Req | Description |
|---|---|---|---|
| group | string | – | Load-balancing pool name. Tunnels sharing the same (group, group_key) form one pool (http/tcp only). |
| group_key | string | – | Shared secret for the load-balancing group. Members of one pool must agree on this value. |
| health_check | object | – | Optional client-side health probe. The client probes the local service and reports health so the server routes around a sick backend. Only meaningful for load-balanced tunnels (group set). |
| local_host | string | – | Local hostname to forward to (default 'localhost'). Use to expose a service on another host in your network. |
| local_port | integer | yes | Local port the service is listening on, e.g. 3000 |
| peer_name | string | – | P2P publisher mode: publish the local service under this name. |
| peer_target | string | – | P2P subscriber mode: connect to a published P2P tunnel with this name. |
| protocol | string | yes | Tunnel type |
| region | string | – | Region ID (e.g. 'eu', 'us', 'ap'). Omit to auto-select the nearest by latency. Use list_regions to see options. |
| secret | string | – | Shared secret for P2P (protocol='p2p'). Publisher and subscriber must use the same value. |
| subdomain | string | – | Custom subdomain (HTTP tunnels only). Server assigns a random one if omitted. |
| token | string | – | API token. Optional if RUSTUNNEL_TOKEN is set in the MCP client config. |
No output schema declared.
No examples provided.
get_connection_info ~313
Get the CLI command (and, for load-balanced tunnels, a config file) needed to create a tunnel manually — without spawning anything. Use this when the MCP server cannot spawn subprocesses (e.g. cloud sandbox), when the tunnel must outlive the MCP server, or when you prefer to run the client yourself. Accepts the same arguments as create_tunnel.
| Name | Type | Req | Description |
|---|---|---|---|
| group | string | – | Load-balancing pool name (http/tcp only) |
| group_key | string | – | Shared secret for the load-balancing group |
| health_check | object | – | Optional client-side health probe. The client probes the local service and reports health so the server routes around a sick backend. Only meaningful for load-balanced tunnels (group set). |
| local_host | string | – | Local hostname to forward to (default 'localhost') |
| local_port | integer | yes | Local port the service is listening on |
| peer_name | string | – | P2P publisher mode: publish under this name |
| peer_target | string | – | P2P subscriber mode: connect to this name |
| protocol | string | yes | Tunnel type |
| region | string | – | Region ID (e.g. 'eu', 'us', 'ap'). Omit to auto-select. |
| secret | string | – | Shared secret for P2P (protocol='p2p') |
| subdomain | string | – | Custom subdomain (HTTP only) |
| token | string | – | API token. Optional if RUSTUNNEL_TOKEN is set. |
No output schema declared.
No examples provided.
get_tunnel_history ~98
Retrieve the history of past tunnels, including their duration and which token opened them. Use this when auditing past tunnel activity or debugging why a tunnel dropped or is no longer listed by list_tunnels.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of entries to return |
| protocol | string | – | Optional: filter by protocol. Omit for all. |
| token | string | – | API token. Optional if RUSTUNNEL_TOKEN is set. |
No output schema declared.
No examples provided.
list_regions ~49
List available tunnel server regions with their IDs, names, and locations. Use this when you need to pick a specific `region` for create_tunnel or check which edge locations exist. No authentication required.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_tunnels ~87
List all tunnels currently open on this server. Returns the public URL, protocol, and traffic count for each active tunnel. Use this when you need to check whether a tunnel is still running, recover the public URL of an existing tunnel, or find a tunnel_id to pass to close_tunnel.
| Name | Type | Req | Description |
|---|---|---|---|
| token | string | – | API token. Optional if RUSTUNNEL_TOKEN is set. |
No output schema declared.
No examples provided.
What is the rustunnel MCP server?
rustunnel is an MCP server listed in the public MCP registry as io.github.joaoh82/rustunnel. Give AI agents public HTTPS/TCP/UDP URLs for any localhost service. Open source, self-hostable. This page covers its container image (ghcr.io/joaoh82/rustunnel-mcp:0.8.5).
Is the rustunnel MCP server safe to use?
rustunnel scores 48 out of 100 on VerifyMCP. 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 rustunnel MCP server expose?
rustunnel exposes 6 tools: create_tunnel, list_tunnels, close_tunnel, get_connection_info, list_regions, get_tunnel_history. Their descriptions and schemas cost roughly 1,191 tokens of context every time the server is loaded.
Is the rustunnel MCP server still maintained?
rustunnel 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 rustunnel MCP server under?
rustunnel declares the AGPL-3.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.