This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Product upvotes vs the next 3
Waiting for data. Loading
Product comments vs the next 3
Waiting for data. Loading
Product upvote speed vs the next 3
Waiting for data. Loading
Product upvotes and comments
Waiting for data. Loading
Product vs the next 3
Loading
Nexus Protocol
Secure protocol for AI agents. Apache 2.0.
MCP has 84k GitHub stars and a documented RCE Anthropic calls "intended behavior." Nexus Protocol is the fix. WASM sandbox. 19 dangerous syscalls blocked at the kernel boundary. Binary protocol with zero JSON overhead. Three sandbox policies. Prompt injection guard at the protocol layer. SDKs in Rust, Python, Go, and TypeScript. Apache 2.0. If your agent can call execve() without a sandbox, you don't have a secure agent. You have a polite backdoor.
MCP became the standard with 84,000 GitHub stars and a documented hole: zero sandbox, zero authentication, RCE by design.
I built Nexus Protocol to fix that at the protocol layer, not with wrappers.
What ships today: 19 syscalls blocked. WASM sandbox. Binary protocol. Three sandbox policies. Prompt injection guard. SDKs in Rust, Python, Go, TypeScript. Apache 2.0. 60 tests passing.
The demo that matters: MCP receives "rm -rf /" and executes it. Intended behavior. Nexus Protocol blocks syscall 87 (unlink) and syscall 59 (execve) before the kernel sees them.
Repo: github.com/KaioH3/nexus Apache 2.0. Read the spec. Break the sandbox. Tell me what you find.
About Nexus Protocol on Product Hunt
“Secure protocol for AI agents. Apache 2.0.”
Nexus Protocol was submitted on Product Hunt and earned 3 upvotes and 1 comments, placing #117 on the daily leaderboard. MCP has 84k GitHub stars and a documented RCE Anthropic calls "intended behavior." Nexus Protocol is the fix. WASM sandbox. 19 dangerous syscalls blocked at the kernel boundary. Binary protocol with zero JSON overhead. Three sandbox policies. Prompt injection guard at the protocol layer. SDKs in Rust, Python, Go, and TypeScript. Apache 2.0. If your agent can call execve() without a sandbox, you don't have a secure agent. You have a polite backdoor.
On the analytics side, Nexus Protocol competes within Developer Tools, Artificial Intelligence and GitHub — topics that collectively have 1M followers on Product Hunt. The dashboard above tracks how Nexus Protocol performed against the three products that launched closest to it on the same day.
Who hunted Nexus Protocol?
Nexus Protocol was hunted by Kaio Henrique. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
For a complete overview of Nexus Protocol including community comment highlights and product details, visit the product overview.
Kaio Henrique
MCP became the standard with 84,000 GitHub stars and a documented hole: zero sandbox, zero authentication, RCE by design.
I built Nexus Protocol to fix that at the protocol layer, not with wrappers.
What ships today:
19 syscalls blocked. WASM sandbox. Binary protocol. Three sandbox policies. Prompt injection guard. SDKs in Rust, Python, Go, TypeScript. Apache 2.0. 60 tests passing.
The demo that matters:
MCP receives "rm -rf /" and executes it. Intended behavior.
Nexus Protocol blocks syscall 87 (unlink) and syscall 59 (execve) before the kernel sees them.
Repo: github.com/KaioH3/nexus
Apache 2.0. Read the spec. Break the sandbox. Tell me what you find.