MCP Server Code Runner

Code Runner MCP Server

MCP Servers TypeScript Grade D Listed MIT
25.4/100
Rank #1252 of 1320
Compare MCP Server Code Runner

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-02-05 · 211d ago
Recent change
Rank +7

Is MCP Server Code Runner safe? MCP Server Code Runner scores 25.4/100 (Grade D), ranked #1252 of 1320 tracked open-source AI agent projects, on evidence coverage C (2 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 →

Ranked neighbours in MCP Servers

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
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)
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 211 days ago. Fresh activity helps separate stable projects from stale ones.
21.4
Activity sub-score · out of 100
#736

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 C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-09-04 14:33 UTC · Repo last pushed 211 days ago — may be stale

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars
245
Forks
33
Last Push
2026-02-05
211 days ago
Commits (4 wk)
0
Downloads (7d)
HN mentions (30d)
Open Issues
8
Rank Change
▼6
was #1246

Analysis

HVTrust Dimensions vs MCP Servers

25.4 / 100 · 67.0% confidence

MCP Server Code Runner MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
2.7 / 25
6.8 below avg 9.5
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
1.9 below avg 11.8
Maintenance60% last-push freshness · 40% commit activity
0 / 20
12.2 below avg 12.2
AdoptionLog-scaled stars · package downloads
5.7 / 20
0.5 below avg 6.2

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 Aug 29, 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

Is MCP Server Code Runner safe?

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 211 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

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.

Reputation Timeline

Signal history
Rank 9Listed 1HVTrust 1Scorecard 1
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

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 25.4 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