Leaderboard github.com
DarkPhilosophy/mcp-system-monitor
A Model Context Protocol (MCP) server implementation designed for AI agents to monitor and interact with Linux servers (Ubuntu, CentOS, RedHat, etc.). This server provides comprehensive system information including CPU, memory, disk, network, and process data through both MCP protocol and HTTP REST API
AI provenance
0%
possible
- Confidence
- 42%
- Coverage
- 100%
Estimated share of AI-generated code. Explicit attribution is a lower bound.
Code quality
66/100
adequate
- Confidence
- 90%
- Coverage
- 100%
Complexity, duplication, lint density, tests, CI, docs and review process.
Security
81/100
adequate
- Confidence
- 85%
- Coverage
- 100%
Secrets, static analysis, vulnerable dependencies, CI and supply-chain posture.
AI provenance
0% possible
Weak signals consistent with AI-assisted development. Comments and strings use phrasing typical of LLM-written code (see the coding style evidence).
How the score is built
- Explicitly attributed share0%
- Unattributed share in AI-pace bursts0%
- Estimated AI-generated share0%
- AI tool configuration files0
- Work sessions at AI pace0
- Releases at AI pacenot measured
- Coding-style index (1.0+ means possible)12.32
Lines added per month all AI-attributed share
- 2025-073,398 · 0% AI
- 2025-12775 · 0% AI
Evidence by analyzer
Explicit AI attributionok
- attributed_commit_share
- 0.0%
- attributed_commits
- 0
- attributed_loc
- 0
- attributed_loc_share
- 0.0%
- commits
- 9
- effective_loc
- 4,173
- tools_detected
- 0
AI tool configurationok
- artifacts
- 0
- tools_configured
- 0
- workflow_agents
- 0
Commit velocityok
- excluded_import_loc
- 3,398
- flagged_loc
- 0
- flagged_loc_share
- 0.0%
- flagged_units
- 0
- max_loc_per_hour
- 96.02
- measured_loc
- 775
- median_loc_per_hour
- 94.76
- pr_timed_units
- 0
- pre_ai_era_burst_loc
- 0
- pre_ai_era_bursts
- 0
- pre_ai_era_measured_loc
- 0
- work_units
- 2
Release velocityskipped
Coding styleok4 items
- placeholder or demo-only phrasing: //! of system monitoring data for demonstration purposes.
- placeholder or demo-only phrasing: /// Simulate system metrics (replace with actual MCP server calls)
- placeholder or demo-only phrasing: // In a real scenario, you would call the MCP server here
- placeholder or demo-only phrasing: // For demo purposes, we'll simulate realistic data
- count:assistant_voice
- 0
- count:emoji_in_code
- 73
- count:narrated_steps
- 0
- count:placeholder
- 4
- files:assistant_voice
- 0
- files:emoji_in_code
- 6
- files:narrated_steps
- 0
- files:placeholder
- 1
- index
- 12.32
- lines_scanned
- 3,612
- per_kloc:assistant_voice
- 0
- per_kloc:emoji_in_code
- 20.21
- per_kloc:narrated_steps
- 0
- per_kloc:placeholder
- 1.11
Code quality
66 adequate
Code quality is adequate: test-to-source ratio 0.12, no CI test run detected; 8% of function code in complex or long functions; 4% duplicated lines. Weakest area: testing.
How the score is built
- Complexity78
- Duplication79
- Lint and smells86
- Tests and CI36
- Documentation65
- Type safetynot measured
- Review processnot measured
Evidence by analyzer
Complexity (lizard)ok2 items
- run in src/stdio_server.rs: complexity 17, 52 lines
- main in examples/client.rs: complexity 15, 114 lines
- complex_functions
- 1
- function_nloc
- 1,962
- functions
- 110
- long_functions
- 1
- many_param_functions
- 0
- mean_ccn
- 3.48
- p90_ccn
- 7
- risky_nloc_share
- 8.5%
Duplication (jscpd)ok3 items
- 6+ duplicated lines: examples/client.rs:59 and examples/client.rs:153
- 6+ duplicated lines: examples/demo_visualization.rs:220 and examples/demo_visualization.rs:259
- 6+ duplicated lines: src/system_monitor/linux.rs:233 and src/system_monitor/linux.rs:288
- compared_lines
- 2,552
- duplicated_lines
- 100
- duplicated_share
- 3.9%
- files
- 19
Lintok
- category:correctness
- 9
- findings
- 9
- scanned_lines
- 3,612
- weighted_findings
- 2.25
Tests and CIok
- check:ci_present
- no
- check:ci_runs_lint
- no
- check:ci_runs_tests
- no
- check:has_tests
- yes
- check:test_ratio
- no
- check:tests_cochange
- yes
- ci_files
- 0
- cochange_commits
- 4
- cochange_share
- 25.0%
- source_lines
- 3,612
- test_lines
- 427
- test_ratio
- 0.12
Documentationok2 items
- README.md
README.md - LICENSE
LICENSE
- check:changelog
- no
- check:contributing
- no
- check:license
- yes
- check:readme
- yes
- readme_lines
- 1,172
Type safetyskipped
Security
81 adequate
Security posture is adequate: no high-impact findings. Weakest area: posture.
How the score is built
- Secrets100
- Static analysis (SAST)98
- Vulnerable dependenciesnot measured
- CI workflowsnot measured
- Security posture0
- OpenSSF Scorecardnot measured
Evidence by analyzer
OpenSSF Scorecardskipped
no published OpenSSF Scorecard result for this repo
Package registriesok
- checked
- 19
- declared
- 19
- lookup_errors
- 0
- missing
- 0
- recent
- 0
Secrets (gitleaks)ok
- secrets_current
- 0
- secrets_history
- 0
- secrets_low_confidence
- 0
- secrets_nonprod
- 0
Static analysis (opengrep)ok
- findings
- 1
- findings_high
- 0
- findings_low
- 1
- findings_medium
- 0
- parse_errors
- 0
- scanned_lines
- 3,612
- weighted_findings
- 0.25
Dependencies (osv-scanner)skipped
CI workflows (zizmor)skipped
Security postureok1 item
- Cargo.toml has no lockfile alongside it (unpinned dependencies)
Cargo.toml
- check:dependency_updates
- no
- check:lockfiles
- no
- check:security_policy
- no
- check:signed_commits
- no
- signed_commit_share
- 0.0%
- unpinned_manifests
- 1
Release downloadsok
- binary_assets
- 0
- signals
- 0
- suspicious
- 0
Findings
10 low
10 findings
| Severity | Rule | Location | Message | Tool |
|---|---|---|---|---|
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
deploy.sh:37 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
deploy.sh:43 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
install.sh:228 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
install.sh:229 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
install.sh:57 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
install.sh:68 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
install.sh:95 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
test_server.sh:67 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/bash.lang.correctness.unquoted-variable-expansion-in-command |
test_server.sh:68 | Variable expansions must be double-quoted so as to prevent being split into multiple pieces according to whitespace or whichever separator is specified by the IFS variable. If you really wish to split the variable's contents, you may... | Lint |
| low | opengrep/rust.lang.security.args |
src/main.rs:19 | args should not be used for security operations. From the docs: "The first element is traditionally the path of the executable, but it can be set to arbitrary text, and might not even exist. This means this property should not be relied... | Static analysis (opengrep) |
Tools and coverage
Every analyzer that ran on this commit. A failed or skipped tool is a coverage gap: its share of the score is left out and the coverage figure drops.
| Analyzer | Pillar | Status | Version | Findings | Note |
|---|---|---|---|---|---|
| AI tool configuration | AI provenance | ok | signatures-v1 | 0 | |
| Explicit AI attribution | AI provenance | ok | signatures-v1 | 0 | |
| Release velocity | AI provenance | skipped | — | 0 | |
| Coding style | AI provenance | ok | — | 0 | |
| Commit velocity | AI provenance | ok | prov-4 | 0 | |
| Complexity (lizard) | Code quality | ok | lizard 1.25.1 | 0 | |
| Documentation | Code quality | ok | — | 0 | |
| Duplication (jscpd) | Code quality | ok | repotrust-dup-w6 | 0 | |
| Lint | Code quality | ok | opengrep 1.33.1; rules f1d2b562b414 | 9 | |
| Tests and CI | Code quality | ok | — | 0 | |
| Type safety | Code quality | skipped | — | 0 | |
| CI workflows (zizmor) | Security | skipped | — | 0 | |
| Dependencies (osv-scanner) | Security | skipped | — | 0 | |
| Release downloads | Security | ok | — | 0 | |
| Security posture | Security | ok | — | 0 | |
| Package registries | Security | ok | — | 0 | |
| Static analysis (opengrep) | Security | ok | opengrep 1.33.1; rules f1d2b562b414 | 1 | |
| OpenSSF Scorecard | Security | skipped | — | 0 | no published OpenSSF Scorecard result for this repo |
| Secrets (gitleaks) | Security | ok | gitleaks 8.30.1 | 0 |
Score history
Scores from different scoring versions aren't directly comparable.
| Scored | Commit | Scoring | AI provenance | Quality | Security |
|---|---|---|---|---|---|
| 2026-11-14 | b541b00b29e9 | prov-5+qual-2+sec-2 | 0% | 66 | 81 |
| 2026-11-14 | b541b00b29e9 | prov-4+qual-2+sec-2 | 0% | 66 | 81 |
Full text report
- Repository: https://github.com/DarkPhilosophy/mcp-system-monitor
- Commit:
b541b00b29e9b49008166c43316183780817a300 - Generated: 2026-11-14T14:52:00+00:00
- Scorer 0.1.0, scoring prov-5+qual-2+sec-2, report schema v2
Scores
| Pillar | Score | Signal | Confidence | Coverage |
|---|---|---|---|---|
| AI provenance (estimated AI-generated share) | 0 | possible | 42% | 100% |
| Code quality | 66 | adequate | 90% | 100% |
| Security | 81 | adequate | 85% | 100% |
AI provenance
Weak signals consistent with AI-assisted development. Comments and strings use phrasing typical of LLM-written code (see the coding style evidence).
-
Explicitly attributed share (lower bound): 0.0%
-
Unattributed share in AI-consistent velocity bursts: 0.0%
-
Estimated AI-generated share: 0.0%
-
Stylometry index: 12.32 per 1,000 lines (narrated steps 0, placeholders 4, assistant phrasing 0, emoji 73). Reported as a signal, not scored.
| Month | Lines added | Attributed to AI |
|---|---|---|
| 2025-07 | 3,398 | 0% |
| 2025-12 | 775 | 0% |
Evidence
- placeholder or demo-only phrasing: //! of system monitoring data for demonstration purposes. (examples/dem)
- placeholder or demo-only phrasing: /// Simulate system metrics (replace with actual MCP server calls) (examples/dem)
- placeholder or demo-only phrasing: // In a real scenario, you would call the MCP server here (examples/dem)
- placeholder or demo-only phrasing: // For demo purposes, we'll simulate realistic data (examples/dem)
AI provenance describes how code was produced; it is not a quality judgment. Unless attribution is explicit, these are signals consistent with AI generation, not proof. Squash/rebase workflows, imported code, and rewritten history reduce accuracy.
Code quality
Code quality is adequate: test-to-source ratio 0.12, no CI test run detected; 8% of function code in complex or long functions; 4% duplicated lines. Weakest area: testing.
| Area | Score |
|---|---|
| Complexity (lizard) | 78 |
| Duplication | 79 |
| Code smells (Opengrep) | 86 |
| Tests and CI | 36 |
| Documentation | 65 |
| Type safety | n/a |
| Process (Scorecard review/maintenance) | n/a |
- Functions: 110; mean complexity 3.5, 90th percentile 7; 1 complex and 1 long functions
- Duplicated lines: 3.9% of 2,552 compared
- Tests: 427 test lines for 3,612 source lines (ratio 0.12); CI test commands: none detected; 25% of recent source commits also change tests
- Docs missing or thin: contributing, changelog
Most complex functions:
- run in src/stdio_server.rs: complexity 17, 52 lines
- main in examples/client.rs: complexity 15, 114 lines
Security
Security posture is adequate: no high-impact findings. Weakest area: posture.
| Area | Score |
|---|---|
| Secrets (gitleaks, tree + history) | 100 |
| Static analysis (Opengrep) | 98 |
| Vulnerable dependencies (OSV) | n/a |
| CI workflows (zizmor) | n/a |
| Posture (policy, updates, signing, lockfiles) | 0 |
| OpenSSF Scorecard | n/a |
- Posture checks passed: none; missing: security policy, dependency updates, signed commits, lockfiles
Top findings
| Severity | Finding | Location |
|---|---|---|
| low | opengrep/rust.lang.security.args: args should not be used for security operations. From the docs: "The first element is traditionally the path of the executable, but it can be set to arbitrary text, and might not even exist. This means this property should not be relied upon for security purposes." [confidence high] |
src/main.rs:19 |
Static signals only: the scorer never runs the project's code. Secret findings are pattern matches that were not verified, and secret values are never stored.
Repository profile
- Source lines: 3,612; test lines: 427
| Language | Lines |
|---|---|
| Rust | 3,536 |
| Shell | 503 |