updated 2026-11-11 00:08 UTC

Linux MCP Server

Repository

Tools to allow LLM clients to interact with Linux systems remotely

MCP Servers Python Listed Apache-2.0

Is Linux MCP Server safe? Strong public trust posture, backed by multiple independent signals.

OSSF Scorecard 6.8 / 10
Provenance Attested
Signed commits 100%
Last push today
Advisories None known
Compare Linux MCP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Linux MCP Server scores 83.8/100 (Grade A), ranked #123 of 1387 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 6.8/10; 100% of recent commits are signed; no published advisory affects its latest release (linux-mcp-server); last pushed 2026-11-11. Every point is earned from checkable signals — never paid placement. How scoring works →

How Linux MCP Server could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Linux MCP Server and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Signed

    github.com/rhel-lightspeed/linux-mcp-server, Apache-2.0, last pushed 2026-11-11. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 6.8/10 (scanned Nov 9, 2026). The checks that decide who can get a change released:

    • Code Review10
    • Branch Protection5
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies9
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 5
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 10
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 0
    License 10
    Maintained 10
    Packaging 10
    Pinned-Dependencies 9
    SAST 4
    Security-Policy 4
    Signed-Releases 0
    Token-Permissions 0
    Vulnerabilities 9

  3. Published packages Partly attested

    • PyPI linux-mcp-server Source link isn't a GitHub repo Build provenance attested

  4. What you install today No known advisories

    Latest release checked: linux-mcp-server 1.8.0. No published advisory affects it (OSV, checked 2026-11-10).

Changes to this chain

  • 2026-09-23 Package provenance attestation detected
  • 2026-08-26 OSSF Scorecard: 7.0/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Linux MCP Server’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Linux MCP Server compares in MCP Servers

  1. #48 LibreNMS MCP 84.0 +0.2
  2. #49 Scrivener MCP 83.9 +0.1
  3. #50 Linux MCP Server 83.8 this agent
  4. #51 Discord MCP 83.4 −0.4
  5. #52 MCP AutoMem 83.4 −0.4

Bars show each HVTrust score; the tick marks Linux MCP Server’s 83.8.

Where the 83.8 comes from

HVTrust dimensions vs the MCP Servers average

83.8 / 100 · 100.0% confidence

Linux MCP Server MCP Servers average (779 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
21.0 / 25
10.2 above avg 10.8
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.3 above avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
14.3 / 17
2.0 above avg 12.3
Maintenance60% last-push freshness · 40% commit activity
19.1 / 20
6.8 above avg 12.3
AdoptionLog-scaled stars · package downloads
9.9 / 20
2.3 above avg 7.6

Quick Trust Read

What Would Improve It
Improve adoption to lift the weakest part of the trust profile.
Recent Changes
2026-11-09
Rank Moved
Rank rose 33 spots (#158 → #125)
2026-10-27
Rank Moved
Rank rose 10 spots (#165 → #155)
2026-10-20
Grade Changed
Trust grade B → A
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 6.8/10. Tighten the weakest checks to improve public safety evidence.
Compare with another agent
View MCP Servers Report missing data
70.8
Activity sub-score · out of 100
#50
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 A 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-11-11 00:08 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
319
Forks
68
Last Push
2026-11-11
today
Commits (4 wk)
59
Downloads (7d)
821
pypi
HN mentions (30d)
—
Open Issues
17
Rank Change
▼1
was #122

Analysis

Activity Inputs

70.8 / 100
StarsRepository reach
15.0 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
22.2 / 25
CommunityFork signal
8.6 / 20

Common questions about Linux MCP Server

Public supply-chain signals for Linux MCP Server are strong: it has multiple independent trust indicators in place. This does not replace your own security review, but Linux MCP Server carries less obvious unverified-evidence risk than projects with thin signals.
Does Linux MCP Server publish package provenance?
Yes. Linux MCP Server's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Linux MCP Server have an OpenSSF Scorecard?
Linux MCP Server has an OpenSSF Scorecard score of 6.8/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 Linux MCP Server actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Linux MCP Server use?
Linux MCP Server ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Linux MCP Server's commits signed?
100% of the last 100 commits to Linux MCP Server 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
Linux MCP Server appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
medium confidence
1 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
medium confidence
1 tags
Broad capability areas detected.
  • database
Detailed evidence is not shown in the public view.
Package Provenance Drift
low confidence
Unknown
Package source metadata is missing or inconclusive
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 Linux MCP Server'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
Provider Added
Runtime surface grew — new detected provider dependency: Redis
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-05
Provider Added
Runtime surface grew — new detected provider dependency: Redis
2026-09-03
Provider Removed
Runtime surface shrank — no longer detected: Google Gemini, Multi-provider (LiteLLM)

Maintain Linux MCP Server?

For maintainers

HVTrust scores Linux MCP Server 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 10Grade 6HVTrust 3Surface 2Scorecard 1Surface 1Delisted 1Listed 1Provenance 1MCP 1
2026-11-09
Rank Moved
Rank rose 33 spots (#158 → #125)
2026-10-27
Rank Moved
Rank rose 10 spots (#165 → #155)
2026-10-20
Grade Changed
Trust grade B → A
2026-10-08
Grade Changed
Trust grade A → B
2026-10-08
Rank Moved
Rank dropped 11 spots (#150 → #161)
2026-09-28
Grade Changed
Trust grade B → A
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependency: Redis
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-23
Grade Changed
Trust grade D → B
2026-09-23
Rank Moved
Rank rose 578 spots (#727 → #149)
2026-09-23
HVTrust Changed
HVTrust up 49.2pts (30.3 → 79.5)
2026-09-22
Newly Listed
First tracked at rank #727
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-09
Grade Changed
Trust grade A → B
2026-09-09
Rank Moved
Rank dropped 45 spots (#98 → #143)
2026-09-09
HVTrust Changed
HVTrust down 3.3pts (82.7 → 79.4)
2026-09-05
Provider Added
Runtime surface grew — new detected provider dependency: Redis
2026-09-05
Rank Moved
Rank dropped 27 spots (#71 → #98)
2026-09-03
Provider Removed
Runtime surface shrank — no longer detected: Google Gemini, Multi-provider (LiteLLM)
2026-08-26
Scorecard Added
OSSF Scorecard: 7.0/10
2026-08-26
Grade Changed
Trust grade B → A
2026-08-26
Rank Moved
Rank rose 118 spots (#191 → #73)
2026-08-26
HVTrust Changed
HVTrust up 14.2pts (67.4 → 81.6)
2026-08-22
Rank Moved
Rank rose 13 spots (#190 → #177)
2026-08-20
Rank Moved
Rank rose 11 spots (#197 → #186)
2026-08-17
Rank Moved
Rank rose 14 spots (#201 → #187)
GitHub → PyPI: linux-mcp-server

Embed Badge Badge guide for maintainers →

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

Other agents in MCP Servers

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