io.github.taybenlor/runno
NPM · @RUNNO/MCP
MCP Server for the Runno Sandbox
Available components
Last scanned (21 hours ago)
Scores higher than 35% of npm servers
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 33 of 100 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency47
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 326 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 335 tokens (~335/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +27
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.00 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Tool coverage: 0 functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- 2 Nov 26 0
- Known CVEs: partial → pass ▲ security
- Dependency health: partial → 0.85 functional
- 12 Oct 26 +1
- Security disclosure: unverified → pass ▲ functional
- 11 Oct 26 −1
- Security disclosure: pass → unverified ▼ functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 9 Sept 26 0
- Security disclosure: unverified → pass ▲ functional
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 npm/@runno/mcp@0.10.6
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 100 packages
| Packages resolved | 100 |
|---|---|
| Stale | 33 |
| 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 →
run_code ~335
Run code in a sandboxed environment. Specify a runtime and then provide some code to run. | runtime | Programming Language | |---------|----------------------| | python | Python | | quickjs | JavaScript | | clang | C | | clangpp | C++ | | ruby | Ruby | | php-cgi | PHP | You can write code for any of the available runtimes, so use the best programming language for the job. If you're unsure, try Python or JavaScript first. Use this tool for the following scenarios: * Running a complex calculation to get an accurate answer * Solving a problem that requires an algorithm * Generating statistics or analysing data * Seeing the result of a small snippet of code run in isolation * Debugging code by running small snippets * Testing code by running small snippets You can use STDOUT to print out results so that you can use them. Following execution you'll be provided with the STDIN, STDOUT, and STDERR combined in the form of TTY output. Make sure that all the data you need is provided inside the program, you won't be able to access the file system or connect to the internet. The code is executed in a safe and secure temporary sandbox. You won't be able to make network connections, access the filesystem, or execute system commands. You won't be able to import any packages from a package manager or execute any external programs. Only the core programming language capabilities are available.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | – |
| runtime | string | yes | – |
No output schema declared.
No examples provided.
How do I install the io.github.taybenlor/runno MCP server?
io.github.taybenlor/runno runs locally as an npm package, launched with npx -y @runno/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @runno/mcp
claude mcp add taybenlor-runno -- npx -y @runno/mcp
What is the io.github.taybenlor/runno MCP server?
io.github.taybenlor/runno is an MCP server listed in the public MCP registry as io.github.taybenlor/runno. MCP Server for the Runno Sandbox. This page covers its npm package (@runno/mcp).
Is the io.github.taybenlor/runno MCP server safe to use?
io.github.taybenlor/runno scores 67 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. It declares no install or post-install scripts. 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 io.github.taybenlor/runno MCP server expose?
io.github.taybenlor/runno exposes 1 tool: run_code. Their descriptions and schemas cost roughly 335 tokens of context every time the server is loaded.
Is the io.github.taybenlor/runno MCP server still maintained?
io.github.taybenlor/runno 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 io.github.taybenlor/runno MCP server under?
io.github.taybenlor/runno declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.