rustunnel

Infrastructure · tested 2026-09-27 · by the Hlido desk, not the vendor

In short: An open-source, Rust-fast tunnel with a first-class MCP server — genuinely agent-drivable, priced to punish idle time, but the managed edge and reliability claims are asserted, not yet independently run.

5 PASS · 0 FAIL of 5 public-surface claims

Quick answer

rustunnel scores 80/100 (STEADY) on Hlido’s independent, hands-on test (reviewed 2026-09-27). STEADY (80) because the public surface is substantive and internally consistent: a clearly documented open-source (AGPL) tunnel with transparent pay-as-you-go pricing, a self-host path, a broad protocol feature set, and Pricing: Open source · Usage-based · Free tier · Subscription (free entry point documented).

rustunnel is a localhost/webhook/TCP tunneling tool that reads as unusually agent-native: it ships an MCP server that lets Claude Code, Cursor, Windsurf, Cline, Codex and custom harnesses create, manage and close tunnels in plain language, with a one-command installer that writes the right config for each client. That is the standout, and it is backed by a coherent product surface — CLI install (brew install rustunnel), API-key auth via RUSTUNNEL_TOKEN, HTTP/TCP/UDP and P2P tunnels, custom subdomains, load-balanced pools with health checks, a live terminal dashboard, and a loopback request inspector with replay. The positioning against ngrok is direct and, refreshingly, factual rather than snarky: pay-as-you-go from a $3/mo minimum that is credited toward usage, self-host free under AGPL, and idle time billed at zero. Where the evidence thins is exactly where it matters most for infrastructure: end-to-end encryption, 'blazing fast' latency, global edge availability and the reliability of the managed relay are stated on the page, not something Hlido observed by running a tunnel end to end. Traction is moderate (655 GitHub stars) and the managed cloud is newer than the open-source core. As a self-hostable building block it looks credible and honestly documented; as a managed dependency, the durability and edge-fleet claims are the buyer's to verify before production.

Why STEADY

STEADY (80) because the public surface is substantive and internally consistent: a clearly documented open-source (AGPL) tunnel with transparent pay-as-you-go pricing, a self-host path, a broad protocol feature set, and — the differentiator — a first-class MCP server that makes it directly consumable by AI agents. It is not scored higher because this is a public-surface (medium-confidence) review with no hands-on behavioral run: encryption, latency, and managed-edge reliability are asserted on the page rather than independently exercised, and community traction (655 stars) is moderate rather than dominant.

Public-surface checklist

What we saw

1 screenshot captured by the Hlido engine during the reviewed run (run-3260a53e28969487-rustunnel-com). Our own captures — not vendor marketing material.

rustunnel — run screenshot 1 (home.png)
home.png

What it does well

What it fails at

Best for

  • Developers who want an AI agent to spin up and tear down tunnels in plain language via MCP
  • Teams tunneling webhooks or sharing localhost who resent paying a flat fee for idle time
  • Users wanting an open-source, self-hostable ngrok alternative under AGPL with full data control
  • Builders needing TCP/UDP/P2P tunnels or load-balanced backends with health checks, not just HTTP
  • Cost-sensitive light users who benefit from pay-as-you-go billing credited toward usage

Not recommended for

  • Production dependencies that require independently verified edge uptime and reliability SLAs before adoption
  • Buyers who need a mature, heavily battle-tested vendor rather than a growing open-source project
  • Teams wanting fully managed tunneling with zero self-host or operational responsibility on the free tier
  • Anyone who needs the encryption and latency claims proven before trusting sensitive traffic

Pricing & access

Derived from Hlido-held evidence only (engine checklist + editorial text); quotes are verbatim from the scorecard; not vendor-supplied; re-derived daily. Verify current prices on the vendor's pricing page. Last verified 2026-09-27.

Related agents

Agent relevance

API CLI MCP Behavioral-testable

First-class MCP server (rustunnel-mcp, JSON-RPC over stdio): an agent sets RUSTUNNEL_TOKEN and can create, manage and close tunnels in natural language (e.g. "Expose port 3000" -> create_tunnel). Also drivable via the CLI (brew install rustunnel) and an API-key-authenticated HTTP surface. One-command installer writes per-harness config for Claude Code, Cursor, Windsurf, Cline and Codex.

Agent-friendly score: 9/10

Evidence

scorecard.json · transparency passport · registry · methodology

More: compare agents · best of · developer tools · incident registry

Verdict by Hlido Editor, our automated editorial system · Method: public-surface-tier-2+editorial-narrative-v2 · Methodology version 2026.09 ·

How this page was produced. The scores, claim verdicts and evidence come from automated hands-on testing of the product’s public surface. The written analysis is drafted by an AI system, and pages publish without a person reviewing each one. Hlido publishes this record and answers for it — tell us if anything here is wrong and we will correct it.

Embed this trust badge

Hlido trust score

Live, always-current independent score — free to embed on your site or README. No vendor pays for placement.

Markdown

[![Hlido trust score](https://hlido.eu/badge/joaoh82-rustunnel.svg)](https://hlido.eu/check/?agent=joaoh82-rustunnel)

HTML

<a href="https://hlido.eu/check/?agent=joaoh82-rustunnel"><img src="https://hlido.eu/badge/joaoh82-rustunnel.svg" alt="Hlido trust score"></a>