Code execution · MCP server
MCP v8: MCP server, setup and security
MCP v8 is an open-source MCP server published on GitHub that lets an AI agent run AI-generated JavaScript locally in isolated sessions with heap snapshots. Its repository has 62 stars and its last commit is from October 23, 2026 and it is licensed under AGPL-3.0.
| Adoption (stars) | 18/40 | |
|---|---|---|
| Maintenance | 30/30 | |
| Framework (licence, registry, official) | 20/30 |
What MCP v8 does
According to its repository: “JavaScript sandbox that uses V8 isolation to run AI-generated code locally, with heap snapshotting for persistent sessions.”
The Model Context Protocol (MCP) is a standard plug between an AI agent and an outside service: once the server is connected, its tools show up in the agent, which decides when to call them. MCP v8 is listed under Code execution, a category of 32 servers in the directory, where it ranks #20 by stars.
Topics declared by the repository: javascript.
Installing and connecting MCP v8
Distribution modes declared in the official MCP registry:
- Docker (OCI) image
It works with any MCP-compatible client (Claude Desktop, Claude Code, Cursor, VS Code, Codex and most recent agents). You add one entry to the client's MCP configuration: server name, start command or URL, environment variables. Project language: Rust. Listed systems: macOS, Linux.
Security: what to check
Connecting an MCP server means installing software that talks straight to your agent: it runs with your rights and the model trusts its tool descriptions. The risk therefore depends on what it can touch and how far its code can be trusted.
Points found for MCP v8:
- System access: the Code execution category gives the agent control over files, a terminal, code or a browser. A booby-trapped instruction in content the agent reads (prompt injection) can then turn into an action.
Good practice: grant only the rights needed (least privilege), require human approval for irreversible actions, and run the AI agent security check.
Project activity and maintenance
Created on April 6, 2025, the r33drichards/mcp-js repository has 62 stars and 13 forks, with 9 open issues. It has more stars than 56% of the servers in the directory. It received changes this month. Version published in the registry: 0.22.0 (October 8, 2026).
Stars measure attention, not quality: a recent, heavily promoted project can collect them fast, while a useful but niche server will have few.
Verdict
MCP v8 is a reasonable choice; check the points below before connecting it.
Strengths
- Active project: recent commit
- Listed in the official MCP registry
Avoid if…
- You cannot isolate the agent (sandbox, container)
Alternatives
- Container use4.1K ★
- LLM Sandbox1.1K ★
- Tidewave Phoenix858 ★
- Superserve466 ★
- OrcaReplay281 ★
- Mailtrap66 ★
Learn more
Frequently asked questions
How do I install MCP v8?
MCP v8 is distributed as Docker (OCI) image. Add it to your client's MCP configuration (Claude Desktop, Cursor, VS Code…) following the README of r33drichards/mcp-js.
Is MCP v8 free?
The code is published under the AGPL-3.0 licence and can be used free of charge.
Is MCP v8 safe?
Points to watch: system access. Give it minimum rights and approve sensitive actions.
Is it an official server?
Nothing says so: it is a project published by r33drichards on GitHub. Check who maintains it before giving it access.
What are the alternatives to MCP v8?
In the same category: Container use, LLM Sandbox, Tidewave Phoenix, and Superserve.
Related articles
- Build your own MCP server in 30 minutesOctober 24, 2026
- Automate your inbox with an AI agentOctober 18, 2026
- MCP, A2A, and tool calling: agent protocols explainedOctober 17, 2026
- Build an AI agent with n8n, without codingOctober 16, 2026
Neutrality. No affiliate links. No vendor pays to be reviewed, rated or ranked. Reviews are directed by François Chollet, neutral and factual, and every data point is dated and sourced. How we score