Rust port of @masterking32's MasterHttpRelayVPN — all credit to @masterking32 for the original idea and Python implementation. Free DPI bypass via a Google Apps Script relay with TLS SNI concealment. CLI + cross-platform desktop UI, HTTP + SOCKS5 proxy, no runtime deps.
3.4k
Stars
541
Forks
194
Open issues
16
Contributors
AI Analysis
mhrv-rs is a Rust-based DPI/SNI bypass tool that uses a free Google Apps Script relay to circumvent internet censorship, allowing users to access blocked websites through encrypted tunneling. It's purpose-built for users in censored regions (particularly Iran) who need circumvention tools, providing both CLI and cross-platform desktop UI with HTTP and SOCKS5 proxy support. Not suitable for general-purpose VPN or privacy use cases outside censorship circumvention scenarios.
Inferred from signals mentioned in the README (tests, CI, type safety) — not a review of the actual code.
AI's overall editorial judgment — not an average of the bars above, can weigh other factors too.
Rust DPI-bypass tool leveraging Google Apps Script relay; niche censorship circumvention with rapid early adoption.
mhrv-rs is a Rust port of MasterHttpRelayVPN that enables DPI/SNI blocking bypass by relaying traffic through a user-deployed Google Apps Script, making censored content appear as encrypted Google traffic to ISPs. Built for users in regions with aggressive internet filtering (primarily Iran and similar contexts), it combines CLI and cross-platform desktop UI with zero runtime dependencies. Gained ~3,400 stars in ~6 weeks; adoption appears concentrated in Persian-speaking communities and anti-censorship networks.
Fork of @masterking32's Python MasterHttpRelayVPN (3,899 stars); Rust port created April 2026 to eliminate runtime dependencies and improve performance. Original concept proven by sibling MasterDnsVPN (6,634 stars, Go). Appears driven by demand for lightweight, portable, battery-efficient binaries in censored regions.
Explosive star growth (3,436 in ~6 weeks, 19 in last 7 days) suggests strong initial network effect and word-of-mouth adoption among Persian-speaking anti-censorship communities. Bilingual README (English + Farsi) and community guides (YouTube, blog posts) indicate organic grassroots adoption rather than mainstream tech marketing. Growth velocity slowing as of late May 2026 suggests saturation within target demographic or natural lifecycle plateau post-launch buzz.
Adoption not verified in traditional SaaS/enterprise metrics. Evidence suggests strong grassroots usage in Iran and similar regions based on: (1) bilingual Farsi+English docs, (2) community guides and YouTube tutorials in Persian, (3) star clustering among anti-censorship tool ecosystems, (4) credits to Iranian developers (Kian Irani guide). Real production usage likely but not documented with testimonials, case studies, or quantitative user counts. Download count badge present but not accessible in metadata provided.
Based on README: single ~3 MB binary, no runtime dependencies, supports HTTP and SOCKS5 proxies, multi-platform builds (macOS, Windows, Linux, Android, OpenWRT). Likely uses tokio or async-std for networking; likely embeds certificate generation and TLS SNI manipulation logic. Appears to be a clean Rust rewrite optimizing for bundle size and portability versus Python original.
Not documented in README. No mention of test suite, CI beyond release pipeline, or test methodology. Uncertainty on test depth.
Last push 2026-05-28 (approximately 37 days ago from evaluation date 2026-07-04); actively maintained but not hyperactive. Release CI passing. No evidence of rapid issue resolution or changelog visibility in README excerpt. Project is young (created 2026-04-21) so inactivity window is normal; however, lack of visible activity post-launch suggests either project stabilized quickly or maintainer attention has moved elsewhere. Not stagnant, but not heavily evolved post-launch.
ADOPT IF: you are in a region with DPI/SNI-based censorship, have a Google account, tolerate the Apps Script relay performance and quota limits, and want zero runtime dependencies and minimal binary size. AVOID IF: you need high throughput (Google Apps Script has inherent quota limits), require formal vendor support, or operate in a regime that actively persecutes circumvention tool use (legal risk is end-user's responsibility). MONITOR IF: you are building anti-censorship tooling and want to track Rust ecosystem maturity or gauge adoption velocity in restricted regions; project may become template for similar relay architectures.
Independent dimensions
Mainstream potential
2/10
Technical importance
6/10
Adoption evidence
4/10
- Google Apps Script quota and rate limits will throttle throughput for heavy users; no evidence of testing under sustained load.
- Google account suspension or terms-of-service violation risk if Google detects relay abuse; users shoulder legal/account risk.
- Minimal test coverage and young codebase (6 weeks old) mean undiscovered bugs likely; Rust memory safety mitigates some classes, but protocol-level and logic errors untested.
- Single-maintainer project (appears to be @therealaleph); key-person risk if maintainer disengages post-launch-buzz or faces personal circumstances.
- Adoption concentrated in Persian-speaking regions creates geographic/linguistic moat and reduces mainstream visibility; if target regime blocks Google altogether, relay becomes inoperable.
Project likely stabilizes as mature niche tool for Iranian and similar censored-region users over next 12 months. Star growth will plateau; maintenance may become minimal if bugs are rare and protocol remains stable. Unlikely to penetrate mainstream circumvention tool adoption (shadowsocks, Wireguard, etc.) due to architectural dependence on Google and Apps Script quota limits. May be cited or forked as reference implementation for 'Google relay' pattern in academic anti-censorship literature.
Newsletter
Get analyses like this every Monday
Free weekly digest of the most interesting open-source discoveries.
Languages
Information
- Language
- Rust
- License
- MIT
- Last updated
- 1mo ago
- Created
- 3mo ago
- Analyzed with
- anthropic/claude-haiku-4-5
Stars over time
Contributors over time
Top 100 contributors only — repos with more will plateau at 100.
Open issues
Top contributors
Similar repos
masterking32/MasterHttpRelayVPN
MasterHttpRelayVPN is a local HTTP/SOCKS5 proxy that routes traffic through...
masterking32/MasterDnsVPN
MasterDnsVPN is a DNS tunneling VPN written in Go that encapsulates TCP traffic...
| Repository | Stars | Week Δ | Language | Score | Updated |
|---|---|---|---|---|---|
|
|
3.4k | +12 | Rust | 7/10 | 1mo ago |
|
|
3.9k | — | Python | 6/10 | 1mo ago |
|
|
6.7k | — | Go | 7/10 | 4d ago |
|
|
4.4k | — | Python | 7/10 | 2mo ago |
|
|
1.2k | — | Rust | 4/10 | 10h ago |
|
|
10.7k | — | Rust | 8/10 | 12h ago |
Original inspiration; mhrv-rs trades features for portability (no runtime) and performance; Python version likely has slower startup, larger bundle, and dependency management friction in low-bandwidth/restricted-internet contexts.
Sibling project with 6,634 stars; DNS-based approach versus HTTP relay. Different attack surface; mhrv-rs may be more transparent/compatible with arbitrary HTTP clients.
Established, mainstream circumvention tool; mhrv-rs uses different relay architecture (Google Apps Script vs. traditional proxy server) and targets DPI/SNI rather than pure encryption, may be more resilient to detection but less portable to shared server hosting.
Comparable star count and Rust implementation; both serve anti-censorship niche; TrustTunnel likely uses different protocol/relay method; direct feature comparison not evident from README.
MTProto proxy for Telegram; narrower use case; mhrv-rs is general-purpose HTTP proxy, broader applicability.