updated 2026-09-26 06:32 UTC

MCP Server Code Runner

formulahendry/mcp-server-code-runner

Code Runner MCP Server

MCP Servers TypeScript Listed MIT

Is MCP Server Code Runner safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 1.7 / 10
Provenance None
Signed commits 12%
Last push 233d ago
Compare MCP Server Code Runner

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: MCP Server Code Runner scores 39.7/100 (Grade D), ranked #1171 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 1.7/10; 12% of recent commits are signed; last pushed 2026-02-05. Every point is earned from checkable signals — never paid placement. How scoring works →

How MCP Server Code Runner compares in MCP Servers

  1. #692 AkTools MCP Server 40.1 +0.4
  2. #693 TradeOS 39.7 ±0
  3. #694 MCP Server Code Runner 39.7 this agent
  4. #695 X64dbg MCP 39.7 ±0
  5. #696 Clipboard History MCP 39.6 −0.1

Bars show each HVTrust score; the tick marks MCP Server Code Runner’s 39.7.

Where the 39.7 comes from

HVTrust dimensions vs the MCP Servers average

39.7 / 100 · 100.0% confidence

MCP Server Code Runner MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
2.7 / 25
7.6 below avg 10.3
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.6 below avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
9.9 / 17
2.3 below avg 12.2
Maintenance60% last-push freshness · 40% commit activity
0 / 20
12.1 below avg 12.1
AdoptionLog-scaled stars · package downloads
10.3 / 20
3.1 above avg 7.2

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-25
Rank Moved
Rank rose 14 spots (#1188 → #1174)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank rose 106 spots (#1294 → #1188)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 1.7/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Refresh maintenance signals The repo was last pushed 233 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent Get email alerts for MCP Server Code Runner View MCP Servers Report missing data
21.4
Activity sub-score · out of 100
#694
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-09-26 06:32 UTC · Repo last pushed 233 days ago — may be stale

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars
245
Forks
33
Last Push
2026-02-05
233 days ago
Commits (4 wk)
0
Downloads (7d)
2,495
npm+docker
HN mentions (30d)
—
Open Issues
8
Rank Change
▲3
was #1174

Analysis

Activity Inputs

21.4 / 100
StarsRepository reach
14.3 / 30
FreshnessLast push recency
0.0 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
7.1 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
1.7 / 10
OpenSSF Scorecard · scanned Sep 18, 2026
Signed Commits
12%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 0
CI-Tests 0
CII-Best-Practices 0
Code-Review 0
Contributors 10
Dangerous-Workflow -1
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 0
Packaging -1
Pinned-Dependencies 0
SAST 0
Security-Policy 0
Signed-Releases -1
Token-Permissions -1
Vulnerabilities 0

Common questions about MCP Server Code Runner

Public trust evidence for MCP Server Code Runner is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does MCP Server Code Runner publish package provenance?
No published build provenance is currently detected for MCP Server Code Runner. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does MCP Server Code Runner have an OpenSSF Scorecard?
MCP Server Code Runner has an OpenSSF Scorecard score of 1.7/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is MCP Server Code Runner actively maintained?
Stale. The repository has not been pushed to in 233 days. Consider whether the project is still being maintained.
What license does MCP Server Code Runner use?
MCP Server Code Runner ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are MCP Server Code Runner's commits signed?
12% of the last 100 commits to MCP Server Code Runner are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
MCP Server Code Runner appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to MCP Server Code Runner's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain MCP Server Code Runner?

For maintainers

HVTrust scores MCP Server Code Runner from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 16HVTrust 3Listed 2Scorecard 1Delisted 1MCP 1
2026-09-25
Rank Moved
Rank rose 14 spots (#1188 → #1174)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank rose 106 spots (#1294 → #1188)
2026-09-23
HVTrust Changed
HVTrust up 25.5pts (13.3 → 38.8)
2026-09-22
Newly Listed
First tracked at rank #1294
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-09
Rank Moved
Rank dropped 11 spots (#1163 → #1174)
2026-09-08
Rank Moved
Rank rose 129 spots (#1292 → #1163)
2026-09-08
HVTrust Changed
HVTrust up 13.1pts (25.4 → 38.5)
2026-09-06
Rank Moved
Rank dropped 10 spots (#1275 → #1285)
2026-09-05
Rank Moved
Rank dropped 14 spots (#1261 → #1275)
2026-09-04
Rank Moved
Rank dropped 15 spots (#1246 → #1261)
2026-09-03
Rank Moved
Rank dropped 36 spots (#1210 → #1246)
2026-09-02
Rank Moved
Rank dropped 35 spots (#1175 → #1210)
2026-09-01
Rank Moved
Rank dropped 43 spots (#1132 → #1175)
2026-08-31
Rank Moved
Rank dropped 31 spots (#1101 → #1132)
2026-08-30
Rank Moved
Rank dropped 46 spots (#1055 → #1101)
2026-08-29
Scorecard Added
OSSF Scorecard: 1.7/10
2026-08-29
Rank Moved
Rank rose 216 spots (#1271 → #1055)
2026-08-29
HVTrust Changed
HVTrust up 9.2pts (16.2 → 25.4)
2026-08-26
Rank Moved
Rank dropped 20 spots (#1238 → #1258)
2026-08-16
Rank Moved
Rank dropped 26 spots (#1214 → #1240)
2026-08-10
Rank Moved
Rank dropped 73 spots (#1141 → #1214)
2026-08-08
Newly Listed
First tracked at rank #1139
GitHub → npm: mcp-server-code-runner

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 39.7 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/mcp-server-code-runner.svg)](https://hvtracker.net/agents/mcp-server-code-runner)
HTML:
<a href="https://hvtracker.net/agents/mcp-server-code-runner"><img src="https://hvtracker.net/badge/mcp-server-code-runner.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON