Hyperlight
PYPI · MCP-SERVER-HYPERLIGHT
Runs Python in a local, hardware-isolated micro-VM that keeps its state between calls
Available components
Last scanned (16 hours ago)
Scores higher than 69% of PyPI servers
Category Developer Tools
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 Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 4 of 51 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to hyperlight-dev/hyperlight-unikraft). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 14 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 283 tokens (~141/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
- Stability observed for 14 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 3 Nov 26 −9
- Malware scan: pass → unverified ▼ security
- Stability: unverified → 0.43 ▲ functional
- 31 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 29 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 27 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 26 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 22 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 21 Oct 26 67
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 4 Nov 2026 · Analysed pypi/mcp-server-hyperlight@0.1.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | hyperlight-dev/hyperlight-unikraft |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/hyperlight-dev/hyperlight-unikraft/.github/workflows/pypi-publish.yml@refs/heads/main |
| Rekor log index | 3351007331 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:d60eb9713d2d833ed8ed9b8a28d7ae228434012e6f242e3b159d3834ab28ddd1 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 51 packages
| Packages resolved | 51 |
|---|---|
| Stale | 2 |
| No linked repository | 2 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
reset_sandbox Reset the sandbox ~72
Replace the sandbox with a fresh one, in milliseconds: variables and imports are gone. It first waits for calls still running or sent before it, each of which runs for at most 30 seconds, then for the restart one that ran out of time needs; longer while the sandbox first starts, its image pulled.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
run_python Run Python in a micro-VM ~172
Run Python code in a sandbox: a local Hyperlight micro-VM, isolated from this machine by a hypervisor. Variables, imports and functions persist from one call to the next, as in a notebook, until reset_sandbox. The result is what the code prints, then the value of a trailing expression after `Out:`. The sandbox has CPython 3.12 with numpy, pandas, scipy, scikit-learn, matplotlib, pillow and requests. Network: none, every connection is refused. Files: the sandbox has its own filesystem, and none of this machine's files. A call that runs longer than 30 seconds is stopped. That, or a crash, restarts the sandbox, and the variables of earlier calls are lost.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The Python code to run |
No output schema declared.
No examples provided.
How do I install the Hyperlight MCP server?
Hyperlight runs locally as a PyPI package, launched with uvx mcp-server-hyperlight. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · mcp-server-hyperlight
claude mcp add hyperlight-dev-mcp-server-hyperlight -- uvx mcp-server-hyperlight
What is the Hyperlight MCP server?
Hyperlight is an MCP server listed in the public MCP registry as io.github.hyperlight-dev/mcp-server-hyperlight. Runs Python in a local, hardware-isolated micro-VM that keeps its state between calls. This page covers its PyPI package (mcp-server-hyperlight).
Is the Hyperlight MCP server safe to use?
Hyperlight scores 73 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. Its build provenance is signed and verified. 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 Hyperlight MCP server expose?
Hyperlight exposes 2 tools: run_python, reset_sandbox. Their descriptions and schemas cost roughly 244 tokens of context every time the server is loaded.
Is the Hyperlight MCP server still maintained?
Hyperlight is still listed as active in the MCP registry. We last reached this channel on 4 November 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 Hyperlight MCP server under?
Hyperlight declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.